Messages in this thread | | | From | Keith Owens <> | Subject | Re: 2.2.13 kernel oops | Date | Tue, 23 Nov 1999 01:34:12 +1100 |
| |
On Mon, 22 Nov 1999 10:05:59 -0400 (AST), synrg@bgpc.dymaxion.ca wrote: >Came in to work this morning to find machine hung. Details follow: > >ksymoops 0.7c on i686 2.2.13. Options used > -V (default) > -k ksymoops/19991119062555.ksyms (specified) > -l ksymoops/19991119062555.modules (specified) > -o /lib/modules/2.2.13/ (default) > -m /boot/System.map-2.2.13 (default) > >Warning (expand_objects): object /lib/modules/2.2.13/sound/persist.o for module persist has changed since load >Warning (expand_objects): object /lib/modules/2.2.13/fs/smbfs.o for module smbfs has changed since load >Nov 20 06:25:39 bgpc kernel: Oops: 0002 >Nov 20 06:25:39 bgpc kernel: CPU: 0 >Nov 20 06:25:39 bgpc kernel: EIP: 0010:[free_pages+237/312] >Nov 20 06:25:39 bgpc kernel: EFLAGS: 00010006 >Nov 20 06:25:39 bgpc kernel: eax: 00000000 ebx: 000023e4 ecx: c01eb960 edx: 00000000 >Nov 20 06:25:39 bgpc kernel: esi: 000008f9 edi: fffffffe ebp: 00000203 esp: c0b63f3c >Nov 20 06:25:39 bgpc kernel: ds: 0018 es: 0018 ss: 0018 >Nov 20 06:25:39 bgpc kernel: Process find (pid: 963, process nr: 60, stackpage=c0b63000) >Nov 20 06:25:39 bgpc kernel: Stack: 0805a700 bffff4c0 c0b62000 c23e5000 00000004 c01eb960 00000000 00002c1b >Nov 20 06:25:39 bgpc kernel: 00001000 c012bb20 c23e5000 c08744a0 00000000 00000000 c0b62000 bffff698 > >2 warnings issued. Results may not be reliable. > >I have a bit of trouble with the ksymoops logging, as my /var isn't >mounted at the time the modules are loaded, but the kernel hasn't >changed since the .ksyms and .modules I used for the above report >were written.
Oh yes it has :). The warnings are because the timestamp on the loaded module is not the same as the timestamp on the object file in /lib/modules, something changed after the modules were loaded. Running insmod_ksymoops_clean (from the modutils package) after /var is mounted will (a) delete older entries and (b) take a new snapshot for later reference. Also where did the call trace and code lines go to in that oops?
- 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/
| |