Ah! Bad luck that I did not know this at the time: I recompiled the kernel sometime after that log. It was the only time the system remained running enough time for me to save the log. In any case, I get this: ksymoops 2.4.2 on i686 2.4.16-4GB. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.16-4GB/ (default) -m /boot/System.map-2.4.16-4GB (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c01e53a0, System.map says c0151e6Warning (compare_maps): mismatch on symbol __nvsym03120 , NVdriver says c74da780, /lib/modules/2.4.16-4GB/vid Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010006 eax: c54a9dc4 ebx: 00000000 ecx: 00000001 edx: 00000001 esi: c7d7f014 edi: c4313a80 ebp: c577fee4 esp: c577fec8 ds: 0018 es: 0018 ss: 0018 Process klogd (pid: 493, stackpage=c577f000) Stack: c54a9dc0 c4313a80 c4313a80 c54a9dc4 00000001 00000286 00000001 c577ff20 c01ed14e 7fffffff cfeaa580 c0227029 c4313a80 0000003a c577ff48 c577ff80 c577ff48 c5fec080 00000000 00000000 ffffffe0 c51e7d80 c5c29624 c01ea898 Call Trace: [<c01ed14e>] [<c0227029>] [<c01ea898>] [<c01eaabe>] [<c01315fb>] [<c0106d4b>] Code: 8b 03 85 45 fc 74 56 31 c0 9c 5f fa c7 03 00 00 00 00 83 7b
EIP; c0113fc4 <__wake_up+2c/a0> <===== Trace; c01ed14e
Trace; c0227028 Trace; c01ea898 Trace; c01eaabe Trace; c01315fa Trace; c0106d4a Code; c0113fc4 <__wake_up+2c/a0> 00000000 <_EIP>: EIP; c0113fc4 <__wake_up+2c/a0> <===== Trace; c01ed14e Trace; c0227028 Trace; c01ea898 Trace; c01eaabe Trace; c01315fa Trace; c0106d4a Code; c0113fc4 <__wake_up+2c/a0> 00000000 <_EIP>: Code; c0113fc4 <__wake_up+2c/a0> <===== 0: 8b 03 mov (%ebx),%eax <===== Code; c0113fc6 <__wake_up+2e/a0> 2: 85 45 fc test %eax,0xfffffffc(%ebp) Code; c0113fc8 <__wake_up+30/a0> 5: 74 56 je 5d <_EIP+0x5d> c0114020 <__wake_up+88/a0> Code; c0113fca <__wake_up+32/a0> 7: 31 c0 xor %eax,%eax Code; c0113fcc <__wake_up+34/a0> 9: 9c pushf Code; c0113fce <__wake_up+36/a0> a: 5f pop %edi Code; c0113fce <__wake_up+36/a0> b: fa cli Code; c0113fd0 <__wake_up+38/a0> c: c7 03 00 00 00 00 movl $0x0,(%ebx) Code; c0113fd6 <__wake_up+3e/a0> 12: 83 7b 00 00 cmpl $0x0,0x0(%ebx)
Unable to handle kernel NULL pointer dereference at virtual address 00000000 c0113fc4 *pde = 00000000 Oops: 0000 But I can not understand almost any of it, I'm not a kernel speciallist. -- Cheers, Carlos Robinson El 02.10.07 a las 06:58, Graham Murray escribió:
Date: Mon, 07 Oct 2002 06:58:09 +0100 From: Graham Murray
To: suse-linux-e@suse.com Subject: Re: [SLE] faster booting? "Carlos E. R."
writes: (this one is normal, happens every time I log of X - what happened later is not)
Oops: 0000 CPU: 0 EIP: 0010:[<c0113fc4>] Not tainted [snip]
That is a kernel oops. Input all that data (either from a log file if it has been written, or enter by hand) through 'ksymoops' which will decode it and indicate where the problem is occurring.