From: dv@vollmann.ch (Detlef Vollmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Kernel oops with undefined instruction when accessing memory on an AT91 custom system
Date: Sun, 15 May 2011 17:08:38 +0200 [thread overview]
Message-ID: <4DCFEC76.9050504@vollmann.ch> (raw)
In-Reply-To: <4DCF4DF5.8020004@usask.ca>
On 05/15/11 05:52, Nicholas Kinar wrote:
> Detlef Vollmann wrote:
>> 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.
> 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.
My point was not that you should turn on debugging in a production
system, my point was that you should turn on debugging features for
debugging the problem.
Turning on debugging features will quite probably not introduce new
problems -- it will just show you problems much earlier and much
nearer to the original cause, so it's much easier to find that original
cause.
Detlef
next prev parent reply other threads:[~2011-05-15 15:08 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
2011-05-15 15:08 ` Detlef Vollmann [this message]
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=4DCFEC76.9050504@vollmann.ch \
--to=dv@vollmann.ch \
--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).