Comment 0 for bug 7168

Package: kernel-image-2.4.26-1-686
Version: 2.4.26-2
Priority: normal

I really don't know what caused this (the computer in which this was found
is turned on 24h a day and I didn't see the oops, I just found it
unresponsive at that time). Digging in the logs (today, now that I had
time) I found this at 06:56 two days ago I found this:

-------------------------------------------------------------------
Jun 18 06:46:38 xxxx -- MARK --
Jun 18 06:56:46 xxxx kernel: printing eip:
Jun 18 06:56:46 xxxx kernel: c0153c3d
Jun 18 06:56:46 xxxx kernel: Oops: 0002
Jun 18 06:56:46 xxxx kernel: CPU: 0
Jun 18 06:56:46 xxxx kernel: EIP: 0010:[d_alloc+77/368] Not tainted
Jun 18 06:56:46 xxxx kernel: EFLAGS: 00010217
Jun 18 06:56:46 xxxx kernel: eax: 0000000e ebx: 2f7795a0 ecx: 00000003
edx: 2f7795fc
Jun 18 06:56:46 xxxx kernel: esi: ce4e0000 edi: 2f7795fc ebp: cfa48620
esp: cd9fdeec
Jun 18 06:56:46 xxxx kernel: ds: 0018 es: 0018 ss: 0018
Jun 18 06:56:46 xxxx kernel: Process find (pid: 31710, stackpage=cd9fd000)
Jun 18 06:56:46 xxxx kernel: Stack: c1487f84 000001f0 0000000e fffffff4
cef9986c cef99800 cfa48620 c014a657
Jun 18 06:56:46 xxxx kernel: cfa48620 cd9fdf40 00000000 ce4e000e
00000000 cd9fdf98 c014ad38 cfa48620
Jun 18 06:56:46 xxxx kernel: cd9fdf40 00000000 00000008 cef99800
00000000 ce4e0000 0000000e a6a94a0b
Jun 18 06:56:46 xxxx kernel: Call Trace: [real_lookup+183/240]
[link_path_walk+1400/1680] [path_lookup+57/64] [__user_walk+73/96]
[sys_lstat64+31/144]
Jun 18 06:56:46 xxxx kernel: [system_call+51/56]
Jun 18 06:56:46 xxxx kernel:
Jun 18 06:56:46 xxxx kernel: Code: f3 a5 a8 02 74 02 66 a5 a8 01 74 01 a4
8b 4c 24 24 85 ed 8b
Jun 18 06:56:46 xxxx kernel: <1>Unable to handle kernel paging request at
virtual address 2f7795fc
Jun 18 06:56:46 xxxx kernel: printing eip:
Jun 18 06:56:46 xxxx kernel: c0153c3d
Jun 18 06:56:46 xxxx kernel: Oops: 0002
Jun 18 06:56:46 xxxx kernel: CPU: 0
Jun 18 06:56:46 xxxx kernel: EIP: 0010:[d_alloc+77/368] Not tainted
Jun 18 06:56:46 xxxx kernel: EFLAGS: 00010213
Jun 18 06:56:46 xxxx kernel: eax: 00000007 ebx: 2f7795a0 ecx: 00000001
edx: 2f7795fc
-------------------------------------------------------------------

Followed by 5 other oops (ksymoops of all of them attached). Since the last
symoops named process 'cron' it seems that it might be related to it. I had
to manually reset the system after this oops at that time.

If there's anything I can do to try to catch this and reproduce it,
please let me know.

Regards

Javier