Kernel oops in 2.0.29

Andy Berkheimer (andy@tho.org)
Fri, 21 Feb 1997 17:45:37 -0500

2.0.29 has been a bit odd lately. It will get to a point where running
_any_ process produces a SIGSEGV and the following oops. The only way to
fix it is to reboot. I think it _may_ have to do with some RAM I got from
a friend recently, it's 70ns on a 66 MHz bus, which is known to cause
problems, but I thought I'd report this anyways to see if its something
else (appears to be ext2fs related...also, the same oops is produced
every time it oopses).

Unable to handle kernel paging request at virtual address c42018a0
current->tss.cr3 = 016a2000,
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<0012db7a>]
EFLAGS: 00010202
eax: 00000003 ebx: 005d2d90 ecx: 00000000 edx: 042018a0
esi: 001fec8c edi: 000253c9 ebp: 00201990 esp: 016a3ec0
ds: 0018 es: 0018 fs: 002b gs: 002b ss: 0018
Process inc (pid: 30409, process nr: 17, stackpage=016a3000)
Stack: 004b72e0 005d2d90 0000eee0 000002e8 00001601 001fec8c 00155d47 005d2d90
004b72e0 00000003 000253c9 01322dc0 00012e00 0000eee0 bfffe86c 004b72d8
000002d8 00000000 006064d8 006064d8 00000000 00000000 006064d8 00157293
Call Trace: [<00155d47>] [<00157293>] [<0012a170>] [<0012a688>] [<0012c0c0>] [<0012bfc4>] [<0010a5b9>]
Code: 39 32 75 16 8b 46 2c 89 02 5b 5e 5f 5d 83 c4 08 c3 90 89 54

And the ksymoops output:

Using `../System.map' to map addresses to symbols.

>>EIP: 12db7a <dcache_add+ba/194>
Trace: 155d47 <ext2_readdir+4af/618>
Trace: 157293 <ext2_put_inode+b/64>
Trace: 12a170 <putname+c/10>
Trace: 12a688 <namei+3c/48>
Trace: 12c0c0 <old_readdir+84/a0>
Trace: 12bfc4 <fillonedir>
Trace: 10a5b9 <system_call+55/7c>

Code: 12db7a <dcache_add+ba/194> 

--
Andy Berkheimer			| Home: andy@tho.org
aberkhei@acm.org		| Work: andrewb@mitre.org