lkml.org 
[lkml]   [2009]   [Oct]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0
Valdis.Kletnieks@vt.edu wrote:
> 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.. ;)
>
>
So after looking around I managed to get the machine to boot
by commenting out(just to see) some calls in
init_ohci1394_controller

these are the ones:

set_fixmap_nocache(FIX_OHCI1394_BASE, ohci_base);

init_ohci1394_reset_and_init_dma(&ohci);


Then kind of isolating the issue I looked into
set_fixmap_nocache
Now looking at fixmap.h I see some comments about
x86_64 integration, leading me to believe maybe this is what/why
I'm hitting a panic.

Justin P. mattock






\
 
 \ /
  Last update: 2009-10-28 04:59    [W:0.093 / U:0.696 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site