[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 I'm turning myself from a verbose senior citizen, to an efficient system admin, with customer support experience. Attached to this comment is a short extract of /var/log/kern.log, with only the lines, relevent to this issue (and 1215513). Reminder that I'm running Ubuntu 12.0.4 LTS Server, with Kernel vmlinuz-3.2.0-53-generic-pae. Thank you and best regards, Kenneth Parker, Seattle, WA ** Attachment added: Short extract from /var/log/kern.log. See comment text. https://bugs.launchpad.net/ubuntu/+source/linux-lts-raring/+bug/1217189/+attachment/3835571/+files/kern_log_pico -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 I STRONGLY suggest that this is NOT a duplicate of bug #1215513, as a fix was distributed that fixes the System Locks Up part, but leaves this error message. In my first comment, both on this Bug and on Bug #1215513, I responded to the error message by entering fdisk /dev/ram0, under root, followed by p, which showed it to never be partitioned, or anything (like a SWAP partition being defined). So it LOOKS like I was never in danger of bug #1215513, but only experiencing the messages, noted in this Bug (#1217189). Even though no actual harm is done, through a pure experience of Bug # 1217189, the error messages still appear, after fix of #1215513, which can CERTAINLY alarm production Linux administrators anywhere, and cause loss of money in any case where the Server is anything but something assisting non-profit volunteer work, where they can be told they need to be patient and wait for their services. (Actually, due to an early message by dac922, I was able to disable zram services on a system that has no intention of using them). Obviously, what happened was that the Kernel 3.8 work, IMPLEMENTING zram0 swap was back-ported to the 3.2 Kernel tree, somewhere = vmlinuz-3.2.0-53-generic-pae!!! :-O Remember, my system is Ubuntu 12.0.4 LTS Server, which, in my opinion is not in any condition for stray zram swap creation! Fortunately, somebody ported the package zram-config to 12.0.4, allowing me to get it, which, in effect PERMANENTLY DISABLES the zram0 processes, because they fail, during the install of zram-config, allowing apt-get upgrade to state that it was not successful in the install of this package. So I suggest that somebody on this forum, in either of these Bug reports (again, I'm too busy administering Linux to normally submit fixes!) put some of this text in some FAQ file somewhere, Forgive my dry humor in this post. As a Linux admin, I'm trained to roll with the punches and to consider the humor of life on Planet Earth (and, forgive me for adding) the political system in the USA!!! :-) Thank you and best regards, Kenneth Parker, Seattle, WA -- I'm a Troubleshooter. I look for Trouble and Shoot It! :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 Something to add to prior comment: Ubuntu 12.0.4 Server, running in Text mode (at least for now, as I have not brought up FVWM yet, due to this error. I'm thinking the hard stop in 1215513 is because of attempts to run a desktop. Thank you and best regards, Kenneth Parker, Seattle, WA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 I got this, right after apt-get upgrade (plus direct installs of kernel). The message shows up on bootup. My system has not locked up yet, which is why I prefer this to bug 1215513. In my case, the Logical Block is 314223. I did (under root): fdisk /dev/ram0, followed by p. This shows up, as if it's a hard disk: 255 heads, 63 sectors/track, 13 cylinders, total 314224 sectors. Note that total sectors is one higher than the logical block the error message is complaining about. Is it as simple as to find the script under the ramdisk part of bootup that sets up zram0, and decreasing the number of sectors? Thank you and best regards, Kenneth Parker, Seattle, WA -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 I also posted comments in Bug #1215513. I got a workaround there: service zram-config stop. I posted a question about what script (probably in the ramdisk portion of the boot) sets up zram0, so I can possibly edit it. Alternatively, the fix for #1215513 may fix this script, but I'm too much in production to try development kernels. I've signed up for email updates for both this and issue #1215513, so hopefully, I'm covered, when the fix gets to the stable 12.0.4 LTS version. Thank you and best regards, Kenneth Parker, Seattle, WA -- I'm a Troubleshooter. I look for Trouble and Shoot it! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage:
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
*** This bug is a duplicate of bug 1215513 *** https://bugs.launchpad.net/bugs/1215513 ** This bug has been marked a duplicate of bug 1215513 System locks up, requires hard reset -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
I am also having this issue on 3.2.0-53-powerpc-smp . Rather than reverting a commit, there is a patch on LKML: https://lkml.org/lkml/2013/8/12/399 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
The bug seems to affect also Kubuntu 13.04 - Kernel version 3.8.0-29 Kubuntu 13.04 - Kernel version 3.8.0-30 No problem with 3.8.0-28 kernel... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
Damian, I believe you refer to 3.2.0-54.82, which is the 12.04 kernel currently in the -proposed pocket. This kernel should already contain the fix for this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
This seems to be a duplicate of bug #1215513. Could the people running Raring try the test kernel here: http://people.canonical.com/~henrix/lp1215513/ (there are 64bits and 32bits kernels) The faulty commit has been reverted in all the kernels (including Precise and Quantal). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1:
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
@henrix Is 3.2.0.54 already bug-free (for 12.04)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 44' Mixer name : 'SigmaTel
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
Like Hans, I'm seeing this on 12.04 LTS. linux-image-3.2.0-53-generic- pae seems to enable zram by default, which results in lots of scheduling while atomic errors in syslog and occasional lockups (machine still responds to ping, but not ssh, desktop frozen.) This seems like a pretty critical problem now that it's affecting current LTS.. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: New Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1217189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
apport information ** Tags added: apport-collected staging ** Description changed: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) + --- + AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. + ApportVersion: 2.0.1-0ubuntu17.4 + Architecture: i386 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: muresan 29305 F pulseaudio + /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio + /dev/snd/controlC1: muresan 29305 F pulseaudio + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + Card0.Amixer.info: + Card hw:0 'Intel'/'HDA Intel at 0xfebfc000 irq 44' +Mixer name : 'SigmaTel STAC9205' +Components : 'HDA:838476a0,102801f1,00100204 HDA:14f12c06,14f1000f,0010' +Controls : 26 +Simple ctrls : 12 + Card1.Amixer.info: + Card hw:1 'USB'/'E-MU Systems, Inc. E-MU 0202 | USB at usb-:00:1d.0-2, full speed' +Mixer name : 'USB Mixer' +Components : 'USB041e:3f02' +Controls : 4 +
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
This bug also occurs on linux-lts-quantal, I think (I remember booting to a lts-quantal kernel after seeing the raring bug). There was a backport to zram on both branches that is causing this. Note that in Bug #1218278, Tim Gardner (timg-tpi) wrote at #19: There will be a linux-lts-saucy shortly after 13.10 is released.; anyway, I'm marking that one as a duplicate. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F
[Kernel-packages] [Bug 1217189] Re: Buffer I/O error on device zram0 (possibly causing complete machine lockup)
meanwhile: rolling back to kernel 3.2.0.52 - can't wait 'til release of 13.10 - error is critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1217189 Title: Buffer I/O error on device zram0 (possibly causing complete machine lockup) Status in “linux” package in Ubuntu: Confirmed Status in “linux-lts-raring” package in Ubuntu: Confirmed Bug description: This is on linux-image-generic-lts-raring (which I recently upgraded to 3.8.0-29; the problem didn't occur before upgrading AFAIR) I see this junk in my dmesg when creating / formatting a zram swap, and then periodically. Then at some point after heavy swapping incidents, the machine locks up. Correlation does not imply causation, but it does waggle its eyebrows suggestively and all that. --- zram: module is from the staging directory, the quality is unknown, you have been warned. zram: num_devices not specified. Using default: 1 zram: Creating 1 devices Adding 1031648k swap on /dev/zram0. Priority:100 extents:1 across:1031648k SS ... Buffer I/O error on device zram0, logical block 257912 [repeated 10 times] ... BUG: scheduling while atomic: rsyslogd/1439/0x0001 Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796635] Pid: 1439, comm: rsyslogd Tainted: PF WC O 3.8.0-29-generic #42~precise1-Ubuntu [20931.796638] Call Trace: [20931.796649] [c1619449] __schedule_bug+0x52/0x5e [20931.796653] [c162c265] __schedule+0x575/0x5f0 [20931.796660] [f8439e06] ? zram_make_request+0xe6/0x100 [zram] [20931.79] [c111c38d] ? release_pages+0x18d/0x1c0 [20931.796669] [c162c573] schedule+0x23/0x60 [20931.796673] [c162d0fd] rwsem_down_failed_common+0x9d/0xf0 [20931.796677] [c162d162] rwsem_down_write_failed+0x12/0x20 [20931.796681] [c12f809a] call_rwsem_down_write_failed+0x6/0x8 [20931.796685] [c162ba44] ? down_write+0x24/0x30 [20931.796689] [f8439169] zram_slot_free_notify+0x29/0x50 [zram] [20931.796693] [f8439140] ? zram_stat64_inc+0x30/0x30 [zram] [20931.796700] [c11460bc] swap_entry_free+0xdc/0x170 [20931.796703] [c162d100] ? rwsem_down_failed_common+0xa0/0xf0 [20931.796708] [c1146458] swap_free+0x28/0x40 [20931.796712] [c1134ba0] do_swap_page+0x390/0x6f0 [20931.796717] [c10180f8] ? sched_clock+0x8/0x10 [20931.796721] [c11365aa] handle_pte_fault+0x21a/0x2b0 [20931.796726] [c10451e1] ? kmap_atomic_prot+0xf1/0x120 [20931.796730] [c113746a] handle_mm_fault+0x1fa/0x2d0 [20931.796735] [c1630ad0] __do_page_fault+0x190/0x4f0 [20931.796740] [c12f63bc] ? sprintf+0x1c/0x20 [20931.796744] [c104c132] ? print_time.part.4+0x82/0xc0 [20931.796748] [c1630e30] ? __do_page_fault+0x4f0/0x4f0 [20931.796752] [c1630e3d] do_page_fault+0xd/0x10 [20931.796756] [c162dc17] error_code+0x67/0x6c [20931.796759] [c12f8716] ? __copy_to_user_ll+0x46/0x70 [20931.796763] [c12f8970] copy_to_user+0x40/0x60 [20931.796767] [c104e218] syslog_print+0xc8/0x210 [20931.796770] [c104eae6] do_syslog+0x206/0x390 [20931.796775] [c106d570] ? add_wait_queue+0x50/0x50 [20931.796780] [c11c3680] ? kmsg_poll+0x50/0x50 [20931.796784] [c11c36d0] kmsg_read+0x50/0x60 [20931.796788] [c11b6584] proc_reg_read+0x64/0xa0 [20931.796793] [c116469c] vfs_read+0x8c/0x160 [20931.796797] [c10a898d] ? sys_futex+0xed/0x130 [20931.796801] [c11b6520] ? proc_reg_write+0xa0/0xa0 [20931.796805] [c11647b7] sys_read+0x47/0x80 ... [30855.181542] Write-error on swap-device (251:0:131064) [43457.030155] Write-error on swap-device (251:0:131064) [43705.090381] Buffer I/O error on device zram0, logical block 16383 Anyway, there's a couple of lkml messages related to this Buffer I/O error on device zram0, please investigate ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.8.0-29-generic 3.8.0-29.42~precise1 ProcVersionSignature: Ubuntu 3.8.0-29.42~precise1-generic 3.8.13.5 Uname: Linux 3.8.0-29-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 Date: Tue Aug 27 07:33:37 2013 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: TERM=rxvt LC_COLLATE=C PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-raring UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k3.8.0-29-lowlatency. ApportVersion: 2.0.1-0ubuntu17.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: muresan 29305 F pulseaudio /dev/snd/pcmC0D0p: muresan 29305 F...m pulseaudio /dev/snd/controlC1: muresan 29305 F pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at
