From: Scott Wood <scottwood@freescale.com>
To: Ron Madrid <ron_madrid@sbcglobal.net>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Bus Error on MPC8313
Date: Fri, 13 Nov 2009 13:33:33 -0600 [thread overview]
Message-ID: <4AFDB48D.9080203@freescale.com> (raw)
In-Reply-To: <705994.38950.qm@web83505.mail.sp1.yahoo.com>
Ron Madrid wrote:
> I wrote a custom driver for an MPC8313 based board. Everything seems to
> have been working for a long time, but now one of my IOCTL functions seems
> to be having a problem. I'm getting a "Bus error" reported by my
> application and also a kernel "Oops". Here's what the kernel is reporting.
>
> Oops: Machine check, sig: 7 [#1]
Were there any messages before this? Is there anything interesting in
the arbiter registers?
Is this custom driver using the localbus, and are there any NAND
operations going on at the same time?
-Scott
next prev parent reply other threads:[~2009-11-13 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-13 19:07 Bus Error on MPC8313 Ron Madrid
2009-11-13 19:33 ` Scott Wood [this message]
2009-11-13 19:49 ` Ron Madrid
2009-11-13 19:57 ` Scott Wood
2009-11-13 20:08 ` Ron Madrid
2009-11-13 20:17 ` Scott Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AFDB48D.9080203@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ron_madrid@sbcglobal.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox