Re: 2.3.20 will not boot (PCI problem)

Tim Waugh (tim@cyberelk.demon.co.uk)
Sun, 10 Oct 1999 20:05:16 +0100 (BST)


On Sun, 10 Oct 1999, Linus Torvalds wrote:

> >PCI: PCI BIOS revision 2.10 entry at 0xfbc30
> >PCI: Using configuration type 1
> >PCI: Probing PCI hardware
> >Unable to handle kernel paging request at virtual address 000fc140
> > printing eip:
> >c00fbf7a
> >*pde = 00000000
> >Oops: 0000
> >CPU: 0
> >EIP: 0010:[<c00fbf7a>]
> >EFLAGS: 00010002
> >eax: 0000b10e ebx: 00000000 ecx: 00000000 edx: 00000002
> >esi: 000fc140 edi: c0003fa4 ebp: c0004000 esp: c0003f5e
> >ds: 0018 es: 0018 ss: 0018
> >Process swapper (pid: 1, stackpage=c0003000)
> >Stack: c0004000 c0003f76 00000000 00000002 00000000 0000b10e c00fbcaf 0000b10e
> > 00000002 8aee8246 0010c020 00180000 2784c020 0000c01f 60000000 0e00c010
> > 40200000 0fe0c000 c0004020 925e0018 2784c020 2784c01f 6000c01f 938dc010
> >Call Trace: [<c01bf1a5>] [<c01bf1ed>] [<c01bf1f8>] [<c01bf20c>] [<c01bf220>] [<c01bf4a8>] [<c010200>]
> >(this is where I got it to stop)
>
> Would you mind trying to turn the hex addresses into function+offset?
> ksymoops should do it for you, and it's needed to make any sense of it.

I didn't do that originally because there's not much there. My System.map
has:

c01bdf70 T stext_lock
c01c02e8 r common_interrupt

and all the addresses are in stext_lock. I also left the EIP alone: the
first kernel symbol is at 0xc0100000; the PCI BIOS entry is at 0xfbc30,
and EIP is at 0xc0000000 + 0xfbc30 + a bit. Doesn't that mean we're
oopsing inside the PCI BIOS?

Tim.
*/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/