Messages in this thread |  | | Subject | Re: 2.4.10: Crash on boot with trident driver non-module | From | "Trever L. Adams" <> | Date | 26 Sep 2001 08:32:12 -0400 |
| |
Well, I realized that the EIP wasn't typed in correctly. the l was supposed to be a 1. The new output is:
>>???; c01ba1ce <ac97_init_mixer+7e/e0> <===== Trace; c01bae74 <pci_announce_device+34/50> Trace; c01baed2 <pci_register_driver+42/60> Trace; c0105000 <_stext+0/0> Trace; c0105049 <init+9/140> Trace; c0105000 <_stext+0/0> Trace; c0105536 <kernel_thread+26/30> Trace; c0105040 <init+0/140>
Hope this helps. I am having a hard time seeing where the changes in 2.4.9 would cause this NULL dereference in ac97_init_mixer when it is compiled in but not when it is a module.
Trever
> ac97_codec: AC97 Codec, id 0x0000:0x0000 (unknown) > Unable to handle kernel Null pointer derefference at virtual addresss 00000000 > *pde = 00000000 > Oops: 0000 > CPU: 0 > EIP: 0010:[<c01balce>] > EFLAGS: 00010206 > EAX: 00000000 ebx: c7faac80 ecx: 00000802 edx: 00000006 > esi: 00000000 edi: c7faad30 ebp: 00000001 esp: c1219f48 > ds: 0018 es: 0018 ss: 0018 > Process swapper pid 1, stackpage=c1219000 > stack: c7faac80 00000040 c7faad30 00000001 > c026831b c7faac80 00000024 00000003 > c024da40 c1275000 ffffffff 000cc000 (may be 0000cc00) > c02687b1 c1275000 0200180d c027063c > c024db00 c1212000 00000000 c01bae74 > c1212000 c026063c c1212000 c024db00 > call trace: [<c01bae74>] [<c01baed2>] [<c0105000>] [<c0105049>] > [<c0105000>] [<c0105536>] [<c0105040>] > code: 8b 00 85 c0 74 04 53 ff d0 5a 31 ed 83 3d 40 dc 24 c0 ff ba > Using defaults from ksymoops -a i386 > Error (Oops_bfd_perror): /tmp/ksymoops.pWqCMC Invalid bfd target > > Trace; c01bae74 <pci_announce_device+34/50> > Trace; c01baed2 <pci_register_driver+42/60> > Trace; c0105000 <_stext+0/0> > Trace; c0105049 <init+9/140> > Trace; c0105000 <_stext+0/0> > Trace; c0105536 <kernel_thread+26/30> > Trace; c0105040 <init+0/140> > > Kernel Panic: Attempted to kill init! > > 984 warnings and 1 error issued. Results may not be reliable.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |