Hi there,
Yesterday one of our highly loaded servers suddenly started reporting
the following kernel bugs:
kernel BUG at page_alloc.c:221!
invalid operand: 0000
CPU: 0
EIP: 0010:[rmqueue+135/576] Not tainted
EFLAGS: 00010006
eax: 00038000 ebx: c13a1350 ecx: 00001000 edx: 55568b11
esi: c03704d0 edi: 00000000 ebp: c0370498 esp: ef4c3e50
ds: 0018 es: 0018 ss: 0018
Process cleanup-mgr (pid: 28856, stackpage=ef4c3000)
Stack: e7504f00 ea23f980 000285df 00000286 00000000 c0370498 c0370498 c0370670
00000002 c03703c0 c01323db 0000000d f73dda20 f73dda2e 00000000 ef4c3f84
c0370570 c0370668 00000000 000001d2 c01434d3 00104025 00000025 cfb8b180
Call Trace: [__alloc_pages+107/640] [link_path_walk+1363/1680]
[do_anonymous_page+94/272] [handle_mm_fault+119/256]
[do_page_fault+392/1277]
[get_empty_filp+76/288] [dentry_open+205/464] [file_ioctl+106/384]
[sys_llseek+173/192] [do_page_fault+0/1277] [error_code+52/60]
Code: 0f 0b dd 00 fb 07 32 c0 8b 53 04 89 dd 8b 03 89 50 04 89 02
kernel BUG at page_alloc.c:221!
invalid operand: 0000
CPU: 0
EIP: 0010:[rmqueue+135/576] Not tainted
EFLAGS: 00010006
eax: 00038000 ebx: c13a1350 ecx: 00001000 edx: 55568b11
esi: c03704d0 edi: 00000000 ebp: c0370498 esp: c6b39e50
ds: 0018 es: 0018 ss: 0018
Process cleanup-run (pid: 28887, stackpage=c6b39000)
Stack: 00000000 c0370498 000088b4 00000286 00000000 c0370498 c0370498 c0370670
00000002 c03703c0 c01323db 0000006d f7df8890 000000f9 f73ddd00 f73dddb4
c0370570 c0370668 00000000 000001d2 e3b212d4 00104025 00000025 f7616180
Call Trace: [__alloc_pages+107/640] [do_anonymous_page+94/272]
[handle_mm_fault+119/256] [do_page_fault+392/1277]
[do_mmap_pgoff+1154/1440]
[old_mmap+212/272] [do_page_fault+0/1277] [error_code+52/60]
Code: 0f 0b dd 00 fb 07 32 c0 8b 53 04 89 dd 8b 03 89 50 04 89 02
The cleanup-mgr process is invoked from cron every 5 minutes and every
time it died. I had to reboot the machine to resume its normal
operation.
As it appeared suddenly and haven't returned after reboot I'm quite
worried about hardware problem - is that possible?
And yeah, it's a custom build 2.4.26 on one of those machines that
you'd better not touch (or, God forbid, upgrade anything!) as long as
they run at least somehow.
Does anyone have any idea what could have caused this bug?
Thx Goo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
