From: n.kinar@usask.ca (Nicholas Kinar)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel oops with undefined instruction when accessing memory on an AT91 custom system
Date: Sat, 14 May 2011 21:52:21 -0600 [thread overview]
Message-ID: <4DCF4DF5.8020004@usask.ca> (raw)
In-Reply-To: <4DCEF71A.9050405@vollmann.ch>
Detlef Vollmann wrote:
> On 05/14/11 18:28, Nicholas Kinar wrote:
>> I've had a number of random kernel oops when trying to use the AT91 mmc
>> driver with an SD card,
> I'm not sure if this is related, but we also get oopses with SDcard,
> with both, at91_mci.c and atmel-mci.c.
> But we only get it with debugging turned on (CONFIG_DEBUG_BUGVERBOSE=y
> and CONFIG_DEBUG_VM=y).
> This is the interesting part of the oops:
> kernel BUG at include/linux/mm.h:636
> [<c0026450>] (__bug+0x18/0x24) from [<c0029d30>]
> (flush_dcache_page+0x28/0x144)
> [<c0029d30>] (flush_dcache_page+0x28/0x144) from [<c01b5240>]
> (atmci_interrupt+0x1f4/0x6ec)
> [<c01b5240>] (atmci_interrupt+0x1f4/0x6ec) from [<c00567f4>]
> (handle_IRQ_event+0x3c/0x10c)
>
> This is for a 2.6.32 kernel, but I also tested 2.6.39-rc4.
> The interesting thing is that this only happens with SDcard, with
> an original MMC card everything is fine.
> I haven't had the time yet to hunt this down, but I propose you
> turn on DEBUG_VM and BUG and see whether you get more consistent oopses.
>
> Detlef
Thanks for your response, Detlef. It appears that the AT91 mmc driver
is a little bit more stable now with debugging turned off. The kernel
oops still continues as documented in my response to Nicolas Ferre, but
I think that the debugging should indeed be turned off in a production
system.
Once again, thank you very much for your response!
Nicholas
next prev parent reply other threads:[~2011-05-15 3:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 16:28 Kernel oops with undefined instruction when accessing memory on an AT91 custom system Nicholas Kinar
2011-05-14 20:43 ` Nicolas Ferre
2011-05-15 3:48 ` Nicholas Kinar
2011-05-15 7:33 ` Russell King - ARM Linux
2011-05-15 14:24 ` Nicholas Kinar
2011-05-14 21:41 ` Detlef Vollmann
2011-05-15 3:52 ` Nicholas Kinar [this message]
2011-05-15 15:08 ` Detlef Vollmann
2011-05-15 15:15 ` Nicholas Kinar
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=4DCF4DF5.8020004@usask.ca \
--to=n.kinar@usask.ca \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).