Machine info:
ASUS P2B-D, 2 x PII/266, 256M, SCSI disks, SB64_AWE, NE2K, four port
Byterunner serial card.
Linux avo.ic.net 2.2.0 #6 SMP Tue Jan 26 02:36:04 EST 1999 i686 unknown
Gnu C 2.7.2.3
Binutils 2.9.1.0.4
Linux C Library 2.0.7
Dynamic linker ldd (GNU libc) 2.0.7
Linux C++ Library 2.8.0
Procps 1.2.7
Mount 2.7l
Net-tools 1.33
Kbd 0.94
Sh-utils 1.16
I had been banging on 2.2.0 a little last night before I went to bed.
Doing big file reads, tested my scanner, etc. Because of the
timestamp I believe it crashed just as a cron job was running this
morning. The cron job is just a script which periodically verifies my
ppp link is up and some other basic system status type stuff. The
machine was also running two instances of Mersenne prime testing
software. These are fairly CPU intensive and were running niced in
the background.
I've been running the 2.1 and 2.2.0-pre kernels for several months and
never had an oops before. In fact this is my first use of ksymoops,
so I hope I interpreted it correctly for the Subject: line.
My .config and the cron script which was apparently running are
available on request. Trace is below....
David
----
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/