[Kernel-packages] [Bug 1510051] Re: Ubuntu 15.10: WiFi disabled on Thinkpad X230
Dear Christopher, Thanks for your help! I followed your advice and updated my BIOS. For now, I haven't encountered the WiFi problem anymore but this might just be a random fact. If I ever encounter the issue again, I will report back! Warmly, ~ Robert -- 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/1510051 Title: Ubuntu 15.10: WiFi disabled on Thinkpad X230 Status in linux package in Ubuntu: Incomplete Bug description: Dear all, Occasionally the WiFi module of my Thinkpad X230 is disabled. It occurs without a recognisable pattern. Sometimes on a fresh boot. Sometimes on resume from suspend. In the indicator icon context menu, networking and wifi is enabled but greyed out. Switching off/on the Wifi using the hardware switch doesn't solve the problem. The only working solution is to do a fresh reboot. Thank you for any possible help! Robert ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: orschiro 1627 F pulseaudio CurrentDesktop: Unity Date: Mon Oct 26 12:21:15 2015 HibernationDevice: RESUME=UUID=64b3d395-2d88-4111-a079-f94b1bdd9239 InstallationDate: Installed on 2015-09-22 (33 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: LENOVO 23352CG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=361b58ba-4794-4b5b-955a-9706e758f5d6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/05/2015 dmi.bios.vendor: LENOVO dmi.bios.version: G2ETA3WW (2.63 ) dmi.board.asset.tag: Not Available dmi.board.name: 23352CG dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ETA3WW(2.63):bd02/05/2015:svnLENOVO:pn23352CG:pvrThinkPadX230:rvnLENOVO:rn23352CG:rvrNODPK:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23352CG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1510051/+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 1511694] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510971/+files/RfKill.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510969/+files/ProcModules.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510970/+files/PulseList.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510972/+files/UdevDb.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510964/+files/Lspci.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510973/+files/WifiSyslog.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510968/+files/ProcInterrupts.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510963/+files/JournalErrors.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510967/+files/ProcEnviron.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510962/+files/IwConfig.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510965/+files/Lsusb.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] Re: USB tethering does not work after system Suspend
Christopher, submitted the app-port information. Did this while I had awakened my system from suspended state and USB tethering was not working. One minor thing, while running the apport-collect it did give a terminal message saying dpkg-query: no packages found matching linux Please let me know however I can contribute towards this :) Thanks -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510966/+files/ProcCpuinfo.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510961/+files/CurrentDmesg.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 Tags: wily UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 4.2.0-16-generic x86_64 UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0K02M5 dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: dmi.product.name: Inspiron 5521 dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511694] Re: USB tethering does not work after system Suspend
apport information ** Tags added: apport-collected ** Description changed: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) + --- + ApportVersion: 2.19.1-0ubuntu4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: aukhan 1516 F pulseaudio + CRDA: + country PK: DFS-JP + (2402 - 2482 @ 40), (N/A, 20), (N/A) + (5735 - 5835 @ 80), (N/A, 30), (N/A) + CurrentDesktop: Unity + DistroRelease: Ubuntu 15.10 + HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f + InstallationDate: Installed on 2015-05-23 (162 days ago) + InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) + MachineType: Dell Inc. Inspiron 5521 + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e92-4975-a79c-da36ae777b32 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 + RelatedPackageVersions: + linux-restricted-modules-4.2.0-16-generic N/A + linux-backports-modules-4.2.0-16-generic N/A + linux-firmware1.149 + Tags: wily + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 4.2.0-16-generic x86_64 + UpgradeStatus: Upgraded to wily on 2015-10-29 (3 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/20/2013 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: 0K02M5 + dmi.board.vendor: Dell Inc. + dmi.board.version: A02 + dmi.chassis.type: 8 + dmi.chassis.vendor: Dell Inc. + dmi.chassis.version: A08 + dmi.modalias: dmi:bvnDellInc.:bvrA08:bd05/20/2013:svnDellInc.:pnInspiron5521:pvrA08:rvnDellInc.:rn0K02M5:rvrA02:cvnDellInc.:ct8:cvrA08: + dmi.product.name: Inspiron 5521 + dmi.product.version: A08 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1511694/+attachment/4510960/+files/AlsaInfo.txt -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) --- ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aukhan 1516 F pulseaudio CRDA: country PK: DFS-JP (2402 - 2482 @ 40), (N/A, 20), (N/A) (5735 - 5835 @ 80), (N/A, 30), (N/A) CurrentDesktop: Unity DistroRelease: Ubuntu 15.10 HibernationDevice: RESUME=UUID=5c647f39-bad9-4662-b6ff-b9de1d8a482f InstallationDate: Installed on 2015-05-23 (162 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Inspiron 5521 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic root=UUID=a45f430b-3e
[Kernel-packages] [Bug 781556] Re: bluetooth discovery fails: no devices found during scan
Confirm bug for 15.10 Even more, Bluetoth applet say 'no adapters found' even if connected to other devises. $sudo bccmd psset -s 0x 0x028c 0x0001 $hcitool dev Devices: hci0CC:52:AF:DE:E9:CB $sudo /etc/init.d/bluetooth restart [ ok ] Restarting bluetooth (via systemctl): bluetooth.service. // in dmesg: Bluetooth: hci0 hardware error 0x37 $hcitool dev Devices: $sudo hciconfig hci0 up @frank@FQC-book:~$ hcitool dev Devices: hci0CC:52:AF:DE:E9:CB -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/781556 Title: bluetooth discovery fails: no devices found during scan Status in Blueman: New Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Bug description: Binary package hint: bluez hcitool scan completes without errors but no devices found ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: bluez 4.91-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5 Uname: Linux 2.6.39-0-generic x86_64 Architecture: amd64 Date: Thu May 12 10:42:55 2011 InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC ProcEnviron: LANGUAGE=en_US:en PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.39-0-generic root=UUID=e48720e0-d114-4e3e-acb1-5d1b33567ac5 ro crashkernel=384M-2G:64M,2G-:128M quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1611 dmi.board.vendor: Hewlett-Packard dmi.board.version: 96.1F dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnHewlett-Packard:bvrF.05:bd03/04/2011:svnHewlett-Packard:pnHPPaviliondm1NotebookPC:pvr058910252B0320100:rvnHewlett-Packard:rn1611:rvr96.1F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion dm1 Notebook PC dmi.product.version: 058910252B0320100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: EC:55:F9:D1:60:07 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:2767 acl:0 sco:0 events:116 errors:0 TX bytes:1966 acl:0 sco:0 commands:111 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/781556/+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 1482711] Re: X displays nothing instead of login screen
I know I took a long time again. My primary observation is that this bug does not appear when the nvidia driver is not installed. I tested the upstream kernel version that matches the most recent repository kernel update(as well as the most recent upstream kernel version) before installing the most recent repository kernel update(3.13.11-031311ckt27 which the package manager calls 3.13.0-66.108). With both of the kernels from the upstream source, the nvidia module failed to install, and neither exhibited the bug, but when installed from the package manager the bug did occur in that same kernel version. Unfortunately I don't know how to make the nvidia driver install for the upstream kernels, if it is even possible, and thus cannot test them properly. This is complicated by the fact that this bug appeared when the package manager forced an update to the nvidia module from 331 which supports my video card to 340 which makes no such claim. Other than the nvidia driver not installing, the upstream kernels worked fine, though with a lot of warnings when I booted them, all about apparmor rules not being enforced. If you want, I ran a dmesg with each of them booted into a file, but I hesitate to post them, and thus pollute the associated data without your say so. Given this information I fully expect that the answer here is either, "go report this to ___ instead of here.", "Sorry but your hardware is not supported by the newer kernel versions. Have a nice day." or possibly a "Well, see if it happens with the repository kernels if you uninstall the ndivia drivers." (I made a half hearted attempt to do that even before I posted this bug, but I didn't figure out how to tell the package manager to uninstall all the nvidia drivers without trying to install some random other version.) Another thing that might provide some clues: some time ago I had installed the CUDA develpoment tools, and made a simple test program. On the version of the kernel for which the desktop works, that CUDA program will not run (it says that there is no device), however, when switched over to a virtual terminal from the blank screen caused by the bug, the program runs just fine. This tells me that perhaps the bug isn't occurring for this kernel version because the nvidia driver isn't working for it. So I hope this is somewhat useful even though technically the response is unable to test upstream. As per the instructions I will mark it as confirmed again. I hope that that is the right thing to do, even though I wasn't really able to test what you wanted well. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1482711 Title: X displays nothing instead of login screen Status in linux package in Ubuntu: Confirmed Bug description: The kernel version in the auto-generated information is wrong, because when using the kernel with the problem, I can't do anything, including send bug reports. This happened with the newest kernel update to 3.13.0-61. I am using -59, which still works, to send the report. Since this is at least possibly graphics related bug I should also state that the update automatically changed the nvidia driver from 331-updates to 340-updates, however Nvidia's page for the 340 driver does not include my graphics card (GeForce 610M). I do use ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-59-generic 3.13.0-59.98 ProcVersionSignature: Ubuntu 3.13.0-59.98-generic 3.13.11-ckt22 Uname: Linux 3.13.0-59-generic i686 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trun 2629 F pulseaudio CurrentDesktop: Unity Date: Fri Aug 7 09:22:29 2015 HibernationDevice: RESUME=UUID=6d121e03-2523-4564-ab73-f600c35a6142 InstallationDate: Installed on 2014-11-23 (256 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 1bcf:288a Sunplus Innovation Technology Inc. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire 7739G ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-59-generic root=/dev/mapper/vg_hydra-lv_root ro noplymouth RelatedPackageVersions: linux-restricted-modules-3.13.0-59-generic N/A linux-backports-modules-3.13.0-59-generic N/A linux-firmware 1.127.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 10/11/2011 dmi.bios.vendor: Insy
[Kernel-packages] [Bug 1512221] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1512221 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1512221 Title: MPT3SAS Driver update for next kernel release Status in linux package in Ubuntu: Incomplete Bug description: Update mpt3sas inbox driver version for next kernel release(i,e., for 16.04) to 9.100.00.00 which is the latest on the upstream kernel. Below are the upstream commit IDs for patches from Phase3 to Phase8, 1. fb77bb5376a55f4e6c8d9243249e82831a276ee5 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=fb77bb5376a55f4e6c8d9243249e82831a276ee5 2. 4dc8c8087f0304ff8d06f862520406b11aac4a66 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=4dc8c8087f0304ff8d06f862520406b11aac4a66 3. e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e 4. 580d4e3153f0d7a9a9235b675b0b7b13e2185a8b http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=580d4e3153f0d7a9a9235b675b0b7b13e2185a8b 5. a94bea343c2f747c62ef66b52d2430e6aeb75434 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=a94bea343c2f747c62ef66b52d2430e6aeb75434 6. e6d45e3e7e6582fa206ef84631639ce70d50e5c5 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e6d45e3e7e6582fa206ef84631639ce70d50e5c5 7. f9d81cfc23151eb6e9e498663c9784c351646d0e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=f9d81cfc23151eb6e9e498663c9784c351646d0e 8. 2e26c3853206ba166c3434e5f2ca4c82078ad84e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=2e26c3853206ba166c3434e5f2ca4c82078ad84e 9. 35c319b47884e49d9d0a84779097916ccb173947 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=35c319b47884e49d9d0a84779097916ccb173947 10. fb84dfc44718ef4099a827d147f738e428828d02 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=fb84dfc44718ef4099a827d147f738e428828d02 11. 38e4141ecb0e59c93d85ec5948f98d1f1e331a88 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=38e4141ecb0e59c93d85ec5948f98d1f1e331a88 12. 2b89669ae4addfa68a58e0fc16afdd24739720d8 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=2b89669ae4addfa68a58e0fc16afdd24739720d8 13. a6f84009b9d7ca97c400ca929f9d58f43b0ece9d http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=a6f84009b9d7ca97c400ca929f9d58f43b0ece9d 14. 3898f08e8ccfc8b7b4c297960ecdde970869e950 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=3898f08e8ccfc8b7b4c297960ecdde970869e950 15. 62f5c74c97037c7c00fdefb69dcfe39810c34a05 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=62f5c74c97037c7c00fdefb69dcfe39810c34a05 16. d8eb4a47c70b4bab34b938d2f682044687f53c64 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=d8eb4a47c70b4bab34b938d2f682044687f53c64 17. bdff785e4f593218816fa3677e043aae1481aa98 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=bdff785e4f593218816fa3677e043aae1481aa98 18. 36814028ad720165a6febcf9ddd7de20833fd240 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=36814028ad720165a6febcf9ddd7de20833fd240 19. df838f92f3f5240dca54e1629e8547818e8ea646 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=df838f92f3f5240dca54e1629e8547818e8ea646 20. c75683ca13d12a700531864bcd3118e94bc9eaa0 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=c75683ca13d12a700531864bcd3118e94bc9eaa0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512221/+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 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
I have sent an email to the debian maintainer of the sta broadcom package, contents as followed: [quote] Hi Eduard, I have just filed a bug on the ubuntu bugs forum at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043 . Essentially the problem is that the driver prevents my XPS15 from resuming from suspend. As a temporary solution, I have created a script for systemd-sleep that unloads the wl driver prior to suspend, and reloads it after resuming. This fixes the problem, but is really just a hack. You can see my script on the bug report. I just wanted to let you know about this issue as the maintainer of the package. Thanks for all of your hard work in providing this software. Thanks and Best Regards, Mark Pointing. [/quote] -- 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/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Triaged Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.lau
[Kernel-packages] [Bug 1512221] [NEW] MPT3SAS Driver update for next kernel release
Public bug reported: Update mpt3sas inbox driver version for next kernel release(i,e., for 16.04) to 9.100.00.00 which is the latest on the upstream kernel. Below are the upstream commit IDs for patches from Phase3 to Phase8, 1. fb77bb5376a55f4e6c8d9243249e82831a276ee5 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=fb77bb5376a55f4e6c8d9243249e82831a276ee5 2. 4dc8c8087f0304ff8d06f862520406b11aac4a66 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=4dc8c8087f0304ff8d06f862520406b11aac4a66 3. e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e 4. 580d4e3153f0d7a9a9235b675b0b7b13e2185a8b http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=580d4e3153f0d7a9a9235b675b0b7b13e2185a8b 5. a94bea343c2f747c62ef66b52d2430e6aeb75434 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=a94bea343c2f747c62ef66b52d2430e6aeb75434 6. e6d45e3e7e6582fa206ef84631639ce70d50e5c5 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e6d45e3e7e6582fa206ef84631639ce70d50e5c5 7. f9d81cfc23151eb6e9e498663c9784c351646d0e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=f9d81cfc23151eb6e9e498663c9784c351646d0e 8. 2e26c3853206ba166c3434e5f2ca4c82078ad84e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=2e26c3853206ba166c3434e5f2ca4c82078ad84e 9. 35c319b47884e49d9d0a84779097916ccb173947 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=35c319b47884e49d9d0a84779097916ccb173947 10. fb84dfc44718ef4099a827d147f738e428828d02 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=fb84dfc44718ef4099a827d147f738e428828d02 11. 38e4141ecb0e59c93d85ec5948f98d1f1e331a88 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=38e4141ecb0e59c93d85ec5948f98d1f1e331a88 12. 2b89669ae4addfa68a58e0fc16afdd24739720d8 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=2b89669ae4addfa68a58e0fc16afdd24739720d8 13. a6f84009b9d7ca97c400ca929f9d58f43b0ece9d http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=a6f84009b9d7ca97c400ca929f9d58f43b0ece9d 14. 3898f08e8ccfc8b7b4c297960ecdde970869e950 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=3898f08e8ccfc8b7b4c297960ecdde970869e950 15. 62f5c74c97037c7c00fdefb69dcfe39810c34a05 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=62f5c74c97037c7c00fdefb69dcfe39810c34a05 16. d8eb4a47c70b4bab34b938d2f682044687f53c64 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=d8eb4a47c70b4bab34b938d2f682044687f53c64 17. bdff785e4f593218816fa3677e043aae1481aa98 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=bdff785e4f593218816fa3677e043aae1481aa98 18. 36814028ad720165a6febcf9ddd7de20833fd240 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=36814028ad720165a6febcf9ddd7de20833fd240 19. df838f92f3f5240dca54e1629e8547818e8ea646 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=df838f92f3f5240dca54e1629e8547818e8ea646 20. c75683ca13d12a700531864bcd3118e94bc9eaa0 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=c75683ca13d12a700531864bcd3118e94bc9eaa0 ** 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/1512221 Title: MPT3SAS Driver update for next kernel release Status in linux package in Ubuntu: New Bug description: Update mpt3sas inbox driver version for next kernel release(i,e., for 16.04) to 9.100.00.00 which is the latest on the upstream kernel. Below are the upstream commit IDs for patches from Phase3 to Phase8, 1. fb77bb5376a55f4e6c8d9243249e82831a276ee5 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=fb77bb5376a55f4e6c8d9243249e82831a276ee5 2. 4dc8c8087f0304ff8d06f862520406b11aac4a66 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=4dc8c8087f0304ff8d06f862520406b11aac4a66 3. e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=e4bc7f5c21a18cab9acd30940df0ee791fcd7b9e 4. 580d4e3153f0d7a9a9235b675b0b7b13e2185a8b http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=for-next&id=580d4e3153f0d7a9a9235b675b0b7b13e2185a8b 5. a94bea343c2f747c62ef66b52d2430e6aeb75434 http://git.kernel.org/cgit/linux/kernel/git/jejb/scsi.git/commit/?h=f
[Kernel-packages] [Bug 1486099] Re: Crash of Xorg under intel drm
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1486099 Title: Crash of Xorg under intel drm Status in linux package in Ubuntu: Expired Bug description: I am using an older Ubuntu mainline kernel with Vivid. The computer I am using is a Dell XPS 9343 which is known not to do too well with linux, like most new dell computers. However the only issue that actively bothers me the fact that Xorg is getting crashed all the time by the frame buffer drm in the intel driver. This can be observer in this trace, [33477.084660] [ cut here ] [33477.084688] WARNING: CPU: 0 PID: 901 at /build/linux-OdodyZ/linux-3.19.0/drivers/gpu/drm/i915/intel_display.c:1256 assert_plane.constprop.87+0x7b/0x90 [i915]() [33477.084689] plane A assertion failure (expected on, current off) [33477.084706] Modules linked in: isofs pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc rfcomm bnep nls_iso8859_1 cdc_acm btusb bluetooth uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core v4l2_common videodev media usbhid joydev snd_hda_codec_hdmi wl(POE) dell_wmi hid_multitouch sparse_keymap intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel dell_laptop dcdbas kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd serio_raw dell_led snd_hda_codec_realtek snd_soc_rt286 snd_hda_codec_generic snd_soc_core snd_compress snd_pcm_dmaengine i915 lpc_ich snd_hda_intel snd_seq_midi snd_hda_controller snd_seq_midi_event cfg80211 snd_hda_codec snd_hwdep rtsx_pci_ms drm_kms_helper memstick [33477.084720] mei_me snd_rawmidi snd_pcm drm i2c_algo_bit shpchp mei wmi int3403_thermal soc_button_array snd_seq snd_seq_device snd_timer snd soundcore i2c_hid hid video dw_dmac dw_dmac_core snd_soc_sst_acpi 8250_dw i2c_designware_platform i2c_designware_core spi_pxa2xx_platform int3402_thermal int3400_thermal acpi_thermal_rel processor_thermal_device acpi_pad mac_hid parport_pc ppdev lp parport autofs4 uas usb_storage rtsx_pci_sdmmc psmouse ahci libahci sdhci_acpi sdhci rtsx_pci [33477.084722] CPU: 0 PID: 901 Comm: Xorg Tainted: PW OE 3.19.0-25-generic #26-Ubuntu [33477.084723] Hardware name: Dell Inc. XPS 13 9343/0310JH, BIOS A05 07/14/2015 [33477.084725] c0611310 880212b076f8 817c4518 888e888e [33477.084726] 880212b07748 880212b07738 81076a6a 8802134c4200 [33477.084727] 880212f3d000 880036582800 880036582800 [33477.084727] Call Trace: [33477.084732] [] dump_stack+0x45/0x57 [33477.084735] [] warn_slowpath_common+0x8a/0xc0 [33477.084736] [] warn_slowpath_fmt+0x46/0x50 [33477.084751] [] assert_plane.constprop.87+0x7b/0x90 [i915] [33477.084764] [] hsw_disable_ips+0x41/0x190 [i915] [33477.084777] [] intel_crtc_disable_planes+0x48/0x140 [i915] [33477.084788] [] haswell_crtc_disable+0x4f/0x3c0 [i915] [33477.084800] [] __intel_set_mode+0xa59/0xc80 [i915] [33477.084812] [] intel_crtc_set_config+0xbfb/0xf70 [i915] [33477.084815] [] ? __enqueue_entity+0x78/0x80 [33477.084827] [] drm_mode_set_config_internal+0x66/0x100 [drm] [33477.084833] [] restore_fbdev_mode+0xc8/0xf0 [drm_kms_helper] [33477.084839] [] drm_fb_helper_restore_fbdev_mode_unlocked+0x29/0x80 [drm_kms_helper] [33477.084843] [] drm_fb_helper_set_par+0x22/0x50 [drm_kms_helper] [33477.084857] [] intel_fbdev_set_par+0x1a/0x60 [i915] [33477.084859] [] fb_set_var+0x18a/0x410 [33477.084862] [] ? check_preempt_curr+0x89/0xa0 [33477.084863] [] ? __enqueue_entity+0x78/0x80 [33477.084865] [] ? enqueue_entity+0x400/0xc30 [33477.084867] [] fbcon_blank+0x229/0x300 [33477.084869] [] do_unblank_screen+0xba/0x1f0 [33477.084872] [] complete_change_console+0x5d/0xf0 [33477.084873] [] vt_ioctl+0x118a/0x1460 [33477.084881] [] ? drm_ioctl+0x8c/0x680 [drm] [33477.084883] [] tty_ioctl+0x411/0xcb0 [33477.084886] [] ? do_readv_writev+0x185/0x280 [33477.084888] [] do_vfs_ioctl+0x2e0/0x4e0 [33477.084889] [] SyS_ioctl+0x81/0xa0 [33477.084890] [] system_call_fastpath+0x16/0x1b [33477.084891] ---[ end trace 4514549be501e890 ]--- [33479.411280] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun I can confirm that the crash occurs in different ways according to different traces I've read but it would be impossible to compile all of them. The crashes of the screen are not apparent to any function done on the user end. They are random and can sometimes be very spaced out or sometimes happen many times in a row. In order to get the screen working without restarting ligh
[Kernel-packages] [Bug 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
Further information, it turns out that pm-suspend is no longer used, and systemd-sleep is the new system. The scripts section of pm-suspend is still there, but it is broken as per https://launchpad.net/ubuntu/+source/pm-utils/+bug/1455097 (why does everything I look into seem to be broken). To fix the problem, I created the script (make it executable) /lib/systemd/system-sleep/broadcom_wl_suspend with the contents [code] #! /bin/sh #mp035: unload buggy broadcom sta driver during suspend. case $1 in pre) modprobe -r wl ;; post) modprobe wl ;; esac [/code] This has fixed the problem. I'm not sure where to push this from here, either the 1) the broadcom package should add ths script, or 2) or the broadcom sta driver needs fixing. Perhaps (1) immediately while we are waiting for broadcom to fix (2)? -- 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/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Triaged Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+subscrip
[Kernel-packages] [Bug 1499425] Re: [nouveau] xmir black window (mesa 11.0.0) and/or freezing and kernel errors
Reassigning this bug to the kernel. AFAIK the only problem that was in Xmir itself was resolved as bug 1417541. The remaining issues, while severe, are general nouveau driver/kernel issues. ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) -- 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/1499425 Title: [nouveau] xmir black window (mesa 11.0.0) and/or freezing and kernel errors Status in Mir: Invalid Status in linux package in Ubuntu: Confirmed Status in mir package in Ubuntu: Invalid Bug description: wily/unity8/mir i'm trying to run some x11 apps on unity8/mir but i get a black window, the window size looks right, tested with geany, firefox, etc (windows size is diff depending on the app). tried every Xmir arg no luck i don't see any warnings or error messages glamor EGL version: 1.4 (DRI2) glamor EGL extensions: EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_WL_bind_wayland_display : glamor GL version: 3.0 Mesa 11.0.0 glamor GL extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blen d_square GL_NV_light_max_e glamor GLSL version: 1.30 [DRI2] Setup complete [DRI2] DRI driver: nouveau [DRI2] VDPAU driver: nouveau Resize requested to 1008x728 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1499425/+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 1041790]
FWIW, my issue (https://bugs.freedesktop.org/show_bug.cgi?id=54226#c191), was resolved by uninstalling various components, re-installing and updating them. I have a hunch (completely unproven) that it was a transparent bit-fail issue from the SSD. By un-installing and re-installing, the files were likely installed to a different location on the drive. It wasn't configuration, as I tried erasing, and even rolling back to defaults, with the problem still persisting. As it was almost daily, prior to uninstall, and hasn't happened since the install, this is all I can attribute it to. HTH someone. -- 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/1041790 Title: [snb] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001, workaround i915.semaphores=0 Status in xf86-video-intel: In Progress Status in linux package in Ubuntu: Incomplete Status in sandybridge-meta package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Triaged Bug description: X locks up periodically for a 2 to ten seconds at a time and this crash log gets generated. It's significantly more than several times a day but not quite continuous. If you indeed have this bug, that should stop the lockups from happening. Irrespective, please file a new bug report so your hardware may be tracked. WORKAROUND: Edit your /etc/default/grub from: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i915.semaphores=0" run the following and reboot: sudo update-grub The side effects of this is rendering throughput is dropped by 10% with SNA, or as much as 3x with UXA. OpenGL performance is likely to be reduced by about 30%. More CPU time is spent waiting for the GPU with rc6 disabled, so increased power consumption. ProblemType: Crash DistroRelease: Ubuntu 12.10 Package: xserver-xorg-video-intel 2:2.20.3-0ubuntu1 Uname: Linux 3.6.0-rc3-git-20120826.1015 x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Chipset: sandybridge-m-gt2 Date: Sun Aug 26 16:06:32 2012 DistroCodename: quantal DistroVariant: ubuntu DuplicateSignature: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 Ubuntu 12.10 EcryptfsInUse: Yes ExecutablePath: /usr/share/apport/apport-gpu-error-intel.py GpuHangFrequency: Continuously InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120724.2) InterpreterPath: /usr/bin/python3.2mu MachineType: Dell Inc. Dell System XPS L502X ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gpu-error-intel.py ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.6.0-rc3-git-20120826.1015 root=UUID=135c8090-427c-460a-909d-eff262cd44b6 ro quiet splash vt.handoff=7 RelatedPackageVersions: xserver-xorg 1:7.7+1ubuntu3 libdrm2 2.4.38-0ubuntu2 xserver-xorg-video-intel 2:2.20.3-0ubuntu1 SourcePackage: xserver-xorg-video-intel Title: [sandybridge-m-gt2] GPU lockup IPEHR: 0x0b160001 IPEHR: 0x0b140001 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 05/29/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0NJT03 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd05/29/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0NJT03:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Dell System XPS L502X dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/1041790/+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 1499425] [NEW] [nouveau] xmir black window (mesa 11.0.0) and/or freezing and kernel errors
You have been subscribed to a public bug: wily/unity8/mir i'm trying to run some x11 apps on unity8/mir but i get a black window, the window size looks right, tested with geany, firefox, etc (windows size is diff depending on the app). tried every Xmir arg no luck i don't see any warnings or error messages glamor EGL version: 1.4 (DRI2) glamor EGL extensions: EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_KHR_create_context EGL_KHR_get_all_proc_addresses EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_surfaceless_context EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_WL_bind_wayland_display : glamor GL version: 3.0 Mesa 11.0.0 glamor GL extensions: GL_ARB_multisample GL_EXT_abgr GL_EXT_bgra GL_EXT_blend_color GL_EXT_blend_minmax GL_EXT_blend_subtract GL_EXT_copy_texture GL_EXT_polygon_offset GL_EXT_subtexture GL_EXT_texture_object GL_EXT_vertex_array GL_EXT_compiled_vertex_array GL_EXT_texture GL_EXT_texture3D GL_IBM_rasterpos_clip GL_ARB_point_parameters GL_EXT_draw_range_elements GL_EXT_packed_pixels GL_EXT_point_parameters GL_EXT_rescale_normal GL_EXT_separate_specular_color GL_EXT_texture_edge_clamp GL_SGIS_generate_mipmap GL_SGIS_texture_border_clamp GL_SGIS_texture_edge_clamp GL_SGIS_texture_lod GL_ARB_framebuffer_sRGB GL_ARB_multitexture GL_EXT_framebuffer_sRGB GL_IBM_multimode_draw_arrays GL_IBM_texture_mirrored_repeat GL_ARB_texture_cube_map GL_ARB_texture_env_add GL_ARB_transpose_matrix GL_EXT_blend_func_separate GL_EXT_fog_coord GL_EXT_multi_draw_arrays GL_EXT_secondary_color GL_EXT_texture_env_add GL_EXT_texture_filter_anisotropic GL_EXT_texture_lod_bias GL_INGR_blend_func_separate GL_NV_blend_ square GL_NV_light_max_e glamor GLSL version: 1.30 [DRI2] Setup complete [DRI2] DRI driver: nouveau [DRI2] VDPAU driver: nouveau Resize requested to 1008x728 ** Affects: mir Importance: Undecided Status: Invalid ** Affects: mir (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu) Importance: High Status: Confirmed ** Tags: xmir -- [nouveau] xmir black window (mesa 11.0.0) and/or freezing and kernel errors https://bugs.launchpad.net/bugs/1499425 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
Ok, I have narrowed the issue down to the broadcom proprietary "wl" driver. If I rmmod before suspend, then the system resumes correctly. I can then modprobe it and continue to work normally. The only problem is that creating /etc/pm/config.d/modules with the content SUSPEND_MODULES="wl" has no effect. Is there a solution to this issue? ** Tags removed: needs-reverse-bisect regression-update -- 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/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Triaged Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+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
Re: [Kernel-packages] [Bug 1505564] Re: Soft lockup with "block nbdX: Attempted send on closed socket" spam
Hello Junien, (recommendations with *) I'm replying to you and to the LP bug so it gets proper documentation. Under comment #91: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1505564/comments/91 You can see my kernel dump analysis, where I am showing you that the OS is stuck in a "migration thread", possibly because of a lack of IPIs synchronisation (maybe even an IPI being lost). We have already seen cases like this - specially in nested virtualisation environments - and this has been discussed in LKML. Before we move further I need you to follow some kind of "best practices" for Proliant Servers: 1 - NMIs caused during MWAIT instruction (caused by intel_idle module): & HP Proliant Servers - Kernel Panic - NMI - DL360 & DL380 - HPWDT module loaded (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1417580) (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1432837) * Firmware: Configure a maximum of a C3 c-state for CPU savings (CPU C-STATES) * Firmware: Disable packed CPU c-state * Firmware: Disable Cooperative Power Management * Make sure NOT TO LOAD HPWDT kernel module (LP: #1432837 Fix Released 3.13.0-49.81) 2 - Recently discovered NMIs caused by a BUG in Intel microcode (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1416414) ** If you have Intel based Proliant Servers, because of Intel microcode issue, use at least* 3.13.0-35.61. 3 - X2APIC support for HP Proliant Servers (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1398497) * For Proliant prior to G8 (<= G7) use "nox2apic intremap=off" into grub cmdline * For Proliant G8 use "intremap=no_x2apic_optout" into grub cmdline 4 - HP Proliant Latest Firmware MOST IMPORTANT Upgrade server firmware to latest version There were numerous firmware fixes from HP. ---> If we are facing a firmware problem - related to IPIs, the inter-processor-interrupts, being missed - we have to make sure this is reproducible in the latest firmware in order to work together with HP ROM engineering team. Summary: Could you follow all these steps and provide feedback ? I understand this might take awhile if you have a big number of servers and - if so - I would take a statistical approach here, by changing only half of the servers and sticking with the first half as the "control group", for future comparisons. Is this feasible ? Looking forward to hearing your feedback. Best Regards Rafael Tinoco Sustaining Engineering -- 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/1505564 Title: Soft lockup with "block nbdX: Attempted send on closed socket" spam Status in linux package in Ubuntu: In Progress Bug description: Hi, Some of our nova compute hosts regularly freeze, sometimes for a few hours, with kern.log getting spammed with : block nbdX: Attempted send on closed socket and a few "CPU soft lockup" messages (see attached log). This clears up when the queue gets cleared, eg : block nbdX: queue cleared trusty hosts with kernel version 3.19.0-30-generic. Note that timestamps from kern.log appears to be wrong, it looks like the messages are being held, and then all delivered at once when the kernel unfreezes. Attaching apport files from 2 hosts below. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 9 13:14 seq crw-rw 1 root audio 116, 33 Oct 9 13:14 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HP ProLiant DL385 G7 Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic root=UUID=1bd039df-c419-4cb7-b1ad-fe004d55ccd4 ro console=tty0 console=ttyS1,38400 nosplash ProcVersionSignature: Ubuntu 3.19.0-30.34~14.04.1-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-30-generic N/A linux-backports-modules-3.19.0-30-generic N/A linux-firmware 1.127.15 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 3.19.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 12/08/2012 dmi.bios.vendor: HP dmi.bios.version: A18 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrA18:bd12/08/2012:svnHP:pnProLiantDL385G7:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL385 G7 dmi.sys.vendor: HP --- AlsaDevices: total 0 crw-rw 1 root audio
[Kernel-packages] [Bug 1508767] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510845/+files/UdevLog.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783f0
[Kernel-packages] [Bug 1508767] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510844/+files/UdevDb.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783f
[Kernel-packages] [Bug 1508767] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510834/+files/CurrentDmesg.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 8
[Kernel-packages] [Bug 1508767] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510833/+files/CRDA.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 n
[Kernel-packages] [Bug 1508767] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510842/+files/ProcModules.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d
[Kernel-packages] [Bug 1508767] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510846/+files/WifiSyslog.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87
[Kernel-packages] [Bug 1508767] nvram.gz
apport information ** Attachment added: "nvram.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510847/+files/nvram.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 n
[Kernel-packages] [Bug 1508767] ProcPpc64.tar.gz
apport information ** Attachment added: "ProcPpc64.tar.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510843/+files/ProcPpc64.tar.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 8
[Kernel-packages] [Bug 1508767] DeviceTree.tar.gz
apport information ** Attachment added: "DeviceTree.tar.gz" https://bugs.launchpad.net/bugs/1508767/+attachment/4510835/+files/DeviceTree.tar.gz -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at
[Kernel-packages] [Bug 1508767] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510836/+files/IwConfig.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783
[Kernel-packages] [Bug 1508767] ProcMisc.txt
apport information ** Attachment added: "ProcMisc.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510841/+files/ProcMisc.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783
[Kernel-packages] [Bug 1508767] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510837/+files/Lspci.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8
[Kernel-packages] [Bug 1508767] ProcLocks.txt
apport information ** Attachment added: "ProcLocks.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510840/+files/ProcLocks.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b7
[Kernel-packages] [Bug 1508767] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510838/+files/ProcCpuinfo.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d
[Kernel-packages] [Bug 1508767] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1508767/+attachment/4510839/+files/ProcInterrupts.txt -- 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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
apport information ** Tags added: apport-collected ** Description changed: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr 100d9cac code 30001 | Oct 14 22:21:46 floette kernel: [168902.724121] neutron-openvsw[153852]: unhandled signal 11 at 882b78783fa8 nip 100b5c8c lr 1014c734 code 30001 | hloeung@patrat:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 15 00:48:13 patrat kernel: [553143.677075] rsync[89656]: unhandled signal 11 at 3fffe6a5 n
[Kernel-packages] [Bug 1508767] Re: IBM POWER8 unhandled signal 11 / SEGV
** Also affects: linux-meta-lts-vivid (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/1508767 Title: IBM POWER8 unhandled signal 11 / SEGV Status in Ubuntu Cloud Archive: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-lts-vivid package in Ubuntu: New Bug description: Hi, We have a few IBM POWER8 servers which we're currently using as OpenStack nova compute nodes. It seems we're regularly running into issues where processes are segfaulting: | hloeung@gligar:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.5.gz | Oct 16 23:31:38 gligar kernel: [88351.465559] neutron-openvsw[29733]: unhandled signal 11 at 88f90100 nip 100ba0d8 lr 101ad860 code 30001 | Oct 16 23:31:38 gligar kernel: [88351.566909] init: neutron-plugin-openvswitch-agent main process (29733) killed by SEGV signal | Oct 16 23:31:38 gligar kernel: [88351.746611] apport[29500]: unhandled signal 11 at 8850e467250040a8 nip 10201f80 lr 10202984 code 30001 | Oct 16 23:31:39 gligar kernel: [88352.245829] neutron-rootwra[29749]: unhandled signal 11 at 0809c4b61000 nip 1014ae4c lr 1014b544 code 30001 | Oct 16 23:31:50 gligar kernel: [88364.040340] neutron-rootwra[30060]: unhandled signal 11 at 08a305c12b00 nip 100b74d0 lr 100b73e4 code 30001 | Oct 16 23:31:51 gligar kernel: [88364.174218] neutron-rootwra[30065]: unhandled signal 11 at 088eb28e2f004078 nip 100b5974 lr 100aa794 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.195380] neutron-rootwra[30098]: unhandled signal 11 at 88c939e32208 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:31:52 gligar kernel: [88365.362374] neutron-rootwra[30106]: unhandled signal 11 at 882c58ad2800f04f nip 3fffaef81220 lr 3fffaef811a0 code 30001 | Oct 16 23:32:27 gligar kernel: [88400.966976] neutron-rootwra[30341]: unhandled signal 11 at 88d1fbe922001008 nip 100c8b28 lr 10060384 code 30001 | Oct 16 23:32:47 gligar kernel: [88420.953053] neutron-rootwra[30412]: unhandled signal 11 at 11b6629054008000 nip 3fff9a864ac4 lr 3fff9a84c42c code 30001 | Oct 16 23:34:49 gligar kernel: [88542.778503] neutron-rootwra[30977]: unhandled signal 11 at 88540f0010a8 nip 100aa768 lr 100b74e8 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.700721] neutron-openvsw[29739]: unhandled signal 11 at 08bfcbf721a8 nip 100ab390 lr 100b7c38 code 30001 | Oct 16 23:35:23 gligar kernel: [88576.804961] init: neutron-plugin-openvswitch-agent main process (29739) killed by SEGV signal | Oct 16 23:36:01 gligar kernel: [88614.995497] nova-compute[31662]: unhandled signal 11 at 8846c1c81f004008 nip 1014c2f0 lr 10151080 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.110735] nova-compute[4331]: unhandled signal 11 at 88befae9220010a8 nip 100b5c8c lr 1014c734 code 30001 | Oct 16 23:36:02 gligar kernel: [88615.219436] init: nova-compute main process (4331) killed by SEGV signal | Oct 17 03:59:56 gligar kernel: [104449.890256] landscape-packa[63283]: unhandled signal 11 at 02f8 nip 101abeac lr 100a8738 code 30001 | Oct 17 04:05:00 gligar kernel: [104753.718195] sudo[63915]: unhandled signal 11 at 08e06105d1dcfff8 nip 3fffb15cf7e4 lr 3fffb15cfa00 code 30001 | hloeung@floette:~$ zgrep -E '(SEGV)|(unhandled signal 11)' /var/log/syslog.7.gz | Oct 14 16:55:30 floette kernel: [149326.697938] rsync[9915]: unhandled signal 11 at 37cb nip 3fffa242d054 lr 3fffa2426560 code 30001 | Oct 14 21:05:57 floette kernel: [164353.333697] apparmor_parser[102284]: unhandled signal 11 at 08680f00 nip 1004bbf8 lr 10028de4 code 30001 | Oct 14 22:21:24 floette kernel: [168880.481778] neutron-rootwra[153488]: unhandled signal 11 at 8860fbe21fa8 nip 100aa768 lr 100b74e8 code 30001 | Oct 14 22:21:26 floette kernel: [168882.078608] neutron-openvsw[4546]: unhandled signal 11 at 8822cbf03d08 nip 100aa764 lr 100e6900 code 30001 | Oct 14 22:21:37 floette kernel: [168893.597834] init: neutron-plugin-openvswitch-agent main process (4546) killed by SEGV signal | Oct 14 22:21:39 floette kernel: [168894.949777] nova-rootwrap[153708]: unhandled signal 11 at 88d495c93ca8 nip 100a57d4 lr 100ab42c code 30001 | Oct 14 22:21:43 floette kernel: [168898.973700] neutron-rootwra[153847]: unhandled signal 11 at 08c90df31820 nip 101ac260 lr 101ad92c code 30001 | Oct 14 22:21:44 floette kernel: [168900.785421] neutron-rootwra[153850]: unhandled signal 11 at 88d87b783fa8 nip 101abf40 lr 100d9cac
[Kernel-packages] [Bug 1512185] UdevLog.txt
apport information
** Attachment added: "UdevLog.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510820/+files/UdevLog.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu package. P
[Kernel-packages] [Bug 1512185] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510819/+files/UdevDb.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu package. Plea
[Kernel-packages] [Bug 1512185] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510817/+files/ProcModules.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu pa
[Kernel-packages] [Bug 1512185] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510811/+files/CurrentDmesg.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu
[Kernel-packages] [Bug 1512185] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510812/+files/IwConfig.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu package.
[Kernel-packages] [Bug 1512185] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510821/+files/WifiSyslog.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-gen
[Kernel-packages] [Bug 1512185] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510814/+files/Lspci.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu package. Please
[Kernel-packages] [Bug 1512185] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510816/+files/ProcInterrupts.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubu
[Kernel-packages] [Bug 1512185] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510815/+files/ProcCpuinfo.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu pa
[Kernel-packages] [Bug 1512185] RelatedPackageVersions.txt
apport information
** Attachment added: "RelatedPackageVersions.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510818/+files/RelatedPackageVersions.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not
[Kernel-packages] [Bug 1512185] KvmCmdLine.txt
apport information
** Attachment added: "KvmCmdLine.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510813/+files/KvmCmdLine.txt
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-lts-vivid package in Ubuntu:
New
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
---
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.18
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
Package: qemu (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: console=ttyS0,9600n8r ro
ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images trusty uec-images
Uname: Linux 3.19.0-31-generic aarch64
UnreportableReason: This is not an official Ubuntu pack
[Kernel-packages] [Bug 1512185] Re: qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
apport information
** Also affects: linux-meta-lts-vivid (Ubuntu)
Importance: Undecided
Status: New
** Tags added: apport-collected trusty uec-images
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
- I'm also not sure if this is related to LP:1505564, which is for
- amd64/x86_64.
+ I'm also not sure if this is related to LP:1505564, which is for amd64/x86_64.
+ ---
+ AlsaDevices:
+ total 0
+ crw-rw 1 root audio 116, 1 Oct 25 17:42 seq
+ crw-rw 1 root audio 116, 33 Oct 25 17:42 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.14.1-0ubuntu3.18
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 14.04
+ Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize
libusb: -99
+ Package: qemu (not installed)
+ PciMultimedia:
+
+ ProcEnviron:
+ TERM=xterm
+ PATH=(custom, no user)
+ XDG_RUNTIME_DIR=
+ LANG=en_GB
+ SHELL=/bin/bash
+ ProcFB:
+
+ ProcKernelCmdLine: console=ttyS0,9600n8r ro
+ ProcVersionSignature: Ubuntu 3.19.0-31.36~14.04.1-generic 3.19.8-ckt7
+ RfKill: Error: [Errno 2] No such file or directory
+ Tags: trusty uec-images trusty uec-images
+ Uname: Linux 3.19.0-31-generic aarch64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm
+ _MarkForUpload: True
** Attachment added: "BootDmesg.txt"
https://bugs.launchpad.net/bugs/1512185/+attachment/4510810/+files/BootDmesg.txt
--
You rece
[Kernel-packages] [Bug 1512185] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:
apport-collect 1512185
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
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/1512185
Title:
qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO],
..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Status in linux package in Ubuntu:
Incomplete
Status in qemu package in Ubuntu:
New
Bug description:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also
a bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for
amd64/x86_64.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512185/+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 1359689] Re: cryptsetup password prompt not shown
I'm currently having the same issue with my system :/ I went through all the mentioned workarounds in this thread but unfortunately none of them have worked. I used the configs listed below via "sudo vim /etc/default/grub". Used "sudo update-grub" once the grub configuration was saved and restarted the machine. Ubuntu would always boot into a blank/black screen at which point I have to insert my password blindly. Does anyone have any other suggestions or workarounds that I can try? Configs used: * GRUB_GFXPAYLOAD_LINUX=1920x1080 * GRUB_GFXPAYLOAD_LINUX=wxh * GRUB_GFXPAYLOAD_LINUX="text" * GRUB_GFXPAYLOAD_LINUX=text * GRUB_GFXMODE=1920x1080 * GRUB_GFXMODE=640x480 * GRUB_CMDLINE_LINUX_DEFAULT="splash" * GRUB_CMDLINE_LINUX_DEFAULT="" * GRUB_CMDLINE_LINUX_DEFAULT="quiet" System: * Linux x 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:21:08 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux * Ubuntu 14.04.3 LTS Release: 14.04 trusty * GeForce GTX 670/PCIe/SSE2 * NVIDIA UNIX x86_64 Kernel Module 346.96 Sun Aug 23 22:29:21 PDT 2015 -- 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/1359689 Title: cryptsetup password prompt not shown Status in xserver-xorg-driver-radeonhd: New Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Invalid Status in linux source package in Vivid: Triaged Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1359689/+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 1512185] [NEW] qemu-nbd on ARM64 deadlock? Stuck in rt_sigtimedwait([BUS ALRM IO], ..) and futex(0x7f749ec230, FUTEX_WAIT, ...)
Public bug reported:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix11:
| hloeung@swirlix11:~$ uname -a
| Linux swirlix11 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix11:~$ ps afx | grep qe\\mu-nbd
| 18149 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd3
/var/lib/nova/instances/84cac137-c1e4-46ac-894a-efcd55ef7e05/disk
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }'/stack
| hloeung@swirlix11:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{ print
$1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
| hloeung@swirlix11:~$ sudo strace -f -p 18149
| Process 18149 attached with 3 threads
| [pid 18150] rt_sigtimedwait([BUS ALRM IO], NULL, NULL, 8
| [pid 18149] futex(0x7f749ec230, FUTEX_WAIT, 18152, NULL
| ... (hangs here) ...
We're using the QEMU package backported from Vivid as per LP:1457639
| hloeung@swirlix11:~$ apt-cache policy qemu-utils
| qemu-utils:
| Installed: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Candidate: 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1
| Version table:
| *** 1:2.2+dfsg-5expubuntu9.5+bug1457639~ubuntu14.04.1 0
| 500
http://ppa.launchpad.net/canonical-is-sa/arm64-infra-workarounds/ubuntu/
trusty/main arm64 Packages
I'm also not sure if this is related to LP:1505564, which is for
amd64/x86_64.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Also affects: qemu (Ubuntu)
Importance: Undecided
Status: New
** Description changed:
Hi,
We're seeing this often on our HP Moonshot ARM64 nova-compute nodes
where qemu-nbd processes would lock up. At the same time, there's also a
bunch of kernel spew as follows:
| [605282.018238] block nbd3: Attempted send on closed socket
| [605282.018242] block nbd3: Attempted send on closed socket
| [605282.018245] block nbd3: Attempted send on closed socket
| [605282.018249] block nbd3: Attempted send on closed socket
swirlix01:
| hloeung@swirlix01:~$ uname -a
| Linux swirlix01 3.19.0-30-generic #34~14.04.1-Ubuntu SMP Fri Oct 2 22:15:46
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix01:~$ ps afx | grep qe\\mu-nbd
| 27782 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd10
/var/lib/nova/instances/ba50751e-56d7-4bc4-8742-1193fe7a138e/disk
| hloeung@swirlix01:~$ sudo cat /proc/$(ps afx | grep qe\\mu-nbd | awk '{
print $1 }')/stack
| [] __switch_to+0x74/0x8c
| [] futex_wait_queue_me+0xf4/0x184
| [] futex_wait+0x154/0x24c
| [] do_futex+0x1a0/0x9ec
| [] SyS_futex+0x98/0x1cc
| [] el0_svc_naked+0x20/0x28
| [] 0x
swirlix08:
| hloeung@swirlix08:~$ uname -a
| Linux swirlix08 3.19.0-31-generic #36~14.04.1-Ubuntu SMP Thu Oct 8 10:50:10
UTC 2015 aarch64 aarch64 aarch64 GNU/Linux
| hloeung@swirlix08:~$ ps afx | grep qe\\mu-nbd
| 31976 ?Ssl0:00 /usr/bin/qemu-nbd -c /dev/nbd6
/var/lib/nova/instances/92ceb061-2ea4-4212-be20-ab0ded6eb3cd/disk
| hloeung@swirlix08:~$ sudo cat /proc/$(ps afx | grep qe\\mu-
[Kernel-packages] [Bug 1511383] Re: Complete Desktop freeze when watching video using VLC
gnufied, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-1.18 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1511383 Title: Complete Desktop freeze when watching video using VLC Status in linux package in Ubuntu: Incomplete Bug description: I was watching some twitch video using VLC and after awhile the desktop froze completely. I couldn't kill Xorg or switch to ttyys (via Alt-Control-F1..F4) and my only option was a hard reboot. I am using Thinkpad T450s with all the latest patches applied. I am attaching relevant log file which should help narrow down the problem. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Oct 29 06:53:54 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-10-28 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=15059329-95a6-482f-b14c-3eb08b5fd404 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET53WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET53WW(1.18):bd09/14/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-vid
[Kernel-packages] [Bug 1511383] [NEW] Complete Desktop freeze when watching video using VLC
You have been subscribed to a public bug: I was watching some twitch video using VLC and after awhile the desktop froze completely. I couldn't kill Xorg or switch to ttyys (via Alt- Control-F1..F4) and my only option was a hard reboot. I am using Thinkpad T450s with all the latest patches applied. I am attaching relevant log file which should help narrow down the problem. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Oct 29 06:53:54 2015 DistUpgraded: Fresh install DistroCodename: wily DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5036] InstallationDate: Installed on 2015-10-28 (1 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20BXCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=15059329-95a6-482f-b14c-3eb08b5fd404 ro noprompt persistent quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET53WW (1.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BXCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET53WW(1.18):bd09/14/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BXCTO1WW dmi.product.version: ThinkPad T450s dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Thu Oct 29 05:21:27 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1133 vendor LGD xserver.version: 2:1.17.2-1ubuntu9 ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 freeze latest-bios-1.18 ubuntu wily -- Complete Desktop freeze when watching video using VLC https://bugs.launchpad.net/bugs/1511383 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1218691] Re: Possible missing firmware /lib/firmware/radeon/*.bin
Maybe we should offer those optional firmware files for Ubuntu users. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1218691 Title: Possible missing firmware /lib/firmware/radeon/*.bin Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Saucy: Fix Released Status in Debian: Fix Released Bug description: When updating the kernel today to 3.11.0-4-generic I saw the same warning messages I saw when I upgraded to 3.11.0-3-generic update-initramfs: Generating /boot/initrd.img-3.11.0-4-generic W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon Further digging found bug 1183777 As mentioned in that bug, I did contact the named person: "Hi, I'm still seeing the errors for KAVERI firmwares being missing in the latest kernel : phillw@piglet:~$ uname -a Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux As the 1st Beta is creeping up fast, do you need this raising as a new bug? Regards, Phill." The reply is: "As far as I can tell, the KAVERI firmware (and hardware) is not publicly available yet, so that's not a bug with the linux-firmware package. If you want to file a new bug about the warning messages, please file it against the linux (kernel) package. Until the firmware is available, I'm not really sure what the fix for that would be, other than removing/commenting out the relevant Kaveri lines in the radeon kernel code." Please find attached bug report as requested. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phillw 1965 F lxpanel CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Aug 30 02:37:54 2013 HibernationDevice: RESUME=UUID=d98ac0ad-5c96-4382-8195-23b44e056358 InstallationDate: Installed on 2013-06-29 (61 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130628) MachineType: Packard Bell EasyNote LJ71 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-3-generic root=UUID=69c7aa0f-ccd0-4ac4-8930-e6f0efda9e6b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2009 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote LJ71 dmi.board.vendor: Packard Bell dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnPackardBell:bvrV1.03:bd09/22/2009:svnPackardBell:pnEasyNoteLJ71:pvrV1.03:rvnPackardBell:rnEasyNoteLJ71:rvrV1.03:cvnPackardBell:ct10:cvrV1.03: dmi.product.name: EasyNote LJ71 dmi.product.version: V1.03 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1218691/+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 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
Further information: The 4.2.5 mainline was tested with all drivers loading. This may be an indication that the problem is with one of the 4 drivers that did not load, however I can't seem to find a way to unload those 4 drivers without stopping the system from booting. -- 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/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Triaged Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+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 1495043] Re: Suspend/Resume Regression 3.19.0-28-generic Dell xps15
Sorry for not explaining clearly. Testing of the upstream kernel did originally work but the kernel that was tested had some DKMS drivers that would not load: [code] Consult /var/lib/dkms/bbswitch/0.7/build/make.log for more information. Consult /var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/make.log for more information. Consult /var/lib/dkms/vboxhost/5.0.4/build/make.log for more information. Consult /var/lib/dkms/nvidia-346/346.59/build/make.log for more information. [/code] The original upstream kernel that was tested was version 3.19.31, when that kernel made it in to the distro, the problem was not fixed. I have since tested mainline kernel 4.2.5, and the problem also is not fixed. So the mainline kernel does not fix the problem. I hope this is clearer. ** Tags removed: kernel-fixed-upstream -- 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/1495043 Title: Suspend/Resume Regression 3.19.0-28-generic Dell xps15 Status in linux package in Ubuntu: Triaged Bug description: Suspend resume was working on 3.19.0-26 but 3.19.0-28 appears to suspend, but no longer resumes. Relevant portion of dmesg info using pm-trace is as follows: [1.168740] registered taskstats version 1 [1.170526] Key type trusted registered [1.174836] Key type encrypted registered [1.174843] AppArmor: AppArmor sha1 policy hashing enabled [1.176721] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input3 [1.398911] evm: HMAC attrs: 0x1 [1.399640] Magic number: 0:469:661 [1.399643] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:642 [1.399655] hash matches /build/linux-5xFjum/linux-3.19.0/drivers/base/power/main.c:738 [1.399670] block ram14: hash matches [1.399692] platform PNP0C0A:00: hash matches [1.399711] battery PNP0C0A:00: hash matches [1.399793] rtc_cmos 00:01: setting system clock to 1976-02-02 02:39:41 UTC (192076781) [1.399886] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.399887] EDD information not available. [1.399970] PM: Hibernation image not present or could not be loaded. [1.400304] Freeing unused kernel memory: 1408K (81d36000 - 81e96000) [1.400305] Write protecting the kernel read-only data: 12288k To reproduce the bug: 1) Boot into Ubuntu Gnome with kernel 3.19.0.28-generic 2) Log in to desktop. 3) Close laptop lid 4) Wait about 10 seconds (doesn't seem to be critical how long you wait) 5) Open laptop lid. What happens: The keyboard backlight and the power button light come on, but the screen remains blank. Using Ctr-Alt-F1 does nothing (can't get to a virtual console, indicating that it's not just X that has stopped) What I expect to happen: On opening of the laptop lid, I expect the lockscreen to show. Other info: This laptop has nvidia graphics disabled using nvidia-prime ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mark 1566 F pulseaudio /dev/snd/controlC0: mark 1566 F pulseaudio CurrentDesktop: GNOME Date: Sat Sep 12 19:26:03 2015 HibernationDevice: RESUME=UUID=ff91bc8d-f7ef-4650-81e0-608068f4f8cb InstallationDate: Installed on 2015-08-31 (12 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. XPS 15 9530 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=b69e369b-42c8-4f85-8a2c-dcfec06b7d88 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/30/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: XPS 15 9530 dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA09:bd07/30/2015:svnDellInc.:pnXPS159530:pvrA09:rvnDellInc.:rnXPS159530:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 15 9530 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1495043/+subscriptions -- Mailing list: https://launchpad
[Kernel-packages] [Bug 1509803] Re: Bluetooth Will not work
Can you use the grub menu to boot into an older 3.19 kernel and see if it works, I have been having a few issues with the latest 3.19 kernel and haven't had the time to figure out what is causing the issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work Status in linux-lts-vivid package in Ubuntu: New Bug description: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-32-generic
[Kernel-packages] [Bug 1512152] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1512152 Title: stack traces in dmesg on boot i915 related on macbook air Status in linux package in Ubuntu: Confirmed Bug description: Noticed stack traces in dmesg after booting Wily on a macbook air. See attached logs. Seems to be related to i915 chipset. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bladernr 2027 F pulseaudio /dev/snd/controlC1: bladernr 2027 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 1 15:34:03 2015 HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152 InstallationDate: Installed on 2015-10-21 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020) MachineType: Apple Inc. MacBookAir6,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B19.1506050547 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C1E88140C3E6CF dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C1E88140C3E6CF dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B19.1506050547:bd06/05/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF: dmi.product.name: MacBookAir6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512152/+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 1511131] Re: Bluetooth LED always lightning
David Baumann, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (Marcel Holtmann, Gustavo Padovan, and Johan Hedberg, CC linux- bluetooth)? Please provide a direct URL to your newly made report when it becomes available so that it may be tracked. Thank you for your understanding. ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Summary changed: - Bluetooth LED always lightning + Bluetooth LED always lit up -- 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/1511131 Title: Bluetooth LED always lit up Status in linux package in Ubuntu: Triaged Bug description: So no matter if I enable or disable bluetooth on my laptop, even if I rfkill it, the bluetooth led is turned on all the time. If you need any more information, please just ask. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2403 F pulseaudio /dev/snd/pcmC0D0p: david 2403 F...m pulseaudio /dev/snd/controlC0: david 2403 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 22:47:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-13 (502 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-07-20 (100 days ago) dmi.bios.date: 09/29/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/29/2015:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511131/+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 1512152] [NEW] stack traces in dmesg on boot i915 related on macbook air
Public bug reported: Noticed stack traces in dmesg after booting Wily on a macbook air. See attached logs. Seems to be related to i915 chipset. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bladernr 2027 F pulseaudio /dev/snd/controlC1: bladernr 2027 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 1 15:34:03 2015 HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152 InstallationDate: Installed on 2015-10-21 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020) MachineType: Apple Inc. MacBookAir6,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B19.1506050547 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C1E88140C3E6CF dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C1E88140C3E6CF dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B19.1506050547:bd06/05/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF: dmi.product.name: MacBookAir6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- 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/1512152 Title: stack traces in dmesg on boot i915 related on macbook air Status in linux package in Ubuntu: New Bug description: Noticed stack traces in dmesg after booting Wily on a macbook air. See attached logs. Seems to be related to i915 chipset. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bladernr 2027 F pulseaudio /dev/snd/controlC1: bladernr 2027 F pulseaudio CurrentDesktop: Unity Date: Sun Nov 1 15:34:03 2015 HibernationDevice: RESUME=UUID=1ec334c0-b29f-454a-9668-0e6f5cc2d152 InstallationDate: Installed on 2015-10-21 (11 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151020) MachineType: Apple Inc. MacBookAir6,1 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=3d44-163a-4386-9871-83e8515efd90 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA61.88Z.0099.B19.1506050547 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-35C1E88140C3E6CF dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir6,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-35C1E88140C3E6CF dmi.modalias: dmi:bvnAppleInc.:bvrMBA61.88Z.0099.B19.1506050547:bd06/05/2015:svnAppleInc.:pnMacBookAir6,1:pvr1.0:rvnAppleInc.:rnMac-35C1E88140C3E6CF:rvrMacBookAir6,1:cvnAppleInc.:ct10:cvrMac-35C1E88140C3E6CF: dmi.product.name: MacBookAir6,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1512152/+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 1512149] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- 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/1512149 Title: package linux-image-4.2.0-16-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: No idea. When I run ubuntu-bug linux, I get the error: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. Since that gives no clue as to what package it's talking about, it could be a Microsoft error message. All I did was let Update Manger upgrade Ubuntu to 15.10 at its own suggestion, unsuccessfully, apparently. During the process, I got dependency problem errors on kernel packages. It took a while, but the machine did reboot. Now I have: $ uname -a Linux Inspiron600m 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:01 UTC 2015 i686 i686 i686 GNU/Linux (which I believe is what I had before the upgrade started). So I did this: $ sudo apt-get check Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-4.2.0-16-generic : Depends: linux-image-4.2.0-16-generic but it is not installed linux-image-generic : Depends: linux-image-4.2.0-16-generic but it is not installed E: Unmet dependencies. Try using -f. $ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: g++-4.9 gir1.2-vte-2.90 gstreamer0.10-gconf libapt-inst1.5 libavcodec56 libavformat56 libavresample2 libavutil54 libboost-filesystem1.55.0 libboost-iostreams1.55.0 libboost-system1.54.0 libboost-system1.55.0 libboost-thread1.54.0 libcamel-1.2-49 libclass-load-perl libdvbpsi9 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16 libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libept1.4.12 libexiv2-13 libfarstream-0.1-0 libgdata19 libgegl-0.2-0 libgnome-bluetooth11 libgphoto2-port10 libgsoap5 libhogweed2 libinput7 libjson0 libkf5kcmutils-data libkf5kcmutils5 libkomparediff2-4 libkonq-common libkonq5-templates libkonq5abi1 liblist-allutils-perl libmirclient8 libmircommon3 libmirprotobuf0 libnettle4 libplist2 libpoppler49 libpostproc52 libprotobuf9 libreadline5 libregexp-common-perl libstdc++-4.9-dev libswscale3 libvncclient0 libvncserver0 libvpx1 libx264-142 libxcb-util0 mir-client-platform-mesa2 python-commandnotfound python3-crypto upstart-bin Use 'apt-get autoremove' to remove them. The following extra packages will be installed: linux-image-4.2.0-16-generic Suggested packages: fdutils linux-doc-4.2.0 linux-source-4.2.0 linux-tools The following NEW packages will be installed: linux-image-4.2.0-16-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/16.9 MB of archives. After this operation, 38.8 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 292072 files and directories currently installed.) Preparing to unpack .../linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) That (finally) tells me the real problem is that Update Manager tried to install an upgrade that doesn't "support a non-PAE CPU". Strictly speaking, as I understand it, the Centrino on this machine has the PAE capability but not the ability to tell the OS the ability is there, as I had to start with a "non-PAE" Ubuntu installer and everything through 15.04 seems to have worked just fine. I guess since the machine still works, I can purge the kernel packages that won't work and see what problems I have to deal with in the future. It is unfortunate that we allow industry to force us to buy new computers when 99.99% of all computer
[Kernel-packages] [Bug 1492850] Re: Dell pro venue 11 - No wireless connections after sleep
So obviously one of the quirks in /usr/lib/pm-utils/sleep.d works around this kernel bug. We need to find out which. Can you please move the files in that directory to some other place one by one and do a "sudo pm-suspend" / resume cycle until it starts failing? That's the "magic" hook then. Which one is it? After that exercise, move the hooks back to /usr/lib/pm-utils/sleep.d/. Thanks! ** This bug is no longer a duplicate of bug 1422143 No wifi connection after suspend with systemd due to missing "wpa_cli suspend" ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1492850 Title: Dell pro venue 11 - No wireless connections after sleep Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: New Bug description: I try for a long time to set-up the wifi for my dell pro venue 11 v7130 (wifi chipset Intel Corporation Wireless 7260). The wifi connection is perfect until the computer is suspend. After a suspend, even activating the wifi from network manager is impossible. After suspend even an exit doesn't reconnect to the wifi connection. It seems that the wifi chipset is off and it's impossible to wake up. Recently 15.04 has been update to 4.2 RC8. Nothing new ! A file unload_modules has been created. /etc/pm/config.d with SUSPEND_MODULES="$SUSPEND_MODULES iwlwifi" without any effect. sudo service network-manager restart doesn't work too ! Before suspend @utopie:~$ sudo lshw -C network *-network description: Interface réseau sans fil produit: Wireless 7260 fabriquant: Intel Corporation identifiant matériel: 0 information bus: pci@:01:00.0 nom logique: wlan0 version: 83 numéro de série: 5c:51:4f:d9:2e:75 bits: 64 bits horloge: 33MHz fonctionnalités: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=iwlwifi driverversion=4.2.0-040200rc8-generic firmware=25.30.13.0 ip=192.168.0.50 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn ressources: irq:49 mémoire:f7d0-f7d01fff *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes After suspend (no more wifi chipset !). @utopie:~$ sudo lshw -C network *-network DÉSACTIVÉ description: Ethernet interface identifiant matériel: 1 nom logique: wwan0 numéro de série: 1e:51:e0:b8:e1:da fonctionnalités: ethernet physical configuration: broadcast=yes driver=cdc_mbim driverversion=22-Aug-2005 firmware=CDC MBIM link=no multicast=yes --- ApportVersion: 2.17.2-0ubuntu1.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: baly 1169 F pulseaudio /dev/snd/controlC1: baly 1169 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=729324f1-42a5-45f8-9585-f6e0169f2d64 InstallationDate: Installed on 2015-04-23 (144 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Dell Inc. Venue 11 Pro 7130 vPro Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-29-generic.efi.signed root=UUID=35cde4a5-bbc3-442b-b239-d3f917925a94 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-29.31-generic 3.19.8-ckt6 RelatedPackageVersions: linux-restricted-modules-3.19.0-29-generic N/A linux-backports-modules-3.19.0-29-generic N/A linux-firmware 1.143.3 Tags: vivid UdevLog: Error: [Errno 2] Aucun fichier ou dossier de ce type: '/var/log/udev' Uname: Linux 3.19.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0T69G0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA10:bd02/18/2014:svnDellInc.:pnVenue11Pro7130vPro:pvr01:rvnDellInc.:rn0T69G0:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Venue 11 Pro 7130 vPro dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1492850/+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 1512149] [NEW] package linux-image-4.2.0-16-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 1
Public bug reported: No idea. When I run ubuntu-bug linux, I get the error: The problem cannot be reported: This is not an official Ubuntu package. Please remove any third party package and try again. Since that gives no clue as to what package it's talking about, it could be a Microsoft error message. All I did was let Update Manger upgrade Ubuntu to 15.10 at its own suggestion, unsuccessfully, apparently. During the process, I got dependency problem errors on kernel packages. It took a while, but the machine did reboot. Now I have: $ uname -a Linux Inspiron600m 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:01 UTC 2015 i686 i686 i686 GNU/Linux (which I believe is what I had before the upgrade started). So I did this: $ sudo apt-get check Reading package lists... Done Building dependency tree Reading state information... Done You might want to run 'apt-get -f install' to correct these. The following packages have unmet dependencies: linux-image-extra-4.2.0-16-generic : Depends: linux-image-4.2.0-16-generic but it is not installed linux-image-generic : Depends: linux-image-4.2.0-16-generic but it is not installed E: Unmet dependencies. Try using -f. $ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following packages were automatically installed and are no longer required: g++-4.9 gir1.2-vte-2.90 gstreamer0.10-gconf libapt-inst1.5 libavcodec56 libavformat56 libavresample2 libavutil54 libboost-filesystem1.55.0 libboost-iostreams1.55.0 libboost-system1.54.0 libboost-system1.55.0 libboost-thread1.54.0 libcamel-1.2-49 libclass-load-perl libdvbpsi9 libebackend-1.2-7 libebook-1.2-14 libebook-contacts-1.2-0 libecal-1.2-16 libedata-book-1.2-20 libedata-cal-1.2-23 libedataserver-1.2-18 libept1.4.12 libexiv2-13 libfarstream-0.1-0 libgdata19 libgegl-0.2-0 libgnome-bluetooth11 libgphoto2-port10 libgsoap5 libhogweed2 libinput7 libjson0 libkf5kcmutils-data libkf5kcmutils5 libkomparediff2-4 libkonq-common libkonq5-templates libkonq5abi1 liblist-allutils-perl libmirclient8 libmircommon3 libmirprotobuf0 libnettle4 libplist2 libpoppler49 libpostproc52 libprotobuf9 libreadline5 libregexp-common-perl libstdc++-4.9-dev libswscale3 libvncclient0 libvncserver0 libvpx1 libx264-142 libxcb-util0 mir-client-platform-mesa2 python-commandnotfound python3-crypto upstart-bin Use 'apt-get autoremove' to remove them. The following extra packages will be installed: linux-image-4.2.0-16-generic Suggested packages: fdutils linux-doc-4.2.0 linux-source-4.2.0 linux-tools The following NEW packages will be installed: linux-image-4.2.0-16-generic 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. Need to get 0 B/16.9 MB of archives. After this operation, 38.8 MB of additional disk space will be used. Do you want to continue? [Y/n] Y (Reading database ... 292072 files and directories currently installed.) Preparing to unpack .../linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb ... This kernel does not support a non-PAE CPU. dpkg: error processing archive /var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 1 Examining /etc/kernel/postrm.d . run-parts: executing /etc/kernel/postrm.d/initramfs-tools 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic run-parts: executing /etc/kernel/postrm.d/zz-update-grub 4.2.0-16-generic /boot/vmlinuz-4.2.0-16-generic Errors were encountered while processing: /var/cache/apt/archives/linux-image-4.2.0-16-generic_4.2.0-16.19_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) That (finally) tells me the real problem is that Update Manager tried to install an upgrade that doesn't "support a non-PAE CPU". Strictly speaking, as I understand it, the Centrino on this machine has the PAE capability but not the ability to tell the OS the ability is there, as I had to start with a "non-PAE" Ubuntu installer and everything through 15.04 seems to have worked just fine. I guess since the machine still works, I can purge the kernel packages that won't work and see what problems I have to deal with in the future. It is unfortunate that we allow industry to force us to buy new computers when 99.99% of all computers currently used privately and in business as computers (as opposed to gaming machines) are so underutilized that buying a new one is 99.99% waste. Let's see: $ cat /proc/version_signature Ubuntu 3.19.0-15.15-generic 3.19.3 $ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Connection timed out ...but there's plenty in the log: $ sudo lspci -vnvn 00:00.0 Host bridge [0600]: Intel Corporation 82855PM Processor to I/O Controller [8086:3340] (rev 03) Subsystem: Dell Device [1028:011e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Ste
[Kernel-packages] [Bug 1448609] Re: bluetooth device works but does not pair any device
The issue is solved with the release of 15.10, thanks everyone for the help. ** Summary changed: - My laptop bluetooth device is working but it is not detecting any of the other devices also no other device detects my laptop. + bluetooth device works but does not pair any device ** This bug is no longer a duplicate of bug 1464576 Realtek Bluetooth [0bda:b001] does not work at all on 14.04.2 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1448609 Title: bluetooth device works but does not pair any device Status in linux package in Ubuntu: Fix Released Bug description: device is on and visible, I tried every thing but bluetooh device is not detecting any other device Laptop model - HP15 R203TX Ubuntu - 15.04 PS - same problem was there in 14.10 Device is Broadcom Bluetooth Adapter ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: evince 3.14.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Sun Apr 26 12:40:57 2015 InstallationDate: Installed on 2015-04-24 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: roopamshukla 1691 F pulseaudio /dev/snd/controlC1: roopamshukla 1691 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=9010676a-35c4-4a4a-a206-2df1e6cf87ca InstallationDate: Installed on 2015-04-24 (4 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP 15 Notebook PC Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic.efi.signed root=UUID=13cc9173-eda0-4add-8ed6-25fa5416d0fd ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 Tags: vivid UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.19.0-15-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/18/2014 dmi.bios.vendor: Insyde dmi.bios.version: F.36 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 2337 dmi.board.vendor: Hewlett-Packard dmi.board.version: 05.24 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.36:bd12/18/2014:svnHewlett-Packard:pnHP15NotebookPC:pvr098F120600087:rvnHewlett-Packard:rn2337:rvr05.24:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP 15 Notebook PC dmi.product.version: 098F120600087 dmi.sys.vendor: Hewlett-Packard --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 InstallationDate: Installed on 2015-04-24 (7 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) Package: linux (not installed) Tags: vivid Uname: Linux 4.0.1-040001-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1448609/+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 1511131] Re: Bluetooth LED always lightning
So I bootet into non-graphics mode, and rfkilled the device - the LED is still lightning. ** Tags added: kernel-bug-exists-upstream kernel-bug-exists- upstream-4.3-rc7 -- 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/1511131 Title: Bluetooth LED always lightning Status in linux package in Ubuntu: Incomplete Bug description: So no matter if I enable or disable bluetooth on my laptop, even if I rfkill it, the bluetooth led is turned on all the time. If you need any more information, please just ask. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2403 F pulseaudio /dev/snd/pcmC0D0p: david 2403 F...m pulseaudio /dev/snd/controlC0: david 2403 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 22:47:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-13 (502 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-07-20 (100 days ago) dmi.bios.date: 09/29/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/29/2015:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511131/+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 1359689] Re: cryptsetup password prompt not shown
I am also affected by this bug since Kernel 3.19.0-29 with Ubuntu 15.04 on a Lenovo T450s with inttegarted Intel graphics. -- 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/1359689 Title: cryptsetup password prompt not shown Status in xserver-xorg-driver-radeonhd: New Status in linux package in Ubuntu: Triaged Status in linux source package in Utopic: Invalid Status in linux source package in Vivid: Triaged Bug description: Currently in utopic the following happens when booting an encrypted setup: Press enter in grub, after a while screen freezes (or turns completely black) and stays like that. When I press the down key, I can see the password prompt. When I press the up key again, I get to the graphical password prompt. This is demonstrated in the following screencast: https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing Maybe this is related to the version of plymouth utopic currently uses, a similar debian bug report seems to be resolved with a newer version 0.9.0-6, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752. --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True --- ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth DistroRelease: Ubuntu 14.10 InstallationDate: Installed on 2014-08-21 (0 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821) MachineType: Dell Inc. Precision M4600 Package: plymouth 0.9.0-0ubuntu3 PackageArchitecture: amd64 ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Tags: utopic TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth Uname: Linux 3.16.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 03/10/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4600 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-radeonhd/+bug/1359689/+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 1509803] Re: Bluetooth Will not work
I've already done all the hardware related troubleshooting. Plus the fact that its a brand new laptop, and as stated before, I plugged a windows drive, to get the correct driver,and bluetooth works just fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work Status in linux-lts-vivid package in Ubuntu: New Bug description: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-32-gen
[Kernel-packages] [Bug 1511131] Re: Bluetooth LED always lightning
** Attachment added: "make.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511131/+attachment/4510461/+files/make.log -- 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/1511131 Title: Bluetooth LED always lightning Status in linux package in Ubuntu: Incomplete Bug description: So no matter if I enable or disable bluetooth on my laptop, even if I rfkill it, the bluetooth led is turned on all the time. If you need any more information, please just ask. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2403 F pulseaudio /dev/snd/pcmC0D0p: david 2403 F...m pulseaudio /dev/snd/controlC0: david 2403 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 22:47:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-13 (502 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-07-20 (100 days ago) dmi.bios.date: 09/29/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/29/2015:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511131/+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 1511131] Re: Bluetooth LED always lightning
$ dpkg -i linux-* Vormals nicht ausgewähltes Paket linux-headers-4.3.0-040300rc7 wird gewählt. (Lese Datenbank ... 341021 Dateien und Verzeichnisse sind derzeit installiert.) Vorbereitung zum Entpacken von linux-headers-4.3.0-040300rc7_4.3.0-040300rc7.201510260712_all.deb ... Entpacken von linux-headers-4.3.0-040300rc7 (4.3.0-040300rc7.201510260712) ... Vormals nicht ausgewähltes Paket linux-headers-4.3.0-040300rc7-generic wird gewählt. Vorbereitung zum Entpacken von linux-headers-4.3.0-040300rc7-generic_4.3.0-040300rc7.201510260712_amd64.deb ... Entpacken von linux-headers-4.3.0-040300rc7-generic (4.3.0-040300rc7.201510260712) ... Vormals nicht ausgewähltes Paket linux-image-4.3.0-040300rc7-generic wird gewählt. Vorbereitung zum Entpacken von linux-image-4.3.0-040300rc7-generic_4.3.0-040300rc7.201510260712_amd64.deb ... Examining /etc/kernel/preinst.d/ run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic Done. Entpacken von linux-image-4.3.0-040300rc7-generic (4.3.0-040300rc7.201510260712) ... linux-headers-4.3.0-040300rc7 (4.3.0-040300rc7.201510260712) wird eingerichtet ... linux-headers-4.3.0-040300rc7-generic (4.3.0-040300rc7.201510260712) wird eingerichtet ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic Error! Bad return status for module build on kernel: 4.3.0-040300rc7-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.4/build/make.log for more information. : Unable to find an initial ram disk that I know how to handle. Will not try to make an initrd. Error! Bad return status for module build on kernel: 4.3.0-040300rc7-generic (x86_64) Consult /var/lib/dkms/nvidia-355/355.11/build/make.log for more information. linux-image-4.3.0-040300rc7-generic (4.3.0-040300rc7.201510260712) wird eingerichtet ... Running depmod. update-initramfs: deferring update (hook will be called later) Examining /etc/kernel/postinst.d. run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/dkms 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/virtualbox-dkms.0.crash' Error! Bad return status for module build on kernel: 4.3.0-040300rc7-generic (x86_64) Consult /var/lib/dkms/virtualbox/5.0.4/build/make.log for more information. ERROR: Cannot create report: [Errno 17] File exists: '/var/crash/nvidia-355.0.crash' Error! Bad return status for module build on kernel: 4.3.0-040300rc7-generic (x86_64) Consult /var/lib/dkms/nvidia-355/355.11/build/make.log for more information. run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic update-initramfs: Generating /boot/initrd.img-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/pm-utils 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/update-notifier 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/zz-extlinux 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.3.0-040300rc7-generic /boot/vmlinuz-4.3.0-040300rc7-generic Grub-Konfigurationsdatei wird generiert … Warnung: Werte ungleich 0 für »GRUB_TIMEOUT« werden, falls »GRUB_HIDDEN_TIMEOUT« aktiviert ist, nicht mehr unterstützt. Linux-Abbild gefunden: /boot/vmlinuz-4.3.0-040300rc7-generic initrd-Abbild gefunden: /boot/initrd.img-4.3.0-040300rc7-generic Linux-Abbild gefunden: /boot/vmlinuz-4.2.0-16-generic initrd-Abbild gefunden: /boot/initrd.img-4.2.0-16-generic Adding boot menu entry for EFI firmware configuration -- 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/1511131 Title: Bluetooth LED always lightning Status in linux package in Ubuntu: Incomplete Bug description: So no matter if I enable or disable bluetooth on my laptop, even if I rfkill it, the bluetooth led is turned on all the time. If you need any more information, please just ask. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2403 F pulseaudio /dev/snd/pcmC0D0p: david 2403 F...m pulseaudio /dev/snd/controlC0: david 2403 F pu
[Kernel-packages] [Bug 1510668] Re: No screen backlight after suspending and resuming on Macbook 4.1
Arvind Krein, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: xorg (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg (Ubuntu) Status: New => Incomplete ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- 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/1510668 Title: No screen backlight after suspending and resuming on Macbook 4.1 Status in linux package in Ubuntu: Incomplete Bug description: Hardware: Macbook-4.1 2008 Graphics: Intel® 965GM Software: ubuntu 15.10 tested kernels: 4.3.0-999-generic 4.1.0-040100rc2-genereic expected: After performing a suspend and resuming the screen back light is turned back on. observed: When trying to suspend and wake up after, the device comes back on but the screen back light stays off. If shined on with an external light source the content of the screen is still readable. steps to reproduce: 1. suspend (via pm-suspend, user interface, or automatic behavior 2. attempt to wake up 3. observe the back light of the screen ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.3.0-999-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 27 19:35:49 2015 DistUpgraded: 2015-10-25 04:06:39,623 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: webcamstudio, 0.73, 4.2.0-16-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00a1] Subsystem: Apple Inc. Device [106b:00a1] InstallationDate: Installed on 2015-08-12 (76 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Apple Inc. MacBook4,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-999-generic root=UUID=c4a2c5bc-c7c6-4887-a1e1-74ab339c4c7d ro acpi_osi=Linux acpi_baclight=vendor SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-25 (2 days ago) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: lib
[Kernel-packages] [Bug 1510668] [NEW] No screen backlight after suspending and resuming on Macbook 4.1
You have been subscribed to a public bug: Hardware: Macbook-4.1 2008 Graphics: Intel® 965GM Software: ubuntu 15.10 tested kernels: 4.3.0-999-generic 4.1.0-040100rc2-genereic expected: After performing a suspend and resuming the screen back light is turned back on. observed: When trying to suspend and wake up after, the device comes back on but the screen back light stays off. If shined on with an external light source the content of the screen is still readable. steps to reproduce: 1. suspend (via pm-suspend, user interface, or automatic behavior 2. attempt to wake up 3. observe the back light of the screen ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: xorg 1:7.7+7ubuntu4 Uname: Linux 4.3.0-999-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Oct 27 19:35:49 2015 DistUpgraded: 2015-10-25 04:06:39,623 DEBUG enabling apt cron job DistroCodename: wily DistroVariant: ubuntu DkmsStatus: webcamstudio, 0.73, 4.2.0-16-generic, x86_64: installed DpkgLog: ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00a1] Subsystem: Apple Inc. Device [106b:00a1] InstallationDate: Installed on 2015-08-12 (76 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Apple Inc. MacBook4,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.3.0-999-generic root=UUID=c4a2c5bc-c7c6-4887-a1e1-74ab339c4c7d ro acpi_osi=Linux acpi_baclight=vendor SourcePackage: xorg Symptom: display UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-25 (2 days ago) dmi.bios.date: 02/09/08 dmi.bios.vendor: Apple Inc. dmi.bios.version: MB41.88Z.00C1.B00.0802091535 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F22788A9 dmi.board.vendor: Apple Inc. dmi.board.version: PVT dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 2 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22788A9 dmi.modalias: dmi:bvnAppleInc.:bvrMB41.88Z.00C1.B00.0802091535:bd02/09/08:svnAppleInc.:pnMacBook4,1:pvr1.0:rvnAppleInc.:rnMac-F22788A9:rvrPVT:cvnAppleInc.:ct2:cvrMac-F22788A9: dmi.product.name: MacBook4,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.64-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4 version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3 xserver.bootTime: Sun Mar 24 12:22:50 2024 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5156 vendor AUO xserver.version: 2:1.17.2-1ubuntu9 ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 suspend ubuntu -- No screen backlight after suspending and resuming on Macbook 4.1 https://bugs.launchpad.net/bugs/1510668 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1507482] Re: ethtool self-test failed and creates a FW reset.
Hi, This bug for Ethernet device and your setup is Infiniband, we see "Link layer: InfiniBand" in the ibstat output. Please validate the fixes on ConnectX3 Ethernet interface. Thanks, Talat -- 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/1507482 Title: ethtool self-test failed and creates a FW reset. Status in linux package in Ubuntu: In Progress Bug description: On ConnectX3 device we try to run self-test and it’s failed, also seen that cause a FW reset. Steps to reproduce: ~# ethtool -t ens2 The test result is FAIL The test extra info: Interrupt Test -16 Link Test0 Speed Test 0 Register Test0 Loopback Test0 ~# dmesg [341548.619799] mlx4_core :07:00.0: command 0x31 timed out (go bit not cleared) [341548.803801] mlx4_core :07:00.0: command 0x49 timed out (go bit not cleared) [341548.803808] mlx4_core :07:00.0: device is going to be reset [341549.816587] mlx4_core :07:00.0: device was reset successfully [341549.823425] mlx4_en :07:00.0: Internal error detected, restarting device ~# cat /etc/os-release NAME="Ubuntu" VERSION="15.10 (Wily Werewolf)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu Wily Werewolf (development branch)" VERSION_ID="15.10" HOME_URL="http://www.ubuntu.com/"; SUPPORT_URL="http://help.ubuntu.com/"; BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"; ~# uname -r 4.2.0-7-generic ~# ethtool -i ens2 driver: mlx4_en version: 2.2-1 (Feb 2014) firmware-version: 2.34.5000 bus-info: :07:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: no supports-register-dump: no supports-priv-flags: yes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507482/+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 1511855] Re: Some Sony Dualshock 4 controllers do not work in kernel 3.15+
** Changed in: linux (Ubuntu) Importance: Undecided => Low -- 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/1511855 Title: Some Sony Dualshock 4 controllers do not work in kernel 3.15+ Status in linux package in Ubuntu: Incomplete Bug description: I'm testing in Ubuntu 15.10 with kernel 4.2.0-16.19 but this bug report actually applies to ALL kernels starting at 3.15 until the current 4.3rc7 and is not limited to Ubuntu. I have a brand new Sony DualShock 4 that seems to use a slightly different protocol than the hid-sony driver expects. I'm not sure why this controller is different. Maybe updated firmware from Sony or maybe because it has never been connected to a PS4. Whatever the case, the device descriptor size is different from what hid-sony expects and because of that it does not remap the descriptor table as required. This causes only the trackpad to function (the trackpad uses a different code path) and none of the other controls work. So basically the controller does not work at all. I have created a patch that fixes it. I have only tested the patch against kernel 4.2 and 4.3 but it's simple enough that it should be trivially portable to any 3.15+ kernel. The attached patch is based against the Ubuntu mainline-crack git v4.2 kernel. I posted to the LKML asking if the descriptor size check was even necessary but never got a response so I left it in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511855/+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 1511694] Re: USB tethering does not work after system Suspend
Asad Khan, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal: apport-collect 1511694 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1511694 Title: USB tethering does not work after system Suspend Status in linux package in Ubuntu: Incomplete Bug description: Recently upgraded to ubuntu 15.10 (Wily Werewolf) After the upgrade everything seems normal, USB tethering is working when system boots. After a while I put the system to suspended state. On awakening the system USB tethering does not work. After restarting the system it seems to work just fine and the process is repeated when I put the system to suspend again. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ubuntu-release-upgrader-core 1:15.10.14.1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: Unity Date: Fri Oct 30 15:52:16 2015 InstallationDate: Installed on 2015-05-23 (160 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to wily on 2015-10-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511694/+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 1511743] Re: 15.10 server - no keyboard in installer
Michael Flaig, thank you for reporting this and helping make Ubuntu better. Could you please plug in a different, working keyboard so the debug information requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511743/comments/1 may be gathered? ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1511743 Title: 15.10 server - no keyboard in installer Status in linux package in Ubuntu: Incomplete Bug description: After starting the 15.10 server setup on my fujitsu tx1320m1 server the keyboard is not working. I checked all USB Ports. The keyboard worked in grub. The keyboard is a Lenovo Keyboard and has USB 2.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511743/+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 1511196] Re: System wakeup disabled by ACPI
** Changed in: linux (Ubuntu) Importance: Undecided => Low -- 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/1511196 Title: System wakeup disabled by ACPI Status in linux package in Ubuntu: Incomplete Bug description: What you’re trying to achieve: 1. I was trying to 'suspend to ram' my Computer through Xubuntu. What steps you take: 1. Clicked the Xfce Blue Mouse Mascot. 2. Clicked the Logout icon from the XFCE Menu. 3. Clicked Suspend. What happens: 1. The computer simply shuts itself down without suspending to the ram and kills all the USB Ports (I used to use USB ports even when computer is suspended to ram). 2. The computer forces a fsck after hitting the power button again and recovers the file system(ext4) from an unclean shutdown from the issue above. What you think should happen instead: 1. The computer should have suspended itself to ram. 2. The USB ports should have continued to function in this low power mode. Additional Information: I have tried playing around with 'Hibernate' rather than 'Suspend' too and hibernate works as it suspends to disk. However, hibernate is not an option in my Xubuntu. Although I rather use suspend to ram anyway as it is more useful. During playing around to see what works and what does not. I have suspended my computer with systemctl hybrid-sleep and the computer resumes only because in this dual mode the 'hibernate' portion from 'hybrid-sleep' works. Trying to find out the issue simply by dmesg here is what I see for anything related to suspending: " [ 103.436332] Suspending console(s) (use no_console_suspend to debug) [ 103.436554] r8712u 1-4:1.0 wlx9444529e5e58: Suspending... [ 103.436557] r8712u 1-4:1.0 wlx9444529e5e58: Unable to suspend [ 103.438080] i8042 aux 00:07: System wakeup disabled by ACPI [ 103.438202] parport_pc 00:06: disabled [ 103.438278] serial 00:05: disabled [ 103.438351] serial 00:04: disabled [ 103.438355] serial 00:04: System wakeup disabled by ACPI [ 103.714993] PM: freeze of devices complete after 278.645 msecs [ 103.715503] PM: late freeze of devices complete after 0.504 msecs [ 103.716138] PM: noirq freeze of devices complete after 0.634 msecs [ 103.716139] Disabling non-boot CPUs ... [ 103.716311] PM: Creating hibernation image: [ 103.720015] PM: Need to copy 191958 pages [ 103.720015] PM: Normal pages needed: 191958 + 1024, available pages: 331921 [ 103.720015] PM: noirq restore of devices complete after 0.771 msecs [ 103.720015] PM: early restore of devices complete after 0.198 msecs [ 103.795754] rtc_cmos 00:01: System wakeup disabled by ACPI [ 103.796182] serial 00:04: activated [ 103.796569] serial 00:05: activated [ 103.797124] parport_pc 00:06: activated [ 103.828783] usb usb3: root hub lost power or was reset [ 103.832821] usb usb2: root hub lost power or was reset [ 103.832874] usb usb1: root hub lost power or was reset [ 103.834363] sd 5:0:0:0: [sda] Starting disk [ 103.834401] sd 5:0:1:0: [sdb] Starting disk " Here is the longer version of dmesg: :~$ dmesg [1.268307] rtc_cmos 00:01: setting system clock to 2015-10-25 02:28:22 UTC (1445740102) [1.268487] powernow_k8: fid 0xe (2200 MHz), vid 0x6 [1.268489] powernow_k8: fid 0xc (2000 MHz), vid 0x8 [1.268490] powernow_k8: fid 0xa (1800 MHz), vid 0xa [1.268492] powernow_k8: fid 0x2 (1000 MHz), vid 0x12 [1.268514] powernow_k8: Found 1 AMD Athlon(tm) 64 Processor 3200+ (1 cpu cores) (version 2.20.00) [1.268524] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found [1.268525] EDD information not available. [1.268611] PM: Hibernation image not present or could not be loaded. [1.269775] Freeing unused kernel memory: 1460K (81d37000 - 81ea4000) [1.269780] Write protecting the kernel read-only data: 12288k [1.269981] Freeing unused kernel memory: 36K (8800017f7000 - 88000180) [1.270258] Freeing unused kernel memory: 296K (880001bb6000 - 880001c0) [1.290019] random: udevadm urandom read with 2 bits of entropy available [1.366840] Floppy drive(s): fd0 is 1.44M [1.371249] sata_sil :00:11.0: version 2.4 [1.379203] scsi host0: sata_sil [1.384537] FDC 0 is a post-1991 82077 [1.387671] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [1.387678] 8139cp :02:05.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [1.388222] scsi host1: sata_sil [1.388306] ata1: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f080 irq 23 [1.388310] ata2: SATA max UDMA/100 mmio m512@0xfe02f000 tf 0xfe02f0c0 irq 23 [1.394614] 8139too: 8139too Fast Ethernet driver 0.9.28 [1.395883] 8139too :02:05.0
[Kernel-packages] [Bug 1511162] Re: Trackpad not working - Ubuntu 15.04
Jay Modi, thank you for reporting this and helping make Ubuntu better. As per http://www.dell.com/support/home/us/en/19/product- support/product/inspiron-15-5547-laptop/drivers/advanced an update to your computer's buggy and outdated BIOS is available (A08). If you update to this following https://help.ubuntu.com/community/BIOSUpdate does it address the issue? If it doesn't, could you please both specify what happened, and provide the output of the following terminal command: sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette . Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful. Also, you don't have to create a new bug report. Once the BIOS is updated, if the problem is still reproducible, and the information above is provided, then please mark this report Status Confirmed. Otherwise, please mark this as Invalid. Thank you for your understanding. ** Tags added: bios-outdated-a08 ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1511162 Title: Trackpad not working - Ubuntu 15.04 Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 15.04 Release: 15.04 What you expected to happen - normal working of trackpad What happened instead - not working. But external mouse is working. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-28-generic 3.19.0-28.30 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jay1940 F pulseaudio /dev/snd/controlC0: jay1940 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 20:20:37 2015 HibernationDevice: RESUME=UUID=1cfd2b1c-e309-4c8c-b4c0-dd31fc5801aa InstallationDate: Installed on 2014-12-23 (309 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 5547 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-28-generic.efi.signed root=UUID=1f4ae70a-f1de-4f96-8384-cd6d039e47a2 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-28-generic N/A linux-backports-modules-3.19.0-28-generic N/A linux-firmware 1.143.4 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-06-24 (126 days ago) dmi.bios.date: 01/23/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0598GM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A07 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd01/23/2015:svnDellInc.:pnInspiron5547:pvrA07:rvnDellInc.:rn0598GM:rvrA00:cvnDellInc.:ct8:cvrA07: dmi.product.name: Inspiron 5547 dmi.product.version: A07 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511162/+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 1511131] Re: Bluetooth LED always lightning
David Baumann, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: latest-bios-a15 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1511131 Title: Bluetooth LED always lightning Status in linux package in Ubuntu: Incomplete Bug description: So no matter if I enable or disable bluetooth on my laptop, even if I rfkill it, the bluetooth led is turned on all the time. If you need any more information, please just ask. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: david 2403 F pulseaudio /dev/snd/pcmC0D0p: david 2403 F...m pulseaudio /dev/snd/controlC0: david 2403 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 28 22:47:55 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-06-13 (502 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: Dell Inc. Precision M4800 ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/xubuntu--vg-root ro quiet RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UpgradeStatus: Upgraded to wily on 2015-07-20 (100 days ago) dmi.bios.date: 09/29/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A15 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA15:bd09/29/2015:svnDellInc.:pnPrecisionM4800:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511131/+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 1121699] Re: aufs CONFIG_AUFS_EXPORT build option should be enabled
Seems the flag is disabled again in linux-4.2.0-16-generic. I've upgraded from Ubuntu 15.04 to Ubuntu 15.10 and my exporting of AuFS is broken now. ** Tags added: wily -- 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/1121699 Title: aufs CONFIG_AUFS_EXPORT build option should be enabled Status in linux package in Ubuntu: Fix Released Status in linux source package in Raring: Fix Released Bug description: This is needed to export aufs filesystems via nfs. This was set in a previous version (in Debian - http://bugs.debian.org /cgi-bin/bugreport.cgi?bug=490079), and released in Ubuntu build for aufs 0+20080719-4 (https://launchpad.net/ubuntu/+source/aufs/0+20080719-4), so this could perhaps be considered a regression (although to be fair aufs and its packaging has undergone significant rewriting since then). Regardless considering aufs is a popular method of supporting large storage systems (among other things) and nfs is a popular method of exporting large storage systems, it would be great if this could be enabled in a future build, unless there is some known contraindication. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1121699/+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 1499089] Re: Please enable kconfig X86_LEGACY_VM86 for i386
Hi there, I believe this tiny patch also needs to be applied. http://git.kernel.org/cgit/linux/kernel/git/tip/tip.git/commit/?id=2459ee8651dc5ab72790c2ffa99af288c7641b64 -- 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/1499089 Title: Please enable kconfig X86_LEGACY_VM86 for i386 Status in linux package in Ubuntu: Fix Released Status in linux source package in Wily: Fix Released Bug description: In order for dosemu to reach maximum performance (a > 10x speedup) please enable kconfig X86_LEGACY_VM86 in the kernel. As of this commit http://www.spinics.net/lists/linux-tip-commits/msg30360.html the overzealous kconfig message that seemed to suggest that the vm86() syscall was a security hazard in itself has been revised to reflect reality. Also please note that even if this kconfig option is enabled the runtime default is still off as vm86 is only actually enabled if the sysctl vm.mmap_min_addr is set to 0. That said, allowing vm.mmap_min_addr=0 is a known security risk and enabling the vm86() syscall to operate additionally would add little value to any potential attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1499089/+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 1511045] Re: Gpu hang unexpected
as, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel- ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue. If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description: kernel-fixed-upstream kernel-fixed-upstream-X.Y-rcZ Where X, Y, and Z are numbers corresponding to the kernel version. If the mainline kernel does not fix the issue, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-X.Y-rcZ Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream. Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- 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/1511045 Title: Gpu hang unexpected Status in linux package in Ubuntu: Incomplete Bug description: $ dmesg | grep drm [2.457690] [drm] Initialized drm 1.1.0 20060810 [2.799030] [drm] Memory usable by graphics device = 256M [2.799059] fb: switching to inteldrmfb from VESA VGA [2.799497] [drm] Replacing VGA console driver [2.801977] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [2.801987] [drm] Driver supports precise vblank timestamp query. [2.833563] [drm] initialized overlay support [2.833703] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on minor 0 [2.935517] fbcon: inteldrmfb (fb0) is primary device [2.936113] i915 :00:02.0: fb0: inteldrmfb frame buffer device [ 2762.004076] [drm] stuck on render ring [ 2762.009803] [drm] GPU HANG: ecode 3:0:0x7a7fffc1, in Xorg [1162], reason: Ring hung, action: reset [ 2762.009816] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 2762.009821] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 2762.009827] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 2762.009832] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 2762.009837] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 2762.042393] drm/i915: Resetting chip after gpu hang ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic i686 ApportVersion: 2.19.1-0ubuntu4 Architecture: i386 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: MATE Date: Wed Oct 28 18:11:02 2015 HibernationDevice: RESUME=/dev/mapper/192--168--0--102--vg-swap_1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-16-generic root=/dev/mapper/192--168--0--102--vg-root ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Fille
[Kernel-packages] [Bug 1218691] Re: Possible missing firmware /lib/firmware/radeon/*.bin
@Martin Suc - You actually have a different (albeit related) bug. This bug is about the radeon module. Your bug is abou the amdgpu module, which is the driver to support the Radeon R9 285 "Tonga" and all future GPUs, including Carrizo APUs and the to-be-supported Fiji/Fury GPUs. This AMDGPU driver will live alongside the current "Radeon" DRM driver as the kernel components to AMD's open-source Linux driver offering. The amdgpu module and it's associated firmware is optional for the GPUs listed in comment #11. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1218691 Title: Possible missing firmware /lib/firmware/radeon/*.bin Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Saucy: Fix Released Status in Debian: Fix Released Bug description: When updating the kernel today to 3.11.0-4-generic I saw the same warning messages I saw when I upgraded to 3.11.0-3-generic update-initramfs: Generating /boot/initrd.img-3.11.0-4-generic W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon Further digging found bug 1183777 As mentioned in that bug, I did contact the named person: "Hi, I'm still seeing the errors for KAVERI firmwares being missing in the latest kernel : phillw@piglet:~$ uname -a Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux As the 1st Beta is creeping up fast, do you need this raising as a new bug? Regards, Phill." The reply is: "As far as I can tell, the KAVERI firmware (and hardware) is not publicly available yet, so that's not a bug with the linux-firmware package. If you want to file a new bug about the warning messages, please file it against the linux (kernel) package. Until the firmware is available, I'm not really sure what the fix for that would be, other than removing/commenting out the relevant Kaveri lines in the radeon kernel code." Please find attached bug report as requested. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phillw 1965 F lxpanel CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Aug 30 02:37:54 2013 HibernationDevice: RESUME=UUID=d98ac0ad-5c96-4382-8195-23b44e056358 InstallationDate: Installed on 2013-06-29 (61 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130628) MachineType: Packard Bell EasyNote LJ71 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-3-generic root=UUID=69c7aa0f-ccd0-4ac4-8930-e6f0efda9e6b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2009 dmi.bios.vendor: Packard Bell dmi.bios.version: V1.03 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: EasyNote LJ71 dmi.board.vendor: Packard Bell dmi.board.version: V1.03 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell dmi.chassis.version: V1.03 dmi.modalias: dmi:bvnPackardBell:bvrV1.03:bd09/22/2009:svnPackardBell:pnEasyNoteLJ71:pvrV1.03:rvnPackardBell:rnEasyNoteLJ71:rvrV1.03:cvnPackardBell:ct10:cvrV1.03: dmi.product.name: EasyNote LJ71 dmi.product.version: V1.03 dmi.sys.vendor: Packard Bell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1218691/+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 1511844] Re: [Acer Aspire ES1-711] System freezes occasionally
I only have this laptop for a few months, so never had Ubuntu 14 installed on 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/1511844 Title: [Acer Aspire ES1-711] System freezes occasionally Status in linux package in Ubuntu: Triaged Bug description: Occasionally my system freezes totally in 15.04 and 15.10. Switching to Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not work. Some days my system will run for many hours without any problem, and on other days I experience 2 or 3 freezes in an hour time. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: freek 2223 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 30 21:11:26 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb InstallationDate: Installed on 2015-07-13 (108 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire ES1-711 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (2 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-711 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511844/+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 1509723] Re: [Acer Aspire ES1-311] Ubuntu freezes occasionally
** Summary changed: - Ubuntu freezes occasionally + [Acer Aspire ES1-311] Ubuntu freezes occasionally -- 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/1509723 Title: [Acer Aspire ES1-311] Ubuntu freezes occasionally Status in linux package in Ubuntu: Triaged Bug description: I am running Ubuntu 15.10 and my notebook freezes occasionally. I had the same issue with Ubuntu 15.04, but I thought that 15.10 might change it. I am running Ubuntu on an Acer Aspire ES1-311 (P1D5). I have no clue what causes this, my system just freezes and I can't do anything anymore. ctrl+alt+f1 doesn't work as well as alt+print+REISUB doesn't work either. It's just frozen. I have to power down manually. Last time I was programming only with a gnome-terminal and atom (editor) opened. I checked some log files but I couldn't find anything suspicious. Any ideas? ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 [modified: boot/vmlinuz-4.2.0-16-generic] ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1490 F pulseaudio CurrentDesktop: Unity Date: Sat Oct 24 23:38:29 2015 HibernationDevice: RESUME=UUID=e81f37fd-8750-4e88-876e-7118ed4fa77e InstallationDate: Installed on 2015-10-24 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f2:b469 Chicony Electronics Co., Ltd Bus 001 Device 005: ID 04ca:300b Lite-On Technology Corp. Atheros AR3012 Bluetooth Bus 001 Device 002: ID 0461:4d2f Primax Electronics, Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire ES1-311 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=a0b570c6-9883-4099-9505-440eeb0d3551 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.10 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Aspire ES1-311 dmi.board.vendor: Acer dmi.board.version: V1.10 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.10 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.10:bd10/24/2014:svnAcer:pnAspireES1-311:pvrV1.10:rvnAcer:rnAspireES1-311:rvrV1.10:cvnAcer:ct10:cvrV1.10: dmi.product.name: Aspire ES1-311 dmi.product.version: V1.10 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723/+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 1511844] Re: System freezes occasionally
Freek, did this problem not occur in a release prior to 15.04? ** Description changed: - Occasionally my system freezes totally. When this happens, the screen - totally freezes, no mouse movements anymore. Switching to Console via - Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not work. I have waited - at least 30 min, but the system doesn't seem to recover. + Occasionally my system freezes totally in 15.04 and 15.10. Switching to + Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not work. Some days my system will run for many hours without any problem, and on - other days I experience 2 or 3 freezes in an hour time. So far I have - not noticed any similarities between the moments of freezing in regard - to programs running etc. - - I filled in this report after reading - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723 which - seemed to describe the same thing to me, on a same brand laptop. The - freezes happened both on Ubuntu 15.04 and 15.10 + other days I experience 2 or 3 freezes in an hour time. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: freek 2223 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: freek 2223 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 30 21:11:26 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb InstallationDate: Installed on 2015-07-13 (108 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire ES1-711 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.2.0-16-generic N/A - linux-backports-modules-4.2.0-16-generic N/A - linux-firmware1.149 + linux-restricted-modules-4.2.0-16-generic N/A + linux-backports-modules-4.2.0-16-generic N/A + linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (2 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-711 dmi.product.version: V1.05 dmi.sys.vendor: Acer ** Changed in: linux (Ubuntu) Importance: Medium => High ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Summary changed: - System freezes occasionally + [Acer Aspire ES1-711] System freezes occasionally -- 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/1511844 Title: [Acer Aspire ES1-711] System freezes occasionally Status in linux package in Ubuntu: Triaged Bug description: Occasionally my system freezes totally in 15.04 and 15.10. Switching to Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not work. Some days my system will run for many hours without any problem, and on other days I experience 2 or 3 freezes in an hour time. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: freek 2223 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 30 21:11:26 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb InstallationDate: Installed on 2015-07-13 (108 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire ES1-711 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/v
[Kernel-packages] [Bug 1509803] Re: Bluetooth Will not work
Power down the laptop, remove the wifi card and check the connector for dirt or debris. Reinstall wifi card and boot If that doesn't help, you might need a new card as this appears to be a hardware issue -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work Status in linux-lts-vivid package in Ubuntu: New Bug description: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.19.0-32-generic
[Kernel-packages] [Bug 1218691] Re: Possible missing firmware /lib/firmware/radeon/KAVERI
same bug in ubuntu 15.10 W: Possible missing firmware /lib/firmware/radeon/boniare_mc.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/mullins_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kabini_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kaveri_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/hawaii_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/bonaire_sdma1.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/mullins_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/hawaii_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kaveri_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kabini_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/bonaire_uvd.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/mullins_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/hawaii_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kaveri_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/kabini_vce.bin for module amdgpu W: Possible missing firmware /lib/firmware/radeon/bonaire_vce.bin for module amdgpu reproducible by run update-initramfs -u -k all ** Tags added: wily ** Summary changed: - Possible missing firmware /lib/firmware/radeon/KAVERI + Possible missing firmware /lib/firmware/radeon/*.bin -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1218691 Title: Possible missing firmware /lib/firmware/radeon/*.bin Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Saucy: Fix Released Status in Debian: Fix Released Bug description: When updating the kernel today to 3.11.0-4-generic I saw the same warning messages I saw when I upgraded to 3.11.0-3-generic update-initramfs: Generating /boot/initrd.img-3.11.0-4-generic W: Possible missing firmware /lib/firmware/radeon/KAVERI_sdma.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_rlc.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_mec.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_ce.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_me.bin for module radeon W: Possible missing firmware /lib/firmware/radeon/KAVERI_pfp.bin for module radeon Further digging found bug 1183777 As mentioned in that bug, I did contact the named person: "Hi, I'm still seeing the errors for KAVERI firmwares being missing in the latest kernel : phillw@piglet:~$ uname -a Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux As the 1st Beta is creeping up fast, do you need this raising as a new bug? Regards, Phill." The reply is: "As far as I can tell, the KAVERI firmware (and hardware) is not publicly available yet, so that's not a bug with the linux-firmware package. If you want to file a new bug about the warning messages, please file it against the linux (kernel) package. Until the firmware is available, I'm not really sure what the fix for that would be, other than removing/commenting out the relevant Kaveri lines in the radeon kernel code." Please find attached bug report as requested. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-4-generic 3.11.0-4.9 ProcVersionSignature: Ubuntu 3.11.0-3.8-generic 3.11.0-rc6 Uname: Linux 3.11.0-3-generic x86_64 ApportVersion: 2.12.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phillw 1965 F lxpanel CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Fri Aug 30 02:37:54 2013 HibernationDevice: RESUME=UUID=d98ac0ad-5c96-4382-8195-23b44e056358 InstallationDate: Installed on 2013-06-29 (61 days ago) InstallationMedia: Lubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130628) MachineType: Packard Bell EasyNote LJ71 MarkForUpload: True ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-3-generic root=UUID=69c7aa0f-ccd0-4ac4-8930-e6f0efda9e6b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.11.0-3-generic N/A linux-backports-modules-3.11.0-3-generic N/A linux-firmware1.113 SourcePackage: linux StagingDrivers: zram UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2009 dmi.bios.vendor: Packard
[Kernel-packages] [Bug 1512085] [NEW] package linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 2 terug
Public bug reported: Steps to reproduce: Start the computer after a sudo apt-get update; sudo apt-get upgrade What should have happend: the new kernel should have loaded and the computer should work normally What really happened: Kernel Panic When I start the computer I get a Kernel Panic - Not Syncing: VFS: Unable to mount root fs on unknown-block(0,0). When I reboot into the previous kernel I am able to create this error report. There needs to be way of checking or ensuring that the new kernel is properly installed before rebooting. I don't want to even imagine this kernel panic happening on one of my remote machines. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Thu Oct 22 10:26:21 2015 DpkgTerminalLog: Log started: 2015-10-22 10:23:46 ErrorMessage: subproces installed post-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2015-03-29 (216 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.8 SourcePackage: linux-lts-utopic Title: package linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-lts-utopic (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1512085 Title: package linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 2 terug Status in linux-lts-utopic package in Ubuntu: New Bug description: Steps to reproduce: Start the computer after a sudo apt-get update; sudo apt-get upgrade What should have happend: the new kernel should have loaded and the computer should work normally What really happened: Kernel Panic When I start the computer I get a Kernel Panic - Not Syncing: VFS: Unable to mount root fs on unknown-block(0,0). When I reboot into the previous kernel I am able to create this error report. There needs to be way of checking or ensuring that the new kernel is properly installed before rebooting. I don't want to even imagine this kernel panic happening on one of my remote machines. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-50.67~14.04.1-generic 3.16.7-ckt16 Uname: Linux 3.16.0-50-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.15 Architecture: amd64 Date: Thu Oct 22 10:26:21 2015 DpkgTerminalLog: Log started: 2015-10-22 10:23:46 ErrorMessage: subproces installed post-installation script gaf een foutwaarde 2 terug InstallationDate: Installed on 2015-03-29 (216 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.8 SourcePackage: linux-lts-utopic Title: package linux-image-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: subproces installed post-installation script gaf een foutwaarde 2 terug UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1512085/+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 1505592] Re: 3.19.0.30 kernel in hyper-v cause hv_netvsc problem
I am also facing the problem 3.19.0.30 is failing on me hyper-v with the same version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1505592 Title: 3.19.0.30 kernel in hyper-v cause hv_netvsc problem Status in linux-lts-vivid package in Ubuntu: New Bug description: Hi, i have a problem, same in https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1491957 I think it's not fixed in 3.19 branch. Oct 11 16:18:29 web01 kernel: [797134.247603] hv_netvsc vmbus_0_14 eth1: unable to send receive completion pkt (tid 1990)...retrying 1 Oct 11 16:18:29 web01 kernel: [797134.247767] hv_netvsc vmbus_0_14 eth1: unable to send receive completion pkt (tid 1990)...retrying 2 Oct 11 16:18:29 web01 kernel: [797134.247903] hv_netvsc vmbus_0_14 eth1: unable to send receive completion pkt (tid 1990)...retrying 3 Oct 11 16:18:29 web01 kernel: [797134.248037] hv_netvsc vmbus_0_14 eth1: unable to send receive completion pkt (tid 1990)...retrying 4 Oct 11 16:18:29 web01 kernel: [797134.248072] hv_netvsc vmbus_0_14 eth1: unable to send receive completion pkt (tid 1990)...give up retrying To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-vivid/+bug/1505592/+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 1509803] Re: Bluetooth Will not work
sudo hciconfig hci0 piscan Can't set scan mode on hci0: Network is down (100) hcitool scan Device is not available: No such device Now here is the deal. Sometimes the mouse connects, and it works for a few hours, and then quits, and won't connect again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-vivid in Ubuntu. https://bugs.launchpad.net/bugs/1509803 Title: Bluetooth Will not work Status in linux-lts-vivid package in Ubuntu: New Bug description: I have an issue with my Bluetooth, in a Lenovo 50-70. It will not turn on, and if I try to turn it on, it gives the messsage that no adapters found. I tied converting the .hex windows driver t .hcd, but that didn't help. Below is my info: 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub dmesg | grep -i blue [ 36.077001] Bluetooth: Core ver 2.20 [ 36.077016] Bluetooth: HCI device and connection manager initialized [ 36.077018] Bluetooth: HCI socket layer initialized [ 36.077020] Bluetooth: L2CAP socket layer initialized [ 36.077024] Bluetooth: SCO socket layer initialized [ 36.165964] Bluetooth: RFCOMM TTY layer initialized [ 36.165973] Bluetooth: RFCOMM socket layer initialized [ 36.165978] Bluetooth: RFCOMM ver 1.11 [ 36.192237] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 36.192239] Bluetooth: BNEP filters: protocol multicast [ 36.192242] Bluetooth: BNEP socket layer initialized ls -l /lib/firmware/brcm total 7716 -rw-rw-r-- 1 root root 28263 Oct 23 22:38 BCM43142A0-105b:e065.hcd -rw-r--r-- 1 root root 269595 Nov 24 2014 bcm4329-fullmac-4.bin -rw-r--r-- 1 root root 96224 Dec 1 2014 bcm43xx-0.fw -rw-r--r-- 1 root root 180 Dec 1 2014 bcm43xx_hdr-0.fw -rw-r--r-- 1 root root 397312 Dec 1 2014 brcmfmac43143.bin -rwxr-xr-x 1 root root 385067 Sep 24 16:20 brcmfmac43143-sdio.bin -rw-r--r-- 1 root root 348160 Nov 24 2014 brcmfmac43236b.bin -rw-r--r-- 1 root root 455745 Dec 1 2014 brcmfmac43241b0-sdio.bin -rw-r--r-- 1 root root 403855 Dec 1 2014 brcmfmac43241b4-sdio.bin -rw-r--r-- 1 root root 479232 Sep 24 16:20 brcmfmac43242a.bin -rw-r--r-- 1 root root 253748 Dec 1 2014 brcmfmac4329-sdio.bin -rw-r--r-- 1 root root 222126 Dec 1 2014 brcmfmac4330-sdio.bin -rw-r--r-- 1 root root 451566 Dec 1 2014 brcmfmac4334-sdio.bin -rw-r--r-- 1 root root 569291 Dec 1 2014 brcmfmac4335-sdio.bin -rw-r--r-- 1 root root 219557 Dec 1 2014 brcmfmac43362-sdio.bin -rw-r--r-- 1 root root 493599 Sep 24 16:20 brcmfmac4339-sdio.bin -rw-r--r-- 1 root root 507752 Sep 24 16:13 brcmfmac4354-sdio.bin -rw-r--r-- 1 root root 557056 Sep 24 16:20 brcmfmac43569.bin -rw-r--r-- 1 root root 550333 Sep 24 16:20 brcmfmac43570-pcie.bin -rw-r--r-- 1 root root 588940 Sep 24 16:20 brcmfmac43602-pcie.ap.bin -rw-r--r-- 1 root root 590544 Sep 24 16:20 brcmfmac43602-pcie.bin lspci -knn | grep Net -A2; lsusb 02:00.0 Network controller [0280]: Broadcom Corporation BCM43142 802.11b/g/n [14e4:4365] (rev 01) Subsystem: Lenovo Device [17aa:0621] Kernel driver in use: wl Bus 003 Device 002: ID 8087:8000 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 105b:e065 Bus 001 Device 004: ID 5986:055d Acer, Inc Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub After loading the .hcd file I get this dmesg | grep -i blue [ 24.144917] Bluetooth: Core ver 2.20 [ 24.144932] Bluetooth: HCI device and connection manager initialized [ 24.144935] Bluetooth: HCI socket layer initialized [ 24.144937] Bluetooth: L2CAP socket layer initialized [ 24.144941] Bluetooth: SCO socket layer initialized [ 24.191155] Bluetooth: RFCOMM TTY layer initialized [ 24.191162] Bluetooth: RFCOMM socket layer initialized [ 24.191167] Bluetooth: RFCOMM ver 1.11 [ 24.215839] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 24.215842] Bluetooth: BNEP filters: protocol multicast [ 24.215845] Bluetooth: BNEP socket layer initialized I have tried about everything I could find out there, and nothing helped. ProblemType: Bug DistroRelease: Ub
[Kernel-packages] [Bug 1511844] Re: System freezes occasionally
Just tried 4.3.0-994 from Oct 29 (later dates don't seem to have 64 bits image). 20 minutes later everything froze again. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1511844 Title: System freezes occasionally Status in linux package in Ubuntu: Confirmed Bug description: Occasionally my system freezes totally. When this happens, the screen totally freezes, no mouse movements anymore. Switching to Console via Ctrl-Alt-F1 or rebooting via Ctrl-Alt-Del does not work. I have waited at least 30 min, but the system doesn't seem to recover. Some days my system will run for many hours without any problem, and on other days I experience 2 or 3 freezes in an hour time. So far I have not noticed any similarities between the moments of freezing in regard to programs running etc. I filled in this report after reading https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509723 which seemed to describe the same thing to me, on a same brand laptop. The freezes happened both on Ubuntu 15.04 and 15.10 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-16-generic 4.2.0-16.19 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: freek 2223 F pulseaudio CurrentDesktop: Unity Date: Fri Oct 30 21:11:26 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c4065390-4392-460d-b828-37b12c4605cb InstallationDate: Installed on 2015-07-13 (108 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Acer Aspire ES1-711 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic.efi.signed root=UUID=772134c4-7cb5-40d6-b0c7-a6bc4a98efe5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-16-generic N/A linux-backports-modules-4.2.0-16-generic N/A linux-firmware1.149 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2015-10-27 (2 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_BM dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd11/07/2014:svnAcer:pnAspireES1-711:pvrV1.05:rvnAcer:rnEA70_BM:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire ES1-711 dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1511844/+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
