[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
This is getting creepier. Even though as I said in comment #66 I was able to fix this with modprobe i2c-i801, it no longer works after upgrading from 5.0.0-27-generic to 5.0.0-29-generic. However, the fix from comment #16 works. modprobe -r psmouse modprobe psmouse -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838434] [NEW] linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+
Public bug reported: I was happily running my Raspberry Pi 3 B+ with linux- image-5.0.0-1012-raspi2, then upgraded to linux-image-5.0.0-1013-raspi2 and now my system does not boot with the last message as: ---[ end kernel panic - not syncing: Attempted to kill init! exitcode 0x0100 ] Lots of other errors on the screen, but I am having a hard time getting a netconsole or anything to dump these errors somewhere readable. All I can do is attach a screenshot, and maybe type up a few of them. Reverting to 5.0.0-1012 is ok. /init: line 263: log_end_msg: not found /init: line 265: maybe_break: not found /init: line 266: log_begin_msg: not found (skip more of this) /init: line 299: log_end_msg: not foudn mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 (repeat last line three more times) /init: line 323: panic: not found /init: line 325: maybe_break: not found mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory /init: line 359: can't open /root/dev/console: no such file [ 36.246460] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 36.256383] CPU: 0 PID: 1 Comm: init Tainted: G B 5.0.0-1013-raspi2 #13-Ubuntu [ 36.262133] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (D)T [ 36.278383] Call trace: (skip the rest) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "20190731_002622_2.jpg" https://bugs.launchpad.net/bugs/1838434/+attachment/5280023/+files/20190731_002622_2.jpg -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1838434 Title: linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+ Status in linux-raspi2 package in Ubuntu: New Bug description: I was happily running my Raspberry Pi 3 B+ with linux- image-5.0.0-1012-raspi2, then upgraded to linux- image-5.0.0-1013-raspi2 and now my system does not boot with the last message as: ---[ end kernel panic - not syncing: Attempted to kill init! exitcode 0x0100 ] Lots of other errors on the screen, but I am having a hard time getting a netconsole or anything to dump these errors somewhere readable. All I can do is attach a screenshot, and maybe type up a few of them. Reverting to 5.0.0-1012 is ok. /init: line 263: log_end_msg: not found /init: line 265: maybe_break: not found /init: line 266: log_begin_msg: not found (skip more of this) /init: line 299: log_end_msg: not foudn mount: mounting /run on /root/run failed: No such file or directory run-init: current directory on the same filesystem as the root: error 0 Target filesystem doesn't have requested /sbin/init run-init: current directory on the same filesystem as the root: error 0 run-init: current directory on the same filesystem as the root: error 0 (repeat last line three more times) /init: line 323: panic: not found /init: line 325: maybe_break: not found mount: mounting /sys on /root/sys failed: No such file or directory mount: mounting /proc on /root/proc failed: No such file or directory /init: line 359: can't open /root/dev/console: no such file [ 36.246460] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 36.256383] CPU: 0 PID: 1 Comm: init Tainted: G B 5.0.0-1013-raspi2 #13-Ubuntu [ 36.262133] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (D)T [ 36.278383] Call trace: (skip the rest) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
Too bad that the fix mentioned in Comment #4 is now crashing my raspi2 on boot with a kernel panic :( -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Disco: Fix Released Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1825235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
This is reported upstream: https://github.com/raspberrypi/linux/issues/2881 ** Bug watch added: github.com/raspberrypi/linux/issues #2881 https://github.com/raspberrypi/linux/issues/2881 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1825235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832290] [NEW] Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle
Public bug reported: $ uptime 12:40:44 up 1 day, 10:56, 1 user, load average: 4.00, 4.02, 4.00 The load is always reported as higher than 4 even on an idle system. Seems to be this upstream: https://github.com/raspberrypi/linux/issues/2881 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9 ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8 Uname: Linux 5.0.0-1009-raspi2 aarch64 ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 Date: Tue Jun 11 12:33:57 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago) ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1832290 Title: Raspberry Pi 3 B+: Load average always reported as 4.0 even when idle Status in linux-raspi2 package in Ubuntu: New Bug description: $ uptime 12:40:44 up 1 day, 10:56, 1 user, load average: 4.00, 4.02, 4.00 The load is always reported as higher than 4 even on an idle system. Seems to be this upstream: https://github.com/raspberrypi/linux/issues/2881 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1009-raspi2 5.0.0-1009.9 ProcVersionSignature: Ubuntu 5.0.0-1009.9-raspi2 5.0.8 Uname: Linux 5.0.0-1009-raspi2 aarch64 ApportVersion: 2.20.10-0ubuntu27 Architecture: arm64 Date: Tue Jun 11 12:33:57 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-raspi2 UpgradeStatus: Upgraded to disco on 2019-05-22 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1832290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
kmod (25-1ubuntu3) disco; urgency=medium * Drop i2c_i801 from the blacklist again, things work fine with current kernels. (LP: #1786574) -- Timo Aaltonen Thu, 04 Apr 2019 11:30:14 +0300 ... The above fixed it for me. -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722478] Re: Two-finger scrolling no longer works after resuming from suspend
This bug is also present on an X1 Carbon (gen 3). modprobe i2c-i801 after removing it from the blacklist.conf seems to solve the issue. -- 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/1722478 Title: Two-finger scrolling no longer works after resuming from suspend Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I own a Thinkpad T440p onto which I have had Debian 9 running without hardware issues. I have recently installed Ubuntu 17.10 final beta to test it out, but two-finger scrolling does not work at the moment. It used to work out-of-the-box from the final beta iso, but a subsequent update broke it. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ghislain 10620 F pulseaudio /dev/snd/controlC0: ghislain 10620 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 09:20:01 2017 HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e InstallationDate: Installed on 2017-10-05 (4 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: LENOVO 20AN00C1UK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: GLET83WW (2.37 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AN00C1UK dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440p dmi.product.name: 20AN00C1UK dmi.product.version: ThinkPad T440p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1722478/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1063354] Re: Sudden Read-Only Filesystems
Dear All,
I also encountered the same issue with Ubuntu Server 13.04 while I was trying
to checkout all Android projects.
Exactly like TeamFahQ (teamfahq1) wrote on 2013-02-22: #99
--
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/1063354
Title:
Sudden Read-Only Filesystems
Status in “linux” package in Ubuntu:
Confirmed
Bug description:
After upgrading to ubuntu 12.10, I experience sudden locks of my
filesystems (I have a root and a home partition with ext4), in which
the filesystems suddenly become mounted readonly. /var/log/syslog
shows the following entries:
Oct 7 20:00:42 StudioXPS signond[3510]: signondaemon.cpp 345 init Failed to
SUID root. Secure storage will not be available.
Oct 7 20:02:12 StudioXPS kernel: [ 249.193555] ata1.00: exception Emask 0x0
SAct 0x7 SErr 0x0 action 0x0
Oct 7 20:02:12 StudioXPS kernel: [ 249.193561] ata1.00: irq_stat 0x4001
Oct 7 20:02:12 StudioXPS kernel: [ 249.193565] ata1.00: failed command:
READ FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] ata1.00: cmd
60/20:00:90:6f:53/00:00:1a:00:00/40 tag 0 ncq 16384 in
Oct 7 20:02:12 StudioXPS kernel: [ 249.193572] res
41/40:20:98:6f:53/00:00:1a:00:00/40 Emask 0x409 (media error) F
Oct 7 20:02:12 StudioXPS kernel: [ 249.193575] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193578] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193581] ata1.00: failed command:
WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] ata1.00: cmd
61/18:08:18:fb:0e/00:00:2b:00:00/40 tag 1 ncq 12288 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193587] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193590] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193593] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193596] ata1.00: failed command:
WRITE FPDMA QUEUED
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] ata1.00: cmd
61/d8:10:a0:bd:8b/00:00:0d:00:00/40 tag 2 ncq 110592 out
Oct 7 20:02:12 StudioXPS kernel: [ 249.193602] res
41/40:08:98:6f:53/00:00:1a:00:00/40 Emask 0x9 (media error)
Oct 7 20:02:12 StudioXPS kernel: [ 249.193605] ata1.00: status: { DRDY ERR }
Oct 7 20:02:12 StudioXPS kernel: [ 249.193607] ata1.00: error: { UNC }
Oct 7 20:02:12 StudioXPS kernel: [ 249.196606] ata1.00: configured for
UDMA/100
Oct 7 20:02:12 StudioXPS kernel: [ 249.196622] sd 0:0:0:0: [sda] Unhandled
sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196624] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196626] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196628] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196629] Sense Key : Medium Error
[current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196633] Descriptor sense data with
sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196634] 72 03 11 04 00 00 00
0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196642] 1a 53 6f 98
Oct 7 20:02:12 StudioXPS kernel: [ 249.196645] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196648] Add. Sense: Unrecovered read
error - auto reallocate failed
Oct 7 20:02:12 StudioXPS kernel: [ 249.196650] sd 0:0:0:0: [sda] CDB:
Oct 7 20:02:12 StudioXPS kernel: [ 249.196651] Read(10): 28 00 1a 53 6f 90
00 00 20 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196658] end_request: I/O error, dev
sda, sector 441675672
Oct 7 20:02:12 StudioXPS kernel: [ 249.196674] sd 0:0:0:0: [sda] Unhandled
sense code
Oct 7 20:02:12 StudioXPS kernel: [ 249.196676] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196678] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
Oct 7 20:02:12 StudioXPS kernel: [ 249.196679] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196681] Sense Key : Medium Error
[current] [descriptor]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196683] Descriptor sense data with
sense descriptors (in hex):
Oct 7 20:02:12 StudioXPS kernel: [ 249.196684] 72 03 11 04 00 00 00
0c 00 0a 80 00 00 00 00 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196692] 1a 53 6f 98
Oct 7 20:02:12 StudioXPS kernel: [ 249.196695] sd 0:0:0:0: [sda]
Oct 7 20:02:12 StudioXPS kernel: [ 249.196697] Add. Sense: Unrecovered read
error - auto reallocate failed
Oct 7 20:02:12 StudioXPS kernel: [ 249.196699] sd 0:0:0:0: [sda] CDB:
Oct 7 20:02:12 StudioXPS kernel: [ 249.196700] Write(10): 2a 00 2b 0e fb 18
00 00 18 00
Oct 7 20:02:12 StudioXPS kernel: [ 249.196706] end_request: I/O error, dev
sda, sector 722402072
Oct 7 20:02:12 StudioXPS kernel: [ 249.196710] Buffer I/O error on
