Topic: Kernel panic problem

[Beast]

Hi

At regular intervals (couple of days) one of my servers crash with this Kernel bug.

Anybody know what might cause this?

Thank you in advance.

Apr  9 04:57:04 beastserver kernel: ------------[ cut here ]------------
Apr  9 04:57:04 beastserver kernel: kernel BUG at mm/rmap.c:479!
Apr  9 04:57:04 beastserver kernel: invalid operand: 0000 [#1]
Apr  9 04:57:04 beastserver kernel: SMP
Apr  9 04:57:04 beastserver kernel: Modules linked in: e100 bonding(U) uhci_hcd ehci_hcd mii dm_snapshot dm_zero dm_mirror ext3 jbd raid1 dm_mod aic7xxx sd_mod scsi_mod
Apr  9 04:57:04 beastserver kernel: CPU:    0
Apr  9 04:57:04 beastserver kernel: EIP:    0060:[page_remove_rmap+35/74]    Not tainted VLI
Apr  9 04:57:04 beastserver kernel: EIP:    0060:[<c0152ad9>]    Not tainted VLI
Apr  9 04:57:04 beastserver kernel: EFLAGS: 00010286   (2.6.9-42.0.10.ELsmp)
Apr  9 04:57:04 beastserver kernel: EIP is at page_remove_rmap+0x23/0x4a
Apr  9 04:57:04 beastserver kernel: eax: ffffffff   ebx: 000b7a40   ecx: c14071c0   edx: c10b7a40
Apr  9 04:57:04 beastserver kernel: esi: 00000000   edi: dd922248   ebp: c19a2b98   esp: df24cdd8
Apr  9 04:57:04 beastserver kernel: ds: 007b   es: 007b   ss: 0068
Apr  9 04:57:05 beastserver kernel: Process spamd (pid: 3267, threadinfo=df24c000 task=dda2e070)
Apr  9 04:57:05 beastserver kernel: Stack: c014c84c 05bd2067 00000000 c10b7a40 00026000 0934d000 c14071c0 00000246
Apr  9 04:57:05 beastserver kernel:        c0143fc0 0934d000 093cd000 dd922250 c14071c0 c014c96e 00080000 00000000
Apr  9 04:57:05 beastserver kernel:        0934d000 de6e28a8 093cd000 c14071c0 c014c9cd 00080000 00000000 df24ce90
Apr  9 04:57:05 beastserver kernel: Call Trace:
Apr  9 04:57:05 beastserver kernel:  [zap_pte_range+640/841] zap_pte_range+0x280/0x349
Apr  9 04:57:05 beastserver kernel:  [<c014c84c>] zap_pte_range+0x280/0x349
Apr  9 04:57:05 beastserver kernel:  [buffered_rmqueue+381/421] buffered_rmqueue+0x17d/0x1a5
Apr  9 04:57:05 beastserver kernel:  [<c0143fc0>] buffered_rmqueue+0x17d/0x1a5
Apr  9 04:57:05 beastserver kernel:  [zap_pmd_range+89/124] zap_pmd_range+0x59/0x7c
Apr  9 04:57:05 beastserver kernel:  [<c014c96e>] zap_pmd_range+0x59/0x7c
Apr  9 04:57:05 beastserver kernel:  [unmap_page_range+60/95] unmap_page_range+0x3c/0x5f
Apr  9 04:57:05 beastserver kernel:  [<c014c9cd>] unmap_page_range+0x3c/0x5f
Apr  9 04:57:05 beastserver kernel:  [unmap_vmas+241/517] unmap_vmas+0xf1/0x205
Apr  9 04:57:05 beastserver kernel:  [<c014cae1>] unmap_vmas+0xf1/0x205
Apr  9 04:57:05 beastserver kernel:  [exit_mmap+121/328] exit_mmap+0x79/0x148
Apr  9 04:57:05 beastserver kernel:  [<c0150e01>] exit_mmap+0x79/0x148
Apr  9 04:57:05 beastserver kernel:  [mmput+78/114] mmput+0x4e/0x72
Apr  9 04:57:05 beastserver kernel:  [<c012079c>] mmput+0x4e/0x72
Apr  9 04:57:05 beastserver kernel:  [do_exit+527/1028] do_exit+0x20f/0x404
Apr  9 04:57:05 beastserver kernel:  [<c0124739>] do_exit+0x20f/0x404
Apr  9 04:57:05 beastserver kernel:  [sys_exit_group+0/13] sys_exit_group+0x0/0xd
Apr  9 04:57:05 beastserver kernel:  [<c0124a19>] sys_exit_group+0x0/0xd
Apr  9 04:57:05 beastserver kernel:  [get_signal_to_deliver+798/838] get_signal_to_deliver+0x31e/0x346
Apr  9 04:57:05 beastserver kernel:  [<c012cd46>] get_signal_to_deliver+0x31e/0x346
Apr  9 04:57:05 beastserver kernel:  [do_signal+85/217] do_signal+0x55/0xd9
Apr  9 04:57:05 beastserver kernel:  [<c0105bd4>] do_signal+0x55/0xd9
Apr  9 04:57:05 beastserver kernel:  [udp_ioctl+0/197] udp_ioctl+0x0/0xc5
Apr  9 04:57:05 beastserver kernel:  [<c02b4d3b>] udp_ioctl+0x0/0xc5
Apr  9 04:57:05 beastserver kernel:  [recalc_task_prio+296/307] recalc_task_prio+0x128/0x133
Apr  9 04:57:05 beastserver kernel:  [<c011cd26>] recalc_task_prio+0x128/0x133
Apr  9 04:57:05 beastserver kernel:  [schedule+2109/2267] schedule+0x83d/0x8db
Apr  9 04:57:05 beastserver kernel:  [<c02d27c5>] schedule+0x83d/0x8db
Apr  9 04:57:05 beastserver kernel:  [schedule+2157/2267] schedule+0x86d/0x8db
Apr  9 04:57:05 beastserver kernel:  [<c02d27f5>] schedule+0x86d/0x8db
Apr  9 04:57:05 beastserver kernel:  [sys_socketcall+337/507] sys_socketcall+0x151/0x1fb
Apr  9 04:57:05 beastserver kernel:  [<c0279a65>] sys_socketcall+0x151/0x1fb
Apr  9 04:57:05 beastserver kernel:  [do_page_fault+0/1478] do_page_fault+0x0/0x5c6
Apr  9 04:57:05 beastserver kernel:  [<c011ae55>] do_page_fault+0x0/0x5c6
Apr  9 04:57:05 beastserver kernel:  [do_notify_resume+40/56] do_notify_resume+0x28/0x38
Apr  9 04:57:05 beastserver kernel:  [<c0105c80>] do_notify_resume+0x28/0x38
Apr  9 04:57:05 beastserver kernel:  [work_notifysig+19/21] work_notifysig+0x13/0x15
Apr  9 04:57:05 beastserver kernel:  [<c02d4966>] work_notifysig+0x13/0x15
Apr  9 04:57:05 beastserver kernel:  [packet_rcv+70/775] packet_rcv+0x46/0x307
Apr  9 04:57:05 beastserver kernel:  [<c02d007b>] packet_rcv+0x46/0x307
Apr  9 04:57:05 beastserver kernel: Code: 3c c0 ff 42 10 51 9d c3 89 c2 8b 00 f6 c4 08 74 08 0f 0b dc 01 ad 8d 2e c0 f0 83 42 08 ff 0f 98 c0 84 c0 74 2c 8b 42 08 40 79 08 <0f> 0b df 01 ad 8d 2e c0 9c 59 fa b8 00 f0 ff ff 21 e0 8b 40 10
Apr  9 04:57:05 beastserver kernel:  <0>Fatal exception: panic in 5 seconds
Apr  9 04:57:05 beastserver kernel: bad: scheduling while atomic!
Apr  9 04:57:05 beastserver kernel:  [schedule+45/2267] schedule+0x2d/0x8db
Apr  9 04:57:05 beastserver kernel:  [<c02d1fb5>] schedule+0x2d/0x8db
Apr  9 04:57:05 beastserver kernel:  [__mod_timer+257/267] __mod_timer+0x101/0x10b
Apr  9 04:57:05 beastserver kernel:  [<c0129e39>] __mod_timer+0x101/0x10b
Apr  9 04:57:05 beastserver kernel:  [poke_blanked_console+143/154] poke_blanked_console+0x8f/0x9a
Apr  9 04:57:05 beastserver kernel:  [<c020c668>] poke_blanked_console+0x8f/0x9a
Apr  9 04:57:05 beastserver kernel:  [vt_console_print+660/677] vt_console_print+0x294/0x2a5
Apr  9 04:57:05 beastserver kernel:  [<c020ba09>] vt_console_print+0x294/0x2a5
Apr  9 04:57:05 beastserver kernel:  [__mod_timer+257/267] __mod_timer+0x101/0x10b
Apr  9 04:57:05 beastserver kernel:  [<c0129e39>] __mod_timer+0x101/0x10b
Apr  9 04:57:05 beastserver kernel:  [schedule_timeout+313/340] schedule_timeout+0x139/0x154
Apr  9 04:57:05 beastserver kernel:  [<c02d30d1>] schedule_timeout+0x139/0x154
Apr  9 04:57:05 beastserver kernel:  [process_timeout+0/5] process_timeout+0x0/0x5
Apr  9 04:57:05 beastserver kernel:  [<c012a6de>] process_timeout+0x0/0x5
Apr  9 04:57:05 beastserver kernel:  [printk+14/17] printk+0xe/0x11
Apr  9 04:57:05 beastserver kernel:  [<c01228ac>] printk+0xe/0x11
Apr  9 04:57:05 beastserver kernel:  [die+346/363] die+0x15a/0x16b
Apr  9 04:57:05 beastserver kernel:  [<c01060c2>] die+0x15a/0x16b
Apr  9 04:57:05 beastserver kernel:  [do_invalid_op+207/242] do_invalid_op+0xcf/0xf2
Apr  9 04:57:05 beastserver kernel:  [<c0106425>] do_invalid_op+0xcf/0xf2
Apr  9 04:57:05 beastserver kernel:  [free_pages_bulk+459/471] free_pages_bulk+0x1cb/0x1d7
Apr  9 04:57:05 beastserver kernel:  [<c01439b8>] free_pages_bulk+0x1cb/0x1d7
Apr  9 04:57:05 beastserver kernel:  [page_remove_rmap+35/74] page_remove_rmap+0x23/0x4a
Apr  9 04:57:05 beastserver kernel:  [<c0152ad9>] page_remove_rmap+0x23/0x4a
Apr  9 04:57:05 beastserver kernel:  [free_hot_cold_page+186/236] free_hot_cold_page+0xba/0xec
Apr  9 04:57:05 beastserver kernel:  [<c0143e00>] free_hot_cold_page+0xba/0xec
Apr  9 04:57:05 beastserver kernel:  [__pagevec_free+21/26] __pagevec_free+0x15/0x1a
Apr  9 04:57:05 beastserver kernel:  [<c0144304>] __pagevec_free+0x15/0x1a
Apr  9 04:57:05 beastserver kernel:  [release_pages+315/323] release_pages+0x13b/0x143
Apr  9 04:57:05 beastserver kernel:  [<c0148e8b>] release_pages+0x13b/0x143
Apr  9 04:57:05 beastserver kernel:  [do_invalid_op+0/242] do_invalid_op+0x0/0xf2
Apr  9 04:57:05 beastserver kernel:  [<c0106356>] do_invalid_op+0x0/0xf2
Apr  9 04:57:05 beastserver kernel:  [error_code+47/56] error_code+0x2f/0x38
Apr  9 04:57:05 beastserver kernel:  [<c02d53fb>] error_code+0x2f/0x38
Apr  9 04:57:05 beastserver kernel:  [page_remove_rmap+35/74] page_remove_rmap+0x23/0x4a
Apr  9 04:57:05 beastserver kernel:  [<c0152ad9>] page_remove_rmap+0x23/0x4a
Apr  9 04:57:05 beastserver kernel:  [zap_pte_range+640/841] zap_pte_range+0x280/0x349
Apr  9 04:57:05 beastserver kernel:  [<c014c84c>] zap_pte_range+0x280/0x349
Apr  9 04:57:05 beastserver kernel:  [buffered_rmqueue+381/421] buffered_rmqueue+0x17d/0x1a5
Apr  9 04:57:05 beastserver kernel:  [<c0143fc0>] buffered_rmqueue+0x17d/0x1a5
Apr  9 04:57:05 beastserver kernel:  [zap_pmd_range+89/124] zap_pmd_range+0x59/0x7c
Apr  9 04:57:05 beastserver kernel:  [<c014c96e>] zap_pmd_range+0x59/0x7c
Apr  9 04:57:05 beastserver kernel:  [unmap_page_range+60/95] unmap_page_range+0x3c/0x5f
Apr  9 04:57:05 beastserver kernel:  [unmap_vmas+241/517] unmap_vmas+0xf1/0x205
Apr  9 04:57:05 beastserver kernel:  [<c014cae1>] unmap_vmas+0xf1/0x205
Apr  9 04:57:05 beastserver kernel:  [exit_mmap+121/328] exit_mmap+0x79/0x148
Apr  9 04:57:05 beastserver kernel:  [<c0150e01>] exit_mmap+0x79/0x148
Apr  9 04:57:05 beastserver kernel:  [mmput+78/114] mmput+0x4e/0x72
Apr  9 04:57:05 beastserver kernel:  [<c012079c>] mmput+0x4e/0x72
Apr  9 04:57:05 beastserver kernel:  [do_exit+527/1028] do_exit+0x20f/0x404
Apr  9 04:57:05 beastserver kernel:  [<c0124739>] do_exit+0x20f/0x404
Apr  9 04:57:05 beastserver kernel:  [sys_exit_group+0/13] sys_exit_group+0x0/0xd
Apr  9 04:57:05 beastserver kernel:  [<c0124a19>] sys_exit_group+0x0/0xd
Apr  9 04:57:05 beastserver kernel:  [get_signal_to_deliver+798/838] get_signal_to_deliver+0x31e/0x346
Apr  9 04:57:05 beastserver kernel:  [<c012cd46>] get_signal_to_deliver+0x31e/0x346
Apr  9 04:57:05 beastserver kernel:  [do_signal+85/217] do_signal+0x55/0xd9
Apr  9 04:57:05 beastserver kernel:  [<c0105bd4>] do_signal+0x55/0xd9
Apr  9 04:57:05 beastserver kernel:  [udp_ioctl+0/197] udp_ioctl+0x0/0xc5
Apr  9 04:57:05 beastserver kernel:  [<c02b4d3b>] udp_ioctl+0x0/0xc5
Apr  9 04:57:05 beastserver kernel:  [recalc_task_prio+296/307] recalc_task_prio+0x128/0x133
Apr  9 04:57:05 beastserver kernel:  [<c011cd26>] recalc_task_prio+0x128/0x133
Apr  9 04:57:05 beastserver kernel:  [schedule+2109/2267] schedule+0x83d/0x8db
Apr  9 04:57:05 beastserver kernel:  [<c02d27c5>] schedule+0x83d/0x8db
Apr  9 04:57:05 beastserver kernel:  [schedule+2157/2267] schedule+0x86d/0x8db
Apr  9 04:57:05 beastserver kernel:  [<c02d27f5>] schedule+0x86d/0x8db
Apr  9 04:57:05 beastserver kernel:  [sys_socketcall+337/507] sys_socketcall+0x151/0x1fb
Apr  9 04:57:05 beastserver kernel:  [<c0279a65>] sys_socketcall+0x151/0x1fb
Apr  9 04:57:05 beastserver kernel:  [do_page_fault+0/1478] do_page_fault+0x0/0x5c6
Apr  9 04:57:05 beastserver kernel:  [<c011ae55>] do_page_fault+0x0/0x5c6
Apr  9 04:57:05 beastserver kernel:  [do_notify_resume+40/56] do_notify_resume+0x28/0x38
Apr  9 04:57:05 beastserver kernel:  [<c0105c80>] do_notify_resume+0x28/0x38
Apr  9 04:57:05 beastserver kernel:  [work_notifysig+19/21] work_notifysig+0x13/0x15
Apr  9 04:57:05 beastserver kernel:  [<c02d4966>] work_notifysig+0x13/0x15
Apr  9 04:57:05 beastserver kernel:  [packet_rcv+70/775] packet_rcv+0x46/0x307
Apr  9 04:57:05 beastserver kernel:  [<c02d007b>] packet_rcv+0x46/0x307

[bpivk]

Report this to the bugtracker.

[compdoc]

SME is pretty stable on its own, but hardware can have problems, as does software you might have added thats not included with SME. Bad ram or conflicts with the PCI cards happen often.

I would try creating a boot disk using this ram test software:

http://oca.microsoft.com/en/windiag.asp

Dont worry, it doesnt require Windows or anything. Its just an excellent ram test that has caught several bad sticks of ram for me. I run it on all the systems I build.

If you run it thru the extended tests once or twice with no errors, your system is good, but you can still have a problem with the other hardware like the nics or hard drive.