From: Valdis.Kletnieks@vt.edu
To: Justin Mattock <justinmattock@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
Bernhard Kaindl <bk@suse.de>
Subject: Re: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Date: Mon, 26 Oct 2009 16:29:36 -0400 [thread overview]
Message-ID: <21504.1256588976@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 26 Oct 2009 11:34:20 PDT." <dd18b0c30910261134s76274dbbj9c1904e78c2b5a38@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
On Mon, 26 Oct 2009 11:34:20 PDT, Justin Mattock said:
> I can't seem to locate a right mailing list
> for ieee1394 for Linux. Anyways here is a
> url to flickr which has the image of the PANIC:
> http://www.flickr.com/photos/44066293@N08/4046711653/
> (hopefully you don't need to sign up to view)
>
> As for the problem, interesting thing here is if I add
> a printk to:
>
> if ((class == 0xffffffff))
> printk(KERN_BUG "init_ohci1394_dma: finished initializing OHCI DMA\n");
> continue; /* No device at this func */
>
> the system will boot-up, and the PANIC will not occur.
Note that just sticking a printk in there without a { } pair enclosing
the printk and continue will change the semantics drastically - if the
conditional is true, it will do the printk instead of continuing. And
possibly more important, the continue just became unconditional.
What *exactly* does your code look like now?
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2009-10-26 20:29 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 [this message]
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
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=21504.1256588976@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=bk@suse.de \
--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®