Yep, I've seen a similar oops during a high stress test on a UP system
(two make -j10 in different kernel trees). The only problem was that
the oops in the kernel message wasn't fully readable for ksysmoops
(bit garbage). After running fsck by hand to recover /dev/sda10 aka
/usr/src/ the system is up again.
Werner
>
> Output from ksymoops:
>
> Jan 26 09:30:00 avo kernel: current->tss.cr3 = 0aed8000, `r3 = 0aed8000
> Jan 26 09:30:00 avo kernel: *pde = 00000000
> Jan 26 09:30:00 avo kernel: Oops: 0002
> Jan 26 09:30:00 avo kernel: CPU: 1
> Jan 26 09:30:00 avo kernel: EIP: 0010:[<c01220db>]
> Jan 26 09:30:00 avo kernel: EFLAGS: 00010282
> Jan 26 09:30:00 avo kernel: eax: 0000003b ebx: c04e36e0 ecx: c0239ad2 edx: cf5fc000
> Jan 26 09:30:00 avo kernel: esi: cbd54880 edi: 00000282 ebp: 00000000 esp: cb003ee8
> Jan 26 09:30:00 avo kernel: ds: 0018 es: 0018 ss: 0018
> Jan 26 09:30:00 avo kernel: Process ps (pid: 6984, process nr: 66, stackpage=cb003000)
> Jan 26 09:30:00 avo kernel: Stack: cb1b4000 000007ff 00000000 cbd548fc 00000000 c01138b9 c04e36e0 cbd54880
> Jan 26 09:30:00 avo kernel: cbd54880 cbd54880 cbd54880 cbd54880 c0151ef6 cbd54880 c015206f cbd54880
> Jan 26 09:30:00 avo kernel: cbd54880 bfffff6f bfffff75 cb1b4000 00001b4b cb1b4000 c0215e0c c0153157
> Jan 26 09:30:00 avo kernel: Call Trace: [<c01138b9>] [<c0151ef6>] [<c015206f>] [<c0153157>] [<c0153269>] [<c0126202>] [<c0126976>]
> Jan 26 09:30:00 avo kernel: [<c0108c00>]
> Jan 26 09:30:00 avo kernel: Code: c7 05 00 00 00 00 00 00 00 00 5b 5e 5f 5d 83 c4 0c c3 8d 76
>
>
> >>EIP: c01220db <kmem_cache_free+17b/19c>
> Trace: c01138b9 <mmput+31/38>
> Trace: c0151ef6 <release_mm+1a/20>
> Trace: c015206f <get_arg+33/3c>
> Trace: c0153157 <get_process_array+6f/a0>
> Trace: c0153269 <array_read+e1/238>
> Trace: c0126202 <filp_open+46/f8>
> Trace: c0126976 <sys_read+d2/104>
> Trace: c0108c00 <system_call+34/38>
> Code: c01220db <kmem_cache_free+17b/19c> 00000000 <_EIP>:
> Code: c01220db <kmem_cache_free+17b/19c> 0: c7 05 00 00 00 movl $0x0,0x0
> Code: c01220e0 <kmem_cache_free+180/19c> 5: 00 00 00 00 00
> Code: c01220e5 <kmem_cache_free+185/19c> a: 5b popl %ebx
> Code: c01220e6 <kmem_cache_free+186/19c> b: 5e popl %esi
> Code: c01220e7 <kmem_cache_free+187/19c> c: 5f popl %edi
> Code: c01220e8 <kmem_cache_free+188/19c> d: 5d popl %ebp
> Code: c01220e9 <kmem_cache_free+189/19c> e: 83 c4 0c addl $0xc,%esp
> Code: c01220ec <kmem_cache_free+18c/19c> 11: c3 ret
> Code: c01220ed <kmem_cache_free+18d/19c> 12: 8d 76 00 leal 0x0(%esi),%esi
-
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/