oopses in 2.2.x

Godmar Back (gback@cs.utah.edu)
Wed, 31 Mar 1999 14:25:05 -0700 (MST)


I'm getting occasional oopses during the nightly run of updatedb,
triggered by cron.
This happens with both 2.2.1 and 2.2.3. It appears to
be intermittent. I've run kernels in various configurations, but
I was able to find that oops in the log for all of them:

[root@peerless linux]# fgrep 'Oops' /var/log/messages*
/var/log/messages:Mar 28 04:04:17 peerless kernel: Oops: 0002
/var/log/messages:Mar 29 04:04:11 peerless kernel: Oops: 0002
/var/log/messages:Mar 31 04:04:09 peerless kernel: Oops: 0002
/var/log/messages.1:Mar 25 04:04:13 peerless kernel: Oops: 0002
/var/log/messages.3:Mar 8 04:04:51 peerless kernel: Oops: 0002

I looked at it, and its indeed the same eip where it crashes.
I cannot trigger it when running updatedb from the cmdline, however.

- Godmar

Here's a trace, although I doubt it will be very useful:

Mar 25 04:04:13 peerless kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000000
Mar 25 04:04:13 peerless kernel: current->tss.cr3 = 075b0000, pr3 = 075b0000
Mar 25 04:04:13 peerless kernel: *pde = 00000000
Mar 25 04:04:13 peerless kernel: Oops: 0002
Mar 25 04:04:13 peerless kernel: CPU: 0
Mar 25 04:04:13 peerless kernel: EIP: 0010:[<c803f06c>]
Mar 25 04:04:13 peerless kernel: EFLAGS: 00010206
Mar 25 04:04:13 peerless kernel: eax: 00000138 ebx: c7537edc ecx: 0000004e edx: 00000138
Mar 25 04:04:13 peerless kernel: esi: c61fc600 edi: 00000000 ebp: 00000138 esp: c7537e28
Mar 25 04:04:13 peerless kernel: ds: 0018 es: 0018 ss: 0018
Mar 25 04:04:13 peerless kernel: Process find (pid: 1630, process nr: 91, stackpage=c7537000)
Mar 25 04:04:13 peerless kernel: Stack: c803fbe5 00000000 c61fc600 00000138 c7537edc c79635ec c80409c6 c7537edc
Mar 25 04:04:13 peerless kernel: c61fc600 00000138 c7537edc c79635ec 00000000 c7537f1c 00001564 00000003
Mar 25 04:04:13 peerless kernel: c803fbcc 000000a8 c8040005 c61fc600 c8045fc8 00000004 00000200 c79635ec
Mar 25 04:04:13 peerless kernel: Call Trace: [<c803fbe5>] [<c80409c6>] [<c803fbcc>] [<c8040005>] [<c8045fc8>] [<c8040c61>] [<c8042e6b>]
Mar 25 04:04:13 peerless kernel: [<c8045fc8>] [<c803fbcc>] [<c8042ee4>] [<c803e91d>] [<c01328c8>] [<c012dfc8>] [<c012e17e>] [<c012e255>]
Mar 25 04:04:13 peerless kernel: [<c012c2a2>] [<c0108c00>]
Mar 25 04:04:13 peerless kernel: Code: f3 a5 a8 02 74 02 66 a5 a8 01 74 01 a4 5e 5f c3 57 56 8b 7c

>>EIP: c803f06c <END_OF_CODE+9760/????>
Trace: c803fbe5 <END_OF_CODE+a2d9/????>
Trace: c80409c6 <END_OF_CODE+b0ba/????>
Trace: c803fbcc <END_OF_CODE+a2c0/????>
Trace: c8040005 <END_OF_CODE+a6f9/????>
Trace: c8045fc8 <END_OF_CODE+106bc/????>
Trace: c8040c61 <END_OF_CODE+b355/????>
Trace: c8042e6b <END_OF_CODE+d55f/????>
Trace: c8045fc8 <END_OF_CODE+106bc/????>
Trace: c012c2a2 <sys_newlstat+2e/94>
Code: c803f06c <END_OF_CODE+9760/????> 00000000 <_EIP>:
Code: c803f06c <END_OF_CODE+9760/????> 0: f3 a5 repz movsl %ds:(%esi),%es:(%edi)
Code: c803f06e <END_OF_CODE+9762/????> 2: a8 02 testb $0x2,%al
Code: c803f070 <END_OF_CODE+9764/????> 4: 74 02 je 8 <_EIP+0x8> c803f074 <END_OF_CODE+9768/????>
Code: c803f072 <END_OF_CODE+9766/????> 6: 66 a5 movsw %ds:(%esi),%es:(%edi)
Code: c803f074 <END_OF_CODE+9768/????> 8: a8 01 testb $0x1,%al
Code: c803f076 <END_OF_CODE+976a/????> a: 74 01 je d <_EIP+0xd> c803f079 <END_OF_CODE+976d/????>
Code: c803f078 <END_OF_CODE+976c/????> c: a4 movsb %ds:(%esi),%es:(%edi)
Code: c803f079 <END_OF_CODE+976d/????> d: 5e popl %esi
Code: c803f07a <END_OF_CODE+976e/????> e: 5f popl %edi
Code: c803f07b <END_OF_CODE+976f/????> f: c3 ret
Code: c803f07c <END_OF_CODE+9770/????> 10: 57 pushl %edi
Code: c803f07d <END_OF_CODE+9771/????> 11: 56 pushl %esi
Code: c803f07e <END_OF_CODE+9772/????> 12: 8b 7c 00 00 movl 0x0(%eax,%eax,1),%edi

-
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/