Re: PANIC: early exception 08 rip 246:10 error ffffffff810251b5 cr2 0

["Justin P. Mattock" <justinmattock@gmail.com>]

Valdis.Kletnieks@vt.edu wrote:
> On Mon, 26 Oct 2009 14:16:34 PDT, "Justin P. Mattock" said:
>
>    
>>      
>
> Try this instead:
>
>
>                     printk(KERN_DEBUG "trying class=%d num=%d slot=%d func=%d\n",
>                               class, num, slot, func);
>                     if ((class == 0xffffffff)) {
>                         printk(KERN_DEBUG "No device here\n");
>                         continue; /* No device at this func */
>                     }
>
> The curly brackets are important.  This version will still panic, and it will
> probably spew a lot of msgs, but we'll hopefully find out which num/slot/func
> is giving it indigestion.
>
>
>    
O.K.thanks for the test printk.
(didn't even think of putting a curly bracket in there)

here's the results from your test printk:
(this goes on for some time during boot)

[    0.000000] trying class=-1 num=31 slot=30 func=7
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=0
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=1
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=2
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=3
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=4
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=5
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=6
[    0.000000] No device here
[    0.000000] trying class=-1 num=31 slot=31 func=7
[    0.000000] No device here
[    0.000000] init_ohci1394_dma: finished initializing OHCI DMA
[    0.000000] ACPI: RSDP 00000000000fe020 00024 (v02 APPLE )
[    0.000000] ACPI: XSDT 000000003fefd1c0 00074 (v01 APPLE   Apple00
000000A5      01000013)
[    0.000000] ACPI: FACP 000000003fefb000 000F4 (v03 APPLE   Apple00
000000A5 Loki 0000005F)


I'm going to have a look at this today, and look to
see if I can fix this.(also the guys e-mail bk@suse.de
keeps giving me a fail to send message so I took it off
for now, and then later I'll try to find that person and
update his e-mail).

Justin P. Mattock