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:57:52 -0600 [thread overview]
Message-ID: <4AFDBA40.5070309@freescale.com> (raw)
In-Reply-To: <200007.626.qm@web83506.mail.sp1.yahoo.com>
Ron Madrid wrote:
> --- On Fri, 11/13/09, Scott Wood <scottwood@freescale.com> wrote:
>
>> From: Scott Wood <scottwood@freescale.com>
>> Subject: Re: Bus Error on MPC8313
>> To: "Ron Madrid" <ron_madrid@sbcglobal.net>
>> Cc: linuxppc-dev@ozlabs.org
>> Date: Friday, November 13, 2009, 11:33 AM
>> 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?
>
> No messages prior, only the normal kernel boot messages.
Hmm, for some reason e300c3's cputable entry has no machine_check field,
while all the other e300s point to machine_check_generic.
> And when this
> does happen in usually causes a lockup, so I haven't been able to check the
> status of any arbiter registers.
The system is up long enough to print an oops; you could stick some
output in the trap handler.
>> Is this custom driver using the localbus, and are there any
>> NAND operations going on at the same time?
>
> This driver does use the localbus.
OK, check the localbus error registers as well.
> It seems to happen (when it does) when
> performing an access to our FPGA that is connected via UPM on the localbus.
> I do not know if there are any NAND operations going on at that same time.
> If there are, they are not being directly caused by any of my apps or
> driver calls.
Are there any filesystems mounted on NAND? There are some issues with
transactions timing out if there's contention with a long-running NAND
operation.
-Scott
next prev parent reply other threads:[~2009-11-13 19:57 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
2009-11-13 19:49 ` Ron Madrid
2009-11-13 19:57 ` Scott Wood [this message]
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=4AFDBA40.5070309@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