From: Valdis.Kletnieks@vt.edu
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Date: Tue, 27 Oct 2009 15:35:13 -0400 [thread overview]
Message-ID: <22388.1256672113@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Tue, 27 Oct 2009 12:07:34 PDT." <4AE744F6.5050801@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 864 bytes --]
On Tue, 27 Oct 2009 12:07:34 PDT, "Justin P. Mattock" said:
> The results are similar with the messages, except
> with the curly's the system will panic the same as above
> and not boot.
As I expected - I explained why already. And in fact, I intentionally did
that, so that the *last* one of those added messages before your panic
will output the info regarding the device that caused it (hacking around
the panic would mean that you'd get a whole bunch of messages and not have
an easy way to tell *which one* caused the now-bypassed issue...)
> (So I guess it was good to forget the curly's
> to some extent).
So out of curiosity, what did the messages actually *SAY*? They should
be pointing at the device that's giving your system indigestion, so it's
useful to actually include the output (I didn't pull that printk format
string out of thin air.. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-10-27 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-23 23:45 Justin P. Mattock
2009-10-26 18:34 ` Justin Mattock
2009-10-26 20:29 ` Valdis.Kletnieks
2009-10-26 21:16 ` Justin P. Mattock
2009-10-27 6:23 ` Valdis.Kletnieks
2009-10-27 18:57 ` Justin P. Mattock
2009-10-27 19:07 ` Justin P. Mattock
2009-10-27 19:35 ` Valdis.Kletnieks [this message]
2009-10-27 20:34 ` Justin P. Mattock
2009-10-28 3:56 ` Justin P. Mattock
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=22388.1256672113@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®