From: Alan B. <al...@ms...> - 2001-02-12 09:49:29
|
hi, > > BTW have you enabled the additional debugging code as suggested by Geert? > > ooops. I forgot to enable debug in drivers/pci/pci.c > When I enable debug there, the kernel panics rigth after startup > dmesg output: sounds familiar > Bus scan for 00 returning with max=00 > Zorro: Probing AutoConfig expansion devices: 3 devices > Oops: kernel access of bad area, sig: 11 > NIP: C00177DC XER: 00000000 LR: C001786C SP: C01C9ED0 REGS: c01c9e20 TRAP: 0300 > MSR: 00009072 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 > DAR: 00009076, DSISR: 40000000 > TASK = c01c8000[1] 'swapper' Last syscall: -1 > last math 00000000 last altivec 00000000 > GPR00: 01000000 C01C9ED0 C01C8000 00009072 C0134134 00000001 801E069E 00000000 > GPR08: FF000000 C01C9BCC FFFFFFFF C012C85C 44848024 08171B74 0807E0CC 3C8AB800 > GPR16: 0928F000 0000004C 00000000 00000000 003FF000 FFFFFD6C 0000001D 08910000 > GPR24: 08910000 00000000 C0170000 C0140000 C0170000 00000002 C0130000 C0134134 > Call backtrace: > 00007F00 C014ABC0 C013F834 C00039F0 C0006438 > Kernel panic: Attempted to kill init! > Rebooting in 180 seconds..<<<<<<<<<<<<<<<<<<<< nah, slightly different place...its still the 'swapper' that crashes though. In my case, its a 2.4 kernel with different options enabled (to get 'user-ready' 2.4 kernel the same config as the 2.2.10 kernel. I've started to disable bits and pieces. I was just going to get the module from sourceforge and compare the two configs...and then isolate which option causes the kernel to oooops on startup :-| alan |