[hardy] Bad page state in process 'kswapd0'

Hi mlind,

I noticed the following: "Trying to fix it up, but a reboot is needed". After a reboot, does the issue reappear? Also how reproducible is the issue? Thanks.

I am getting exacltly the same issue since upgrading from Gutsy to Hardy: From time to time X just freezes - it even no longer reacts on Ctrl+Backspace. This is what I found in /var/log/kern.log:

May 11 15:29:37 andromeda kernel: [104373.352473] Bad page state in process 'kswapd0'
May 11 15:29:37 andromeda kernel: [104373.352476] page:ffff81007fdd44d8 flags:0x0100000000010008 mapping:0000000000000000 mapcount:-1 count:0
May 11 15:29:37 andromeda kernel: [104373.352477] Trying to fix it up, but a reboot is needed
May 11 15:29:37 andromeda kernel: [104373.352479] Backtrace:
May 11 15:29:37 andromeda kernel: [104373.352488] Pid: 193, comm: kswapd0 Tainted: P B D 2.6.24-16-generic #1
May 11 15:29:37 andromeda kernel: [104373.352490]
May 11 15:29:37 andromeda kernel: [104373.352491] Call Trace:
May 11 15:29:37 andromeda kernel: [104373.352530] [bad_page+0x60/0xa0] bad_page+0x60/0xa0
May 11 15:29:37 andromeda kernel: [104373.352538] [free_hot_cold_page+0x18c/0x1a0] free_hot_cold_page+0x18c/0x1a0
May 11 15:29:37 andromeda kernel: [104373.352547] [__pagevec_free+0x24/0x30] __pagevec_free+0x24/0x30
May 11 15:29:37 andromeda kernel: [104373.352554] [__pagevec_release_nonlru+0x62/0x70] __pagevec_release_nonlru+0x62/0x70
May 11 15:29:37 andromeda kernel: [104373.352575] [shrink_page_list+0x27a/0x650] shrink_page_list+0x27a/0x650
May 11 15:29:37 andromeda kernel: [104373.352600] [isolate_lru_pages+0x8a/0x210] isolate_lru_pages+0x8a/0x210
May 11 15:29:37 andromeda kernel: [104373.352619] [shrink_inactive_list+0x149/0x3f0] shrink_inactive_list+0x149/0x3f0
May 11 15:29:37 andromeda kernel: [104373.352660] [shrink_zone+0xbc/0x130] shrink_zone+0xbc/0x130
May 11 15:29:37 andromeda kernel: [104373.352670] [kswapd+0x508/0x560] kswapd+0x508/0x560
May 11 15:29:37 andromeda kernel: [104373.352693] [<ffffffff80253960>] autoremove_wake_function+0x0/0x30
May 11 15:29:37 andromeda kernel: [104373.352707] [kswapd+0x0/0x560] kswapd+0x0/0x560
May 11 15:29:37 andromeda kernel: [104373.352713] [kthread+0x4b/0x80] kthread+0x4b/0x80
May 11 15:29:37 andromeda kernel: [104373.352721] [child_rip+0xa/0x12] child_rip+0xa/0x12
May 11 15:29:37 andromeda kernel: [104373.352740] [kthread+0x0/0x80] kthread+0x0/0x80
May 11 15:29:37 andromeda kernel: [104373.352744] [child_rip+0x0/0x12] child_rip+0x0/0x12
May 11 15:29:37 andromeda kernel: [104373.352751]
May 11 19:48:33 andromeda kernel: [119883.430863] lp0: ECP mode
May 11 19:48:44 andromeda kernel: [119895.036644] DMA write timed out
May 11 20:37:18 andromeda kernel: [122803.950634] hub 4-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
May 11 20:37:18 andromeda kernel: [122803.950642] usb 4-2: USB disconnect, address 3
May 11 20:37:18 andromeda kernel: [122804.062375] usb 4-2: new full speed USB device using uhci_hcd and address 4
May 11 20:37:18 andromeda kernel: [122804.233502] usb 4-2: configuration #1 chosen from 1 choice

or:

May 11 14:33:43 andromeda kernel: [101025.288336] lp0: ECP mode
May 11 15:29:37 andromeda kernel: [104373.352473] Bad page state in process 'kswapd0'
May 11 15:29:37 andromeda kernel: [104373.352476] page:ffff81007fdd44d8 flags:0x0100000000010008 map...

I forgot to add that a hard reset is required to recover from the error...

Oops... Just noticed that I erroneusly posted the same snippet from kern.log twice... Another example:

May 11 13:33:47 andromeda kernel: [97434.661056] Bad page state in process 'kvm'
May 11 13:33:47 andromeda kernel: [97434.661057] page:ffff81007fdd44d8 flags:0x0100000000000014 mapping:0000000000000000 mapcount:1 count:0
May 11 13:33:47 andromeda kernel: [97434.661058] Trying to fix it up, but a reboot is needed
May 11 13:33:47 andromeda kernel: [97434.661059] Backtrace:
May 11 13:33:47 andromeda kernel: [97434.661065] Pid: 21914, comm: kvm Tainted: P 2.6.24-16-generic #1
May 11 13:33:47 andromeda kernel: [97434.661067]
May 11 13:33:47 andromeda kernel: [97434.661067] Call Trace:
May 11 13:33:47 andromeda kernel: [97434.661091] [bad_page+0x60/0xa0] bad_page+0x60/0xa0
May 11 13:33:47 andromeda kernel: [97434.661096] [free_hot_cold_page+0x18c/0x1a0] free_hot_cold_page+0x18c/0x1a0
May 11 13:33:47 andromeda kernel: [97434.661110] [kvm:rmap_remove+0xd8/0x1e0] :kvm:rmap_remove+0xd8/0x1e0
May 11 13:33:47 andromeda kernel: [97434.661120] [kvm:kvm_mmu_zap_page+0x2a4/0x2b0] :kvm:kvm_mmu_zap_page+0x2a4/0x2b0
May 11 13:33:47 andromeda kernel: [97434.661131] [kvm:kvm_mmu_pte_write+0x193/0x840] :kvm:kvm_mmu_pte_write+0x193/0x840
May 11 13:33:47 andromeda kernel: [97434.661135] [__up_read+0x21/0xb0] __up_read+0x21/0xb0
May 11 13:33:47 andromeda kernel: [97434.661145] [kvm:mark_page_dirty+0x24/0x60] :kvm:mark_page_dirty+0x24/0x60
May 11 13:33:47 andromeda kernel: [97434.661165] [kvm:emulator_write_emulated_onepage+0xcd/0x170] :kvm:emulator_write_emulated_onepage+0xcd/0x170
May 11 13:33:47 andromeda kernel: [97434.661176] [kvm:x86_emulate_insn+0x3ba/0x4270] :kvm:x86_emulate_insn+0x3ba/0x4270
May 11 13:33:47 andromeda kernel: [97434.661191] [kvm:emulate_instruction+0x1b6/0x330] :kvm:emulate_instruction+0x1b6/0x330
May 11 13:33:47 andromeda kernel: [97434.661202] [kvm:kvm_mmu_page_fault+0x58/0x90] :kvm:kvm_mmu_page_fault+0x58/0x90
May 11 13:33:47 andromeda kernel: [97434.661213] [kvm:kvm_arch_vcpu_ioctl_run+0x147/0x620] :kvm:kvm_arch_vcpu_ioctl_run+0x147/0x620
May 11 13:33:47 andromeda kernel: [97434.661223] [kvm:kvm_vcpu_ioctl+0x33d/0x350] :kvm:kvm_vcpu_ioctl+0x33d/0x350
May 11 13:33:47 andromeda kernel: [97434.661233] [do_wp_page+0x23f/0x510] do_wp_page+0x23f/0x510
May 11 13:33:47 andromeda kernel: [97434.661243] [handle_mm_fault+0x594/0x7b0] handle_mm_fault+0x594/0x7b0
May 11 13:33:47 andromeda kernel: [97434.661251] [add_partial_tail+0x19/0x60] add_partial_tail+0x19/0x60
May 11 13:33:47 andromeda kernel: [97434.661255] [__up_read+0x21/0xb0] __up_read+0x21/0xb0
May 11 13:33:47 andromeda kernel: [97434.661265] [kvm:kvm_vm_ioctl+0x85/0x200] :kvm:kvm_vm_ioctl+0x85/0x200
May 11 13:33:47 andromeda kernel: [97434.661278] [do_ioctl+0x2f/0xa0] do_ioctl+0x2f/0xa0
May 11 13:33:47 andromeda kernel: [97434.661282] [vfs_ioctl+0x220/0x2c0] vfs_ioctl+0x220/0x2c0
May 11 13:33:47 andromeda kernel: [97434.661289] [sys_ioctl+0x91/0xb0] sys_ioctl+0x91/0xb0
May 11 13:33:47 andromeda kernel: [97434.661297] [system_call+0x7e/0x83] system_call+0x7e/0x83
May 11 13:33:47 androme...

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

This bug was reported a while ago but there hasn't been any recent comments or updates. Is this still reproducible in Hardy with the updates applied? Is this still an issue with the latest pre-release of Jaunty 9.04? Refer to http://www.ubuntu.com/testing/jaunty/beta . Please let us know.

I personally have never experienced this issue again since upgrading to Intrepid, so I consider it solved...

As per the previous comments this appears to be fixed in the Intrepid time frame. Marking this Fix Released.

Will this fix be backported to Hardy, especially the server kernel? We have the same error messages occurring and prefer to stay with the LTS release for stability purposes.

I'm experiencing these errors now under jaunty.

I have the same problem.
I tried 2.6.30-020630-generic and 2.6.31-020631-generic kernels as well and the problem is still visible.
hwinfo -- http://pastebin.com/f73add002
lspci -- http://pastebin.com/f295f5cef

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]