kernel: kernel BUG at dcache.c352

[pcorchary]

Help!

I need some information or references to information on this type of error. I'm being told that this is a hardware RAM problem, and I think that is WRONG!

Any information appreciated:

Jan 9 04:06:23 dnweb1 kernel: kernel BUG at dcache.c:352!
Jan 9 04:06:23 dnweb1 kernel: invalid operand: 0000
Jan 9 04:06:23 dnweb1 kernel: CPU: 1
Jan 9 04:06:23 dnweb1 kernel: EIP: 0010:[prune_dcache+124/400]
Jan 9 04:06:23 dnweb1 kernel: EIP: 0010:[<c0150c9c>]
Jan 9 04:06:23 dnweb1 kernel: EFLAGS: 00010282
Jan 9 04:06:23 dnweb1 kernel: eax: 0000001c ebx: f33ab558 ecx: c026059c edx: 0000789a
Jan 9 04:06:23 dnweb1 kernel: esi: f33ab540 edi: c2116148 ebp: ffffe5c0 esp: c22dbf70
Jan 9 04:06:23 dnweb1 kernel: ds: 0018 es: 0018 ss: 0018
Jan 9 04:06:23 dnweb1 kernel: Process kswapd (pid: 5, stackpage=c22db000)
Jan 9 04:06:23 dnweb1 kernel: Stack: c0248661 00000160 ffffffff 00000000 c0261f40 00000000 00000001 00000851
Jan 9 04:06:23 dnweb1 kernel: c013489d 00000001 00000001 000000c0 00000000 0008e000 c01510c1 00000000
Jan 9 04:06:23 dnweb1 kernel: c0134b97 00000000 000000c0 c026c100 000000c0 00000000 c0134c2e 000000c0
Jan 9 04:06:23 dnweb1 kernel: Call Trace: [call_spurious_interrupt+127272/150727] [free_shortage+13/48] [shrink_dcache_memory+33/64] [do_try_to_free_pages+39/96] [kswapd+94/272]
Jan 9 04:06:23 dnweb1 kernel: Call Trace: [<c0248661>] [<c013489d>] [<c01510c1>] [<c0134b97>] [<c0134c2e>]
Jan 9 04:06:23 dnweb1 kernel: [_stext+0/96] [_stext+0/96] [kernel_thread+38/48] [kswapd+0/272]
Jan 9 04:06:23 dnweb1 kernel: [<c0105000>] [<c0105000>] [<c0105836>] [<c0134bd0>]
Jan 9 04:06:23 dnweb1 kernel:
Jan 9 04:06:23 dnweb1 kernel: Code: 0f 0b 5f 58 8d 56 10 8b 4a 04 8b 46 10 89 48 04 89 01 89 56

 

[pcorchary]

Sorry - should have also said this is RedHat 7.2 with 2.4.7-10smp kernel on Tyan 2515 motherboard with Pentium III/867 processors.

 

[marsd]

Your best chance on this is to check the kernel mailing list
archives.
There are no serious kernel hackers I've met on this forum.
You could also try a newer kernel and see if the problem disappears of course.

 

[Morsing]

Looks like a kernel bug to me (which it also admits in the first line
!!). Try another kernel.

Cheers Henrik Morsing
Certified AIX 4.3 Systems Administration
& p690 Technical Support