[Kernel-packages] [Bug 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
[Expired for multipath-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: multipath-tools (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/1655735 Title: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Status in linux package in Ubuntu: Expired Status in lvm2 package in Ubuntu: Expired Status in multipath-tools package in Ubuntu: Expired Bug description: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu- image/20170111_171929_431b1@/log.gz Scroll to the bottom and you see this: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met /dev/mapper/control: mknod failed: Operation not permitted Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met Don't be misled by the gadget.yamls which name different architectures. ubuntu-image should be able to build a disk image for any architecture on any architecture. What this test does is build the image, then run kpartx to map the partitions in the image, and then mount the partitions. It doesn't do anything other than ensure that the partitions can be mounted, and this is where it's failing. This test succeeds on amd64, i386, and ppc64el. It's never passed on s390x so that's not a regression. It *used* to pass on armhf even on Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the regression. I will bugtask this to libdevmapper and kpartx since it's possibly a bug in one of those packages (though I still suspect the kernel). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-11-generic 4.9.0-11.12 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barry 5414 F pulseaudio /dev/snd/controlC0: barry 5414 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 11 13:10:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864 InstallationDate: Installed on 2016-01-22 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro RelatedPackageVersions: linux-restricted-modules-4.9.0-11-generic N/A linux-backports-modules-4.9.0-11-generic N/A linux-firmware1.162 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-UD5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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 Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-UD5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
[Expired for lvm2 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lvm2 (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/1655735 Title: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Status in linux package in Ubuntu: Expired Status in lvm2 package in Ubuntu: Expired Status in multipath-tools package in Ubuntu: Expired Bug description: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu- image/20170111_171929_431b1@/log.gz Scroll to the bottom and you see this: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met /dev/mapper/control: mknod failed: Operation not permitted Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met Don't be misled by the gadget.yamls which name different architectures. ubuntu-image should be able to build a disk image for any architecture on any architecture. What this test does is build the image, then run kpartx to map the partitions in the image, and then mount the partitions. It doesn't do anything other than ensure that the partitions can be mounted, and this is where it's failing. This test succeeds on amd64, i386, and ppc64el. It's never passed on s390x so that's not a regression. It *used* to pass on armhf even on Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the regression. I will bugtask this to libdevmapper and kpartx since it's possibly a bug in one of those packages (though I still suspect the kernel). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-11-generic 4.9.0-11.12 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barry 5414 F pulseaudio /dev/snd/controlC0: barry 5414 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 11 13:10:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864 InstallationDate: Installed on 2016-01-22 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro RelatedPackageVersions: linux-restricted-modules-4.9.0-11-generic N/A linux-backports-modules-4.9.0-11-generic N/A linux-firmware1.162 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-UD5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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 Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-UD5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1656638] Re: Bluetooth stops working after sleep
[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/1656638 Title: Bluetooth stops working after sleep Status in linux package in Ubuntu: Expired Bug description: I am using Ububtu 16.04 LTS, had this problem before and still happens. After restore computer from suspend mode, the bluethooth stops working/ is disabled. It doesn't start even if i toggle the OFF button. Also the icon on the menu bar is also gone. I've tried several commands to restore/reload module's firmware but nothing seems to work. It looks like a bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-57-generic 4.4.0-57.78 ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35 Uname: Linux 4.4.0-57-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: rds1893 F...m pulseaudio /dev/snd/controlC0: rds1893 F pulseaudio CurrentDesktop: Unity Date: Sun Jan 15 11:51:12 2017 HibernationDevice: RESUME=UUID=e7f67138-2dc6-4a9e-a873-11bf33034882 InstallationDate: Installed on 2016-11-05 (70 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 350V5C/351V5C/3540VC/3440VC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-generic root=UUID=0d719643-4a34-4040-9856-fcb903c61c29 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-57-generic N/A linux-backports-modules-4.4.0-57-generic N/A linux-firmware1.157.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/04/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P09ABE dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP350V5C-S0CDE dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: BOARD REVISION 00 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP09ABE:bd07/04/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn350V5C/351V5C/3540VC/3440VC:pvrP09ABE.012.CP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350V5C-S0CDE:rvrBOARDREVISION00:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 350V5C/351V5C/3540VC/3440VC dmi.product.version: P09ABE.012.CP dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656638/+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 1656819] Re: [Acer Aspire ES1-711] System freezes occasionally
[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/1656819 Title: [Acer Aspire ES1-711] System freezes occasionally Status in linux package in Ubuntu: Expired Bug description: I fill that bugreport because I should create a new one, instead of adding information to bug #1511844 Ill collect Information as if the bug is finished and write a notice to bug 1511844. If you need some more information please let me know. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uwe1695 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18 HibernationDevice: RESUME=UUID=8b1bf70d-3649-4e59-9152-0765cb1eb842 InstallationDate: Installed on 2016-09-28 (109 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160628 MachineType: Acer Aspire ES1-711 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic root=UUID=a89c70a1-3925-415e-b0f0-8d64d8015fc6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 RelatedPackageVersions: linux-restricted-modules-4.4.0-21-generic N/A linux-backports-modules-4.4.0-21-generic N/A linux-firmware1.157.6 Tags: sarah Uname: Linux 4.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True 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/1656819/+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 1656592] Re: Samsung Notebook backlight doesn't change levels
[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/1656592 Title: Samsung Notebook backlight doesn't change levels Status in linux package in Ubuntu: Expired Bug description: Samsung Notebook's (version P05ADG) backlight doesn't change levels, even using function keys or system apps. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-47-generic 4.4.0-47.68 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: olivia 3486 F pulseaudio CurrentDesktop: Unity Date: Sat Jan 14 19:05:14 2017 HibernationDevice: RESUME=UUID=037b9eb5-d8cf-4b0d-bd1a-baaafd5befbf InstallationDate: Installed on 2016-11-15 (60 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: SAMSUNG ELECTRONICS CO., LTD. 670Z5E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=3e21c5be-6824-4131-8250-caeb22b8e3bb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-47-generic N/A linux-backports-modules-4.4.0-47-generic N/A linux-firmware1.157.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P05ADG.010.140421.SH dmi.board.asset.tag: No Asset Tag dmi.board.name: NP670Z5E-XD1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SEC_SW_REVISION_1234567890ABCD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP05ADG.010.140421.SH:bd04/21/2014:svnSAMSUNGELECTRONICSCO.,LTD.:pn670Z5E:pvrP05ADG:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP670Z5E-XD1BR:rvrSEC_SW_REVISION_1234567890ABCD:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.name: 670Z5E dmi.product.version: P05ADG dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656592/+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 1655735] Re: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version).
[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/1655735 Title: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). Status in linux package in Ubuntu: Expired Status in lvm2 package in Ubuntu: Expired Status in multipath-tools package in Ubuntu: Expired Bug description: There is a new Zesty regression on armhf, related to the autopkgtest for ubuntu-image. Here's a log of a recent run: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/u/ubuntu- image/20170111_171929_431b1@/log.gz Scroll to the bottom and you see this: Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met /dev/mapper/control: mknod failed: Operation not permitted Failure to communicate with kernel device-mapper driver. Check that device-mapper is available in the kernel. Incompatible libdevmapper 1.02.136 (2016-11-05) and kernel driver (unknown version). device mapper prerequisites not met Don't be misled by the gadget.yamls which name different architectures. ubuntu-image should be able to build a disk image for any architecture on any architecture. What this test does is build the image, then run kpartx to map the partitions in the image, and then mount the partitions. It doesn't do anything other than ensure that the partitions can be mounted, and this is where it's failing. This test succeeds on amd64, i386, and ppc64el. It's never passed on s390x so that's not a regression. It *used* to pass on armhf even on Zesty, but the recent upload of 0.13+17.10ubuntu2 displays the regression. I will bugtask this to libdevmapper and kpartx since it's possibly a bug in one of those packages (though I still suspect the kernel). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.9.0-11-generic 4.9.0-11.12 ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0 Uname: Linux 4.9.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: barry 5414 F pulseaudio /dev/snd/controlC0: barry 5414 F pulseaudio CurrentDesktop: Unity Date: Wed Jan 11 13:10:30 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8cc96f00-242f-42c6-bdb9-72db178f8864 InstallationDate: Installed on 2016-01-22 (355 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.9.0-11-generic root=UUID=d03718f1-9983-4b07-a942-1b42fe8352ec ro RelatedPackageVersions: linux-restricted-modules-4.9.0-11-generic N/A linux-backports-modules-4.9.0-11-generic N/A linux-firmware1.162 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z170X-UD5-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x 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 Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd07/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z170X-UD5 dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1655735/+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 1656627] Re: package linux-image-4.4.0-59-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128
[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/1656627 Title: package linux-image-4.4.0-59-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 Status in linux package in Ubuntu: Expired Bug description: hI, also I received this information "Fallo al descargar archivos de datos extra Los siguientes paquetes han solicitado descargas adicionales de datos después de la instalación del paquete, pero los datos no se han podido descargar o no se han podido procesar. ttf-mscorefonts-installer La descarga se intentará de nuevo más tarde, o puede reintentar la descarga ahora. Para ejecutar esta instrucción se necesita tener una conexión a Interne" Translation Failed to download extra data files The following packages have requested additional data downloads after the package was installed, but the data could not be downloaded or could not be processed. ttf-mscorefonts-installer The download will try again later, or you can retry the download now. To execute this instruction you need to have an Internet connection ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-lowlatency (not installed) ProcVersionSignature: Ubuntu 4.4.0-57.78-lowlatency 4.4.35 Uname: Linux 4.4.0-57-lowlatency i686 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ober 1505 F pulseaudio Date: Wed Jan 11 18:40:00 2017 ErrorMessage: subprocess new pre-installation script returned error exit status 128 HibernationDevice: RESUME=UUID=d7f14169-fb53-4dd9-8975-f5207dd1103d InstallationDate: Installed on 2017-01-08 (6 days ago) InstallationMedia: Ubuntu-Studio 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719) IwConfig: enp0s25 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. OptiPlex 780 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-57-lowlatency root=UUID=8ede0ffe-72ca-4c07-a0c9-d14946b5f344 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.6 RfKill: SourcePackage: linux Title: package linux-image-4.4.0-59-lowlatency (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0200DY dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd02/13/2010:svnDellInc.:pnOptiPlex780:pvr:rvnDellInc.:rn0200DY:rvrA01:cvnDellInc.:ct3:cvr: dmi.product.name: OptiPlex 780 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1656627/+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 1657015] Re: Suspend resumes in few seconds
[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/1657015 Title: Suspend resumes in few seconds Status in linux package in Ubuntu: Expired Bug description: Normally not the first time after boot but any subsequent attempts to suspend, causes the laptop to resume automatically. I tried several methods to stop this as I found from net. 1. Setting all values to 'disable' in result of 'cat /proc/acpi/wakeup'. I have by default LANC, EHC1, EHC2 and XHC enabled. Disabling them didn't affect this. 2. Updating bios to latest. 3. Changing /etc/systemd/logind.conf to have 'HandleLidSwitch=ignore' and 'HandleSuspendKey=ignore'. Either with changes in 1 or not. This used to work in 14.04 but not after updating. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-59-generic 4.4.0-59.80 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: hena 2048 F pulseaudio /dev/snd/controlC0: hena 2048 F pulseaudio CurrentDesktop: KDE Date: Tue Jan 17 09:07:09 2017 HibernationDevice: RESUME=UUID=d441ee3f-8ae3-4f22-9701-62672fff10f0 InstallationDate: Installed on 2014-02-27 (1054 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Hewlett-Packard HP ZBook 15 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic root=UUID=4391b8ab-e50c-4d99-8450-3ae28c770920 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-12-28 (19 days ago) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L70 Ver. 01.36 dmi.board.name: 1909 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 94.56 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.36:bd09/26/2016:svnHewlett-Packard:pnHPZBook15:pvrA3009DD10203:rvnHewlett-Packard:rn1909:rvrKBCVersion94.56:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ZBook 15 dmi.product.version: A3009DD10203 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657015/+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 256767] Re: USB devices work, but constant syslog errors "unable to enumerate USB device on port 5"
I have an issue with the system being able to see a USB drive. I know the port works because I can plug in a wireless mouse receiver to my USB port. Linux 4.4.0-66-generic #87-Ubuntu SMP Fri Mar 3 15:29:05 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux dmesg provides this log information when plugging in my external USB 2.0 HDD to my laptop: [ 5175.324194] usb 3-1: new full-speed USB device number 13 using ohci-pci [ 5186.192240] usb 3-1: new full-speed USB device number 14 using ohci-pci [ 5186.376232] usb 3-1: device descriptor read/64, error -62 [ 5186.664228] usb 3-1: device descriptor read/64, error -62 [ 5186.944228] usb 3-1: new full-speed USB device number 15 using ohci-pci [ 5187.128231] usb 3-1: device descriptor read/64, error -62 [ 5187.400241] usb 3-1: device descriptor read/64, error -62 [ 5187.680223] usb 3-1: new full-speed USB device number 16 using ohci-pci [ 5188.088164] usb 3-1: device not accepting address 16, error -62 [ 5188.264238] usb 3-1: new full-speed USB device number 17 using ohci-pci [ 5188.672216] usb 3-1: device not accepting address 17, error -62 [ 5188.672278] usb usb3-port1: unable to enumerate USB device [ 5228.528228] usb 3-1: new full-speed USB device number 18 using ohci-pci [ 5228.708117] usb 3-1: device descriptor read/64, error -62 [ 5228.992224] usb 3-1: device descriptor read/64, error -62 [ 5229.272238] usb 3-1: new full-speed USB device number 19 using ohci-pci [ 5229.452228] usb 3-1: device descriptor read/64, error -62 [ 5229.736224] usb 3-1: device descriptor read/64, error -62 [ 5230.016095] usb 3-1: new full-speed USB device number 20 using ohci-pci [ 5230.424246] usb 3-1: device not accepting address 20, error -62 [ 5230.600240] usb 3-1: new full-speed USB device number 21 using ohci-pci [ 5231.008246] usb 3-1: device not accepting address 21, error -62 [ 5231.008308] usb usb3-port1: unable to enumerate USB device -- 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/256767 Title: USB devices work, but constant syslog errors "unable to enumerate USB device on port 5" Status in linux package in Ubuntu: Won't Fix Bug description: 1) lsb_release -rd Description:Ubuntu intrepid (development branch) Release:8.10 2) apt-cache policy linux linux: Installed: (none) Candidate: 2.6.26.5.7 Version table: 2.6.26.5.7 0 500 http://us.archive.ubuntu.com intrepid/restricted Packages 3) I expect for the system to boot up without errors. 4) The system boots up and endlessly repeats: [...] [ 595.878673] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 596.410662] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 596.930656] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 597.442648] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 597.966870] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 598.474842] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 599.002838] hub 4-0:1.0: unable to enumerate USB device on port 5 [ 599.518833] hub 4-0:1.0: unable to enumerate USB device on port 5 [...] Updates This bug is still present in Ubuntu 9.04 and Ubuntu 9.10, for example in 2.6.31-14-generic-pae. It makes consoles almost impossible to use, and causes a lot of writes due to the constant updating of /var/log/syslog. A suggestion of the cause is at http://lkml.org/lkml/2008/10/24/209 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256767/+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 1674041] 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/1674041 Title: Keyboard backlight Status in linux package in Ubuntu: Confirmed Bug description: Key board backlight ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ganesh 2631 F pulseaudio /dev/snd/controlC0: ganesh 2631 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 19 07:59:13 2017 HibernationDevice: RESUME=UUID=eaee8605-adf5-4562-9b5a-c277f2681e6b InstallationDate: Installed on 2016-11-17 (121 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5437 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=3e120dcd-025c-491f-a62c-c4fbc272f381 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0DD2R1 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DD2R1:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674041/+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 1674041] [NEW] Keyboard backlight
Public bug reported: Key board backlight ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ganesh 2631 F pulseaudio /dev/snd/controlC0: ganesh 2631 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 19 07:59:13 2017 HibernationDevice: RESUME=UUID=eaee8605-adf5-4562-9b5a-c277f2681e6b InstallationDate: Installed on 2016-11-17 (121 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5437 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=3e120dcd-025c-491f-a62c-c4fbc272f381 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0DD2R1 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DD2R1:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- 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/1674041 Title: Keyboard backlight Status in linux package in Ubuntu: New Bug description: Key board backlight ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ganesh 2631 F pulseaudio /dev/snd/controlC0: ganesh 2631 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 19 07:59:13 2017 HibernationDevice: RESUME=UUID=eaee8605-adf5-4562-9b5a-c277f2681e6b InstallationDate: Installed on 2016-11-17 (121 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Inspiron 5437 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=3e120dcd-025c-491f-a62c-c4fbc272f381 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A10 dmi.board.name: 0DD2R1 dmi.board.vendor: Dell Inc. dmi.board.version: A10 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA10:bd06/07/2016:svnDellInc.:pnInspiron5437:pvrNotSpecified:rvnDellInc.:rn0DD2R1:rvrA10:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 5437 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674041/+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 1654319] Re: kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413
Im seeing this as well, from other posts ive seen the following is true: 1. Doesnt exist in kernel 4.4 2. Only affects esxi 6.5 with HW version 13. HW version 11 is fine. -- 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/1654319 Title: kernel BUG at /build/linux- _qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Hello everyone, I have jenkins installed with an apache frontend. Sometimes, after making few GET requests whole system crashes and restarts. ESXi host version 6.5, virtual hardware version 13. I've found similar bug report here https://bugzilla.kernel.org/show_bug.cgi?id=191201 [ 6544.559660] [ cut here ] [ 6544.559694] kernel BUG at /build/linux-_qw1uB/linux-4.8.0/drivers/net/vmxnet3/vmxnet3_drv.c:1413! [ 6544.559728] invalid opcode: [#1] SMP [ 6544.559745] Modules linked in: xt_multiport vmw_vsock_vmci_transport vsock ppdev vmw_balloon joydev coretemp input_leds serio_raw nfit shpchp i2c_piix4 vmw_vmci parport_pc parport mac_hid ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt nf_conntrack_ipv6 nf_defrag_ipv6 ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp xt_addrtype nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns ib_iser rdma_cm nf_conntrack_broadcast iw_cm nf_nat_ftp ib_cm nf_nat ib_core nf_conntrack_ftp nf_conntrack iptable_filter configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic [ 6544.560172] usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel vmwgfx ttm aesni_intel aes_x86_64 lrw glue_helper ablk_helper cryptd drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops vmxnet3 ahci libahci mptspi drm mptscsih mptbase scsi_transport_spi pata_acpi fjes [ 6544.560332] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.8.0-32-generic #34-Ubuntu [ 6544.560360] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 04/05/2016 [ 6544.560399] task: a172f62a0d00 task.stack: a172f62ac000 [ 6544.560422] RIP: 0010:[] [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3] [ 6544.560465] RSP: 0018:a172ffc83dc8 EFLAGS: 00010297 [ 6544.560487] RAX: RBX: RCX: a172efb8a000 [ 6544.560513] RDX: 0040 RSI: 0001 RDI: 0040 [ 6544.560540] RBP: a172ffc83e40 R08: 0002 R09: 0030 [ 6544.560566] R10: R11: a172ec950880 R12: a172f35cc280 [ 6544.560593] R13: a172ec951400 R14: a172f1c83000 R15: a172f2b1c000 [ 6544.560621] FS: () GS:a172ffc8() knlGS: [ 6544.560650] CS: 0010 DS: ES: CR0: 80050033 [ 6544.560671] CR2: 7f742a78da30 CR3: 00022f962000 CR4: 06e0 [ 6544.560752] Stack: [ 6544.560766] a172ec950880 a172ec950880 a172ec950880 [ 6544.560803] 002d a172ec951420 0002 00010040 [ 6544.560837] a172ec9514e8 a172ec950880 a172ec951420 [ 6544.560872] Call Trace: [ 6544.561677] [ 6544.561689] [] vmxnet3_poll_rx_only+0x3a/0xb0 [vmxnet3] [ 6544.563233] [] net_rx_action+0x238/0x380 [ 6544.564004] [] __do_softirq+0x10d/0x298 [ 6544.564757] [] irq_exit+0xa3/0xb0 [ 6544.565499] [] do_IRQ+0x54/0xd0 [ 6544.566224] [] common_interrupt+0x82/0x82 [ 6544.566928] [ 6544.566940] [] ? native_safe_halt+0x6/0x10 [ 6544.568313] [] default_idle+0x20/0xd0 [ 6544.568978] [] arch_cpu_idle+0xf/0x20 [ 6544.569625] [] default_idle_call+0x2a/0x40 [ 6544.570255] [] cpu_startup_entry+0x2ec/0x350 [ 6544.570871] [] start_secondary+0x151/0x190 [ 6544.571475] Code: 90 88 45 98 4c 89 55 a0 e8 4d 70 e9 d8 0f b6 45 98 4c 8b 5d 90 4c 8b 55 a0 49 c7 85 60 01 00 00 00 00 00 00 89 c6 e9 91 f8 ff ff <0f> 0b 0f 0b 49 83 85 b8 01 00 00 01 49 c7 85 60 01 00 00 00 00 [ 6544.573327] RIP [] vmxnet3_rq_rx_complete+0x8d1/0xeb0 [vmxnet3] [ 6544.573926] RSP BR, Mikolaj Kowalski ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-32-generic 4.8.0-32.34 ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11 Uname: Linux 4.8.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 sty 3 17:47 seq crw-rw 1 root audio 116, 33 sty 3 17:47 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 ArecordDevices:
[Kernel-packages] [Bug 1530405] Re: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814]
I have a new laptop Asus UX360UAK with this issue too: soft lockup CPU stuck for XX seconds -- 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/1530405 Title: NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Status in linux package in Ubuntu: Triaged Bug description: I'm using Ubuntu Xenial 16.04 and my computer (ASUS M32BF) will randomly freeze up, sometimes before the login screen, sometimes while I'm in the middle of using a program. This sometimes happens on the Wily 15.10 live cd as well, and on both kernel 4.3.0-2, and kernel 4.2.0-22. Important part of log: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112129] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kerneloops:814] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112134] Modules linked in: rfcomm bnep nls_iso8859_1 kvm_amd kvm eeepc_wmi asus_wmi crct10dif_pclmul sparse_keymap crc32_pclmul aesni_intel aes_x86_64 arc4 lrw gf128mul rtl8821ae glue_helper snd_hda_codec_realtek ablk_helper snd_hda_codec_generic snd_hda_codec_hdmi snd_hda_intel btcoexist snd_hda_codec rtl_pci snd_hda_core joydev input_leds snd_hwdep rtlwifi snd_pcm fam15h_power cryptd snd_seq_midi serio_raw snd_seq_midi_event snd_rawmidi mac80211 snd_seq snd_seq_device snd_timer cfg80211 btusb btrtl btbcm btintel bluetooth snd soundcore edac_mce_amd k10temp edac_core i2c_piix4 shpchp mac_hid parport_pc ppdev lp parport autofs4 hid_logitech_hidpp uas usb_storage hid_logitech_dj usbhid hid amdkfd amd_iommu_v2 radeon i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops r8169 psmouse mii drm ahci libahci wmi fjes video Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112183] CPU: 0 PID: 814 Comm: kerneloops Not tainted 4.3.0-2-generic #11-Ubuntu Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112184] Hardware name: ASUSTeK COMPUTER INC. K30BF_M32BF_A_F_K31BF_6/K30BF_M32BF_A_F_K31BF_6, BIOS 0501 07/09/2015 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112186] task: 88031146d400 ti: 88030e838000 task.ti: 88030e838000 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112188] RIP: 0010:[] [] __do_softirq+0x76/0x250 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112194] RSP: 0018:88031fc03f30 EFLAGS: 0202 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112196] RAX: 88030e83c000 RBX: RCX: 40400040 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112197] RDX: RSI: 613e RDI: 0380 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112198] RBP: 88031fc03f80 R08: 0029f8fa1411 R09: 88031fc169f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112199] R10: 0020 R11: 0004 R12: 88031fc169c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112201] R13: 88030df8e200 R14: R15: 0001 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112202] FS: 7f6c266ac880() GS:88031fc0() knlGS: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112203] CS: 0010 DS: ES: CR0: 80050033 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112205] CR2: 7ffef000bff8 CR3: 00030f368000 CR4: 000406f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112206] Stack: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112207] 404000401fc03f78 88030e83c000 0121 8803000a Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112209] 00021fc0d640 88031fc169c0 88030df8e200 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112211] 0001 88031fc03f90 81081d23 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112213] Call Trace: Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112215] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112219] [] irq_exit+0xa3/0xb0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.11] [] smp_apic_timer_interrupt+0x42/0x50 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112225] [] apic_timer_interrupt+0x82/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112226] Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112230] [] ? finish_task_switch+0x67/0x1c0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112232] [] __schedule+0x36c/0x980 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112234] [] schedule+0x33/0x80 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112236] [] do_nanosleep+0x6f/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112239] [] hrtimer_nanosleep+0xdc/0x1f0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112241] [] ? __hrtimer_init+0x90/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112243] [] ? do_nanosleep+0x5a/0xf0 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112245] [] SyS_nanosleep+0x7a/0x90 Dec 31 19:13:12 COMPUTERNAME kernel: [ 64.112247] [] entry_SYSCALL_64_fastpath+0x16/0x71 Dec 31 19:13:12
[Kernel-packages] [Bug 1673678] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. >From a terminal window please run: apport-collect 1673678 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/1673678 Title: System doesn't shut down Status in linux package in Ubuntu: Incomplete Bug description: Sometimes the system doesn't shut down. The log reports the opposite (maybe it reports the hard reset?), but the systems keeps running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673678/+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 1571416] Re: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC)
I tried that and got a syntax error on reboot that I couldn't recover from. I'll look at it again. -- 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/1571416 Title: System freezes shortly after reaching the desktop (Ubuntu MATE 16.04, PowerPC) Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: The freeze happens every time unless I use "radeon.agpmode=-1" as a kernel parameter. Affected machines: PowerBook G4 5,6 + PowerMac G5 7,3 (w. "ATI Radeon 9600 AP (AGP)". ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-18-powerpc-smp 4.4.0-18.34 ProcVersionSignature: Ubuntu 4.4.0-18.34-powerpc-smp 4.4.6 Uname: Linux 4.4.0-18-powerpc-smp ppc ApportVersion: 2.20.1-0ubuntu2 Architecture: powerpc AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperVersion: 1.373 CurrentDesktop: MATE Date: Sun Apr 17 21:08:40 2016 IwConfig: lono wireless extensions. enP2p36s15f0 no wireless extensions. LiveMediaBuild: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release powerpc (20160417.1) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: ro ramdisk_size=1048576 file=/cdrom/preseed/username.seed boot=casper quiet --- radeon.agpmode=-1 RelatedPackageVersions: linux-restricted-modules-4.4.0-18-powerpc-smp N/A linux-backports-modules-4.4.0-18-powerpc-smp N/A linux-firmware1.157 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1571416/+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 1673678] Re: System doesn't shut down
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: ubuntu-mate -- 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/1673678 Title: System doesn't shut down Status in linux package in Ubuntu: New Bug description: Sometimes the system doesn't shut down. The log reports the opposite (maybe it reports the hard reset?), but the systems keeps running. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673678/+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 1674027] 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/1674027 Title: kernel crash during login Status in linux package in Ubuntu: Confirmed Bug description: System works fine with kernel version 4.8.0-37; since 4.8.0-38 I experience a kernel crash when trying to login; login screen just freezes; switching to a console (tty3) instead and trying to login right after entering the pwd I can see that a kernel crash happend and then graphic starts to flicker. Tested for versions kernel > 4.8.0-37 (latest 4.8.0-41). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmetz 2104 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 18 23:10:48 2017 HibernationDevice: RESUME=UUID=77c0b4cc-9c43-4f05-bb93-83eb6cd6caa2 InstallationDate: Installed on 2016-12-17 (91 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: FUJITSU LIFEBOOK P771 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=03f807d5-5fe0-4b2a-a6e5-3c5c2eab002a ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNB22A dmi.board.vendor: FUJITSU dmi.board.version: J5 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P771 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd04/19/2013:svnFUJITSU:pnLIFEBOOKP771:pvr10601115935:rvnFUJITSU:rnFJNB22A:rvrJ5:cvnFUJITSU:ct10:cvrLIFEBOOKP771: dmi.product.name: LIFEBOOK P771 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674027/+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 1674027] [NEW] kernel crash during login
Public bug reported: System works fine with kernel version 4.8.0-37; since 4.8.0-38 I experience a kernel crash when trying to login; login screen just freezes; switching to a console (tty3) instead and trying to login right after entering the pwd I can see that a kernel crash happend and then graphic starts to flicker. Tested for versions kernel > 4.8.0-37 (latest 4.8.0-41). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmetz 2104 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 18 23:10:48 2017 HibernationDevice: RESUME=UUID=77c0b4cc-9c43-4f05-bb93-83eb6cd6caa2 InstallationDate: Installed on 2016-12-17 (91 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: FUJITSU LIFEBOOK P771 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=03f807d5-5fe0-4b2a-a6e5-3c5c2eab002a ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNB22A dmi.board.vendor: FUJITSU dmi.board.version: J5 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P771 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd04/19/2013:svnFUJITSU:pnLIFEBOOKP771:pvr10601115935:rvnFUJITSU:rnFJNB22A:rvrJ5:cvnFUJITSU:ct10:cvrLIFEBOOKP771: dmi.product.name: LIFEBOOK P771 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety -- 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/1674027 Title: kernel crash during login Status in linux package in Ubuntu: New Bug description: System works fine with kernel version 4.8.0-37; since 4.8.0-38 I experience a kernel crash when trying to login; login screen just freezes; switching to a console (tty3) instead and trying to login right after entering the pwd I can see that a kernel crash happend and then graphic starts to flicker. Tested for versions kernel > 4.8.0-37 (latest 4.8.0-41). ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-37-generic 4.8.0-37.39 ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16 Uname: Linux 4.8.0-37-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mmetz 2104 F pulseaudio CurrentDesktop: GNOME Date: Sat Mar 18 23:10:48 2017 HibernationDevice: RESUME=UUID=77c0b4cc-9c43-4f05-bb93-83eb6cd6caa2 InstallationDate: Installed on 2016-12-17 (91 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: FUJITSU LIFEBOOK P771 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-37-generic.efi.signed root=UUID=03f807d5-5fe0-4b2a-a6e5-3c5c2eab002a ro quiet splash crashkernel=384M-:128M vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-37-generic N/A linux-backports-modules-4.8.0-37-generic N/A linux-firmware1.161.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/19/2013 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.17 dmi.board.name: FJNB22A dmi.board.vendor: FUJITSU dmi.board.version: J5 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.chassis.version: LIFEBOOK P771 dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.17:bd04/19/2013:svnFUJITSU:pnLIFEBOOKP771:pvr10601115935:rvnFUJITSU:rnFJNB22A:rvrJ5:cvnFUJITSU:ct10:cvrLIFEBOOKP771: dmi.product.name: LIFEBOOK P771 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674027/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1667323] Re: Backlight control does not work and there are no entries in /sys/class/backlight
The first kernel to has this bug is 4.4.41. I ended up testing all of them, so: 4.4.40 good 4.4.41 bad 4.4.42 bad 4.4.43 bad 4.4.44 bad -- 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/1667323 Title: Backlight control does not work and there are no entries in /sys/class/backlight Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: It was working fine until today. The folder /sys/class/backlight/ use to have "acpi_video0/brightness", but now is empty. I am using Nvidia Proprietary driver 340.101 (proprietary, tested). The problem persists even with the 304 driver. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-64-generic 4.4.0-64.85 ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44 Uname: Linux 4.4.0-64-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: desgua 2028 F pulseaudio /dev/snd/controlC0: desgua 2028 F pulseaudio CurrentDesktop: Unity Date: Thu Feb 23 11:31:18 2017 HibernationDevice: RESUME=UUID=f23a6347-9483-460e-aa29-cbc47850f890 InstallationDate: Installed on 2014-05-01 (1028 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Lsusb: Bus 002 Device 003: ID 064e:a127 Suyin Corp. 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 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Pavilion dv6 Notebook PC ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-64-generic root=/dev/mapper/ubuntu--vg-root ro RelatedPackageVersions: linux-restricted-modules-4.4.0-64-generic N/A linux-backports-modules-4.4.0-64-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: Upgraded to xenial on 2016-08-17 (189 days ago) dmi.bios.date: 12/03/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.13 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 3659 dmi.board.vendor: Hewlett-Packard dmi.board.version: 32.23 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.13:bd12/03/2009:svnHewlett-Packard:pnHPPaviliondv6NotebookPC:pvr049D212412102:rvnHewlett-Packard:rn3659:rvr32.23:cvnHewlett-Packard:ct10:cvrN/A: dmi.product.name: HP Pavilion dv6 Notebook PC dmi.product.version: 049D212412102 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667323/+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 1673796] Re: Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume
Just tried kernel 4.11.0-041100rc2-generic one. Looks like that the bug is happening (had some issues compiling the DKMS nvidia-357 and virtualbox, but still could boot up that kernel). ** Tags added: kernel-bug-exists-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/1673796 Title: Ubuntu 16.10, Dell XPS 15 9550, DNS problem after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: After suspend/resume the wifi network comes back, but the DNS doesn't work. I've tried to ping a known IP and it works ok though. My normal solution is to restart the network totally (haven't found a smaller way to fix the skewed DNS server locally): sudo systemctl restart network-manager.service Not sure if I should report this on other package related to the DNS systemd resolve? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-42-generic 4.8.0-42.45 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: cruz 2658 F...m pulseaudio /dev/snd/controlC0: cruz 2658 F pulseaudio CurrentDesktop: Unity Date: Fri Mar 17 11:34:54 2017 HibernationDevice: RESUME=UUID=afd0c8e7-78e3-47d1-b086-10c627ac3d76 InstallationDate: Installed on 2016-06-13 (277 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Bus 001 Device 002: ID 0a5c:6410 Broadcom Corp. Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic root=UUID=0bdc13dd-b122-4879-8d8a-31cce3301ef5 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-42-generic N/A linux-backports-modules-4.8.0-42-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2017-03-08 (8 days ago) dmi.bios.date: 12/22/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.19 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.19:bd12/22/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673796/+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 1576196] Re: Ubuntu 16.04 doesn't recognize CyPS/2 Cypress Trackpad
** Changed in: linux (Ubuntu) Status: Expired => 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/1576196 Title: Ubuntu 16.04 doesn't recognize CyPS/2 Cypress Trackpad Status in linux package in Ubuntu: Fix Released Bug description: Laptop: Dell XPS13 L321x Trackpad: Cypress Trackpad / Clickpad Problem appeared after update from 14.04 to 16.04 The touchpad is not listed under /proc/bus/input/devices altough it shows up if using 14.04 via live usb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1576196/+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 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install
Never active proposed/romeo repository if you want a stable & productive environment! The proposed/romeo repository is for the builds, which needs to be tested! -- 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/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic' --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: heiko 2688 F...m pulseaudio /dev/snd/controlC0: heiko 2688 F pulseaudio /dev/snd/controlC2: heiko 2688 F pulseaudio /dev/snd/controlC1: heiko 2688 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175 InstallationDate: Installed on 2015-12-03 (383 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115 MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.157.6 RfKill: Tags: serena Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 1566987] Re: No internet connection through WLAN although connected to network
Having the same Problem. It's 17.04 (newest). I was asked by the system to type my passphrase into the field for network connection and after i've done, it seemed to connect but the connection failed without any message or some and due to the failing internet/network connection i can't send any bug report relating this problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1566987 Title: No internet connection through WLAN although connected to network Status in linux package in Ubuntu: Confirmed Bug description: In a fresh install of Kubuntu 16.04 on a ThinkPad t460s, I can connect wireless to the local WLAN, but I don't have an internet connection. A ping to the router doesn't work in that case. After some minutes, the connection usually (but not always) works. A LAN connection through the same router works, too. It seems that the problem doesn't occur in every WLAN, but in my home network (using an O2 box 6431) it always does. The problem is reproducible with a Kubuntu Live CD/USB. The following steps did not solve the problem: - Reconnect to WLAN - Using kernel 4.6 or 4.7 - Restarting NetworkManager and networking service - Disable IPv6 - Factory reset of the o2 box - Restart of the o2 box (sometimes it helps temporarily) --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2016-04-04 (294 days ago) InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323) Package: linux (not installed) Tags: xenial Uname: Linux 4.7.4-040704-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/1566987/+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 1561474] Re: Bluetooth will be disable after resume from suspend on Xenial
Affects me on Lenovo X1 Carbon with Ubuntu 16.04 4.4.0-65-generic. Might be some kind of race condition when going to sleep. I read somewhere that hardware does not always notify the kernel (in time) that it goes to sleep... Another story is that I shortly the screen with open windows before the lock screen appears and asks for password. -- 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/1561474 Title: Bluetooth will be disable after resume from suspend on Xenial Status in linux package in Ubuntu: Confirmed Bug description: CID: 201208-11536 Dell Latitude 6430u The Bluetooth will be disabled after resume from suspend. You will need to use "hciconfig hci0 reset" to enable it. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-15-generic 4.4.0-15.31 ProcVersionSignature: Ubuntu 4.4.0-15.31-generic 4.4.6 Uname: Linux 4.4.0-15-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1202 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 24 19:14:07 2016 HibernationDevice: RESUME=UUID=25c03762-079c-4c6d-aedb-ec768318a6bf InstallationDate: Installed on 2016-03-24 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151209) MachineType: Dell Inc. Latitude 6430U ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-15-generic root=UUID=18cfda3e-4f3d-40cf-8e7e-a83030819487 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-15-generic N/A linux-backports-modules-4.4.0-15-generic N/A linux-firmware1.157 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.asset.tag: 1234567 dmi.board.name: 0MN74V dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.asset.tag: 1234567 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA02:bd11/15/2012:svnDellInc.:pnLatitude6430U:pvr01:rvnDellInc.:rn0MN74V:rvrX01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 6430U 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/1561474/+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 1672439] Re: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520
Kai-Heng Feng, I also noticed that by default the scaling driver used is acpi-cpufreq and not p-state. I've read that p-state is favorable for kernels >= 4.4. Is this something that is up to the user to decide or should this be considered an incorrect default? analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 10.0 us. hardware limits: 800 MHz - 2.80 GHz available frequency steps: 2.80 GHz, 2.80 GHz, 2.70 GHz, 2.60 GHz, 2.40 GHz, 2.30 GHz, 2.00 GHz, 1.90 GHz, 1.80 GHz, 1.70 GHz, 1.50 GHz, 1.40 GHz, 1.20 GHz, 1.10 GHz, 900 MHz, 800 MHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance current policy: frequency should be within 800 MHz and 2.80 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 900 MHz (asserted by call to hardware). cpufreq stats: 2.80 GHz:2.85%, 2.80 GHz:0.00%, 2.70 GHz:0.25%, 2.60 GHz:0.64%, 2.40 GHz:0.65%, 2.30 GHz:1.42%, 2.00 GHz:2.07%, 1.90 GHz:1.27%, 1.80 GHz:1.64%, 1.70 GHz:3.14%, 1.50 GHz:3.57%, 1.40 GHz:5.39%, 1.20 GHz:6.85%, 1.10 GHz:13.39%, 900 MHz:29.31%, 800 MHz:27.53% (2074191) boost state support: Supported: yes Active: yes -- 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/1672439 Title: No C-State Deeper than C3 utilized by Kaby Lake 7820HQ in Precision 5520 Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: In Progress Bug description: My processor does not appear to be utilizing and idling states deeper than C3. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: carl 2446 F pulseaudio CurrentDesktop: Unity Date: Mon Mar 13 08:57:06 2017 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 HibernationDevice: RESUME=UUID=65474558-ead3-4d66-85e5-b55f81978b88 InstallationDate: Installed on 2017-03-09 (3 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 IwConfig: lono wireless extensions. wlp2s0no wireless extensions. MachineType: Dell Inc. Precision 5520 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic.efi.signed root=UUID=d19efcb8-515b-494c-a236-ee0da23f2393 ro acpi_rev_override locale=C quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0X41RR dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd01/18/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672439/+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 1629415] Re: Broken hardware buttons on Dell XPS 12-9Q33
I have same problem with Acer Switch 12. Buttons have never worked on any kernel up to 4.4.0-66. They have the same index numbers. -- 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/1629415 Title: Broken hardware buttons on Dell XPS 12-9Q33 Status in linux package in Ubuntu: Confirmed Bug description: System Ubuntu 16.04 Kernel 4.4.0-36 and newer break the hardware volume control buttons on Dell XPS 12-9Q33. On key press kernel reports: intel-vbtn INT33D6:00: unknown event index 0xc6 intel-vbtn INT33D6:00: unknown event index 0xc7 --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: halbamy1631 F pulseaudio /dev/snd/controlC0: halbamy1631 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=d26cee8a-01a4-4c7d-bba9-9573c01d1ca5 InstallationDate: Installed on 2016-03-15 (200 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. XPS 12-9Q33 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-38-generic root=UUID=94f9e5d4-c056-4277-97b7-8cad719003c8 ro ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 RelatedPackageVersions: linux-restricted-modules-4.4.0-38-generic N/A linux-backports-modules-4.4.0-38-generic N/A linux-firmware1.157.3 Tags: xenial Uname: Linux 4.4.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin mythtv plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 03/03/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: XPS 12-9Q33 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: XPS 12-9Q33 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/1629415/+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 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install
How do you enable 'proposed' repository in LM 18.1? -- 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/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic' --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: heiko 2688 F...m pulseaudio /dev/snd/controlC0: heiko 2688 F pulseaudio /dev/snd/controlC2: heiko 2688 F pulseaudio /dev/snd/controlC1: heiko 2688 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175 InstallationDate: Installed on 2015-12-03 (383 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115 MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.157.6 RfKill: Tags: serena Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2014 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1001810] Re: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS
** Also affects: linux-lts-xenial (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1001810 Title: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS Status in linux-lts-trusty package in Ubuntu: New Status in linux-lts-xenial package in Ubuntu: New Status in vdradmin-am package in Ubuntu: New Bug description: Only the most experienced VDR users can be expected to figure out (let alone know) that vdradmin-am will not work because it needs to have its configuration changed to ENABLED="1" e.g. by: Ctrl-Alt-T sudo nano -w /etc/default/vdradmin-am Its weak default password on port 8001 is no reason to keep it this way, but rather to ask for a stronger one during installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1001810/+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 967399] Re: [11.10] Elantech trackpoint does not work Lenovo
I have the similar problem in ThinkPad Twis: after turn off computer and boot - trackpad and touchpad doesn't work. If restart - it works again. I found this helpful: http://askubuntu.com/questions/763763/touchpad-under-16-04-not-working Need edit grub and trackpad and touch pad now works after shutdown and boot. -- 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/967399 Title: [11.10] Elantech trackpoint does not work Lenovo Status in linux package in Ubuntu: In Progress Status in linux source package in Precise: Fix Released Bug description: Title: trackpoint does not function Summary: trackpoint does not function Steps: 1. log into desktop 2. use trackpoint and trackpoint buttons Expected results: laptop responds to trackpoint and trackpoint buttons being pressed Actual results: nothing happens Manufacturer: LENOVO WORKAROUND: sudo modprobe proto=exps enables the trackpoint and touchpad, but user will lose multi-touch functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/967399/+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 1673961] 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/1673961 Title: [ASUS ZENBOOK UX31A] Bluetooth problems Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth is not always "up" after reboot. When it is down", I need to open/close the screen several times in order to get it "up". It was yet a problem before 16.04 LTS (new installation). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stef 2266 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 18 14:14:43 2017 HibernationDevice: RESUME=UUID=b9fad596-3f76-4c1a-bb2f-fb97d53143f0 InstallationDate: Installed on 2017-01-21 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=926de407-6887-4e54-bf0a-7dfb2ff90e29 ro quiet splash rootfstype=ext4 acpi_osi=Linux pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673961/+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 1673961] [NEW] [ASUS ZENBOOK UX31A] Bluetooth problems
Public bug reported: Bluetooth is not always "up" after reboot. When it is down", I need to open/close the screen several times in order to get it "up". It was yet a problem before 16.04 LTS (new installation). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stef 2266 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 18 14:14:43 2017 HibernationDevice: RESUME=UUID=b9fad596-3f76-4c1a-bb2f-fb97d53143f0 InstallationDate: Installed on 2017-01-21 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=926de407-6887-4e54-bf0a-7dfb2ff90e29 ro quiet splash rootfstype=ext4 acpi_osi=Linux pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug xenial -- 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/1673961 Title: [ASUS ZENBOOK UX31A] Bluetooth problems Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth is not always "up" after reboot. When it is down", I need to open/close the screen several times in order to get it "up". It was yet a problem before 16.04 LTS (new installation). ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-66-generic 4.4.0-66.87 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stef 2266 F pulseaudio CurrentDesktop: Unity Date: Sat Mar 18 14:14:43 2017 HibernationDevice: RESUME=UUID=b9fad596-3f76-4c1a-bb2f-fb97d53143f0 InstallationDate: Installed on 2017-01-21 (55 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: ASUSTeK Computer Inc. UX31E ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic root=UUID=926de407-6887-4e54-bf0a-7dfb2ff90e29 ro quiet splash rootfstype=ext4 acpi_osi=Linux pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-66-generic N/A linux-backports-modules-4.4.0-66-generic N/A linux-firmware1.157.8 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/21/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX31E.213 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX31E dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX31E.213:bd06/21/2012:svnASUSTeKComputerInc.:pnUX31E:pvr1.0:rvnASUSTeKComputerInc.:rnUX31E:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: UX31E dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1673961/+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 1001810] Re: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS
Since /var/cache/vdradmin-am/usr/ through /var/cache/vdradmin-am/usr/share/vdradmin-am/template belong to root:root rather than vdradmin-am:vdradmin-am (and look like they have wrongly been placed into a relative path), the Perl Zlib issue can be fixed by sudo chown -R vdradmin-am:vdradmin-am /var/cache/vdradmin-am/usr && sudo service vdradmin-am restart cf. http://www.vdr-portal.de/board60-linux/board14-betriebssystem/board68-debian-und-derivate/p1128803-vdr-auf-raspberry-mit-weezy/#post1128803 et seq. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1001810 Title: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS Status in linux-lts-trusty package in Ubuntu: New Status in vdradmin-am package in Ubuntu: New Bug description: Only the most experienced VDR users can be expected to figure out (let alone know) that vdradmin-am will not work because it needs to have its configuration changed to ENABLED="1" e.g. by: Ctrl-Alt-T sudo nano -w /etc/default/vdradmin-am Its weak default password on port 8001 is no reason to keep it this way, but rather to ask for a stronger one during installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1001810/+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 1001810] Re: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS
Still the same old (and now new) bugs in Ubuntu 16.04.2 LTS, not logging or returning any reason why "sudo service vdradmin-am start had" no effect either. For a web interface, there really shouldn't be a weak, plaintext default PASSWORD = linvdr in /var/lib/vdradmin-am/vdradmind.conf in 2017 (or ever have been). After logging in, one is greeted with just this: Not a SCALAR reference at /usr/share/perl/5.22/Compress/Zlib.pm line 482. Users are also likely to be misled by (what is only due to their respective rights): $ vdradmind ERROR: directory '/var/lib/vdradmin-am' is NOT writable! ERROR: directory '/var/cache/vdradmin-am' is NOT writable! ERROR: directory '/var/log/vdradmin-am' is NOT writable! ERROR: directory '/var/run/vdradmin-am' is NOT writable! ERROR: file '/var/lib/vdradmin-am/vdradmind.conf' is NOT readable! ERROR: file '/var/lib/vdradmin-am/vdradmind.at' is NOT writable! ERROR: directory '/var/lib/vdradmin-am' is NOT writable! ERROR: directory '/var/lib/vdradmin-am' is NOT writable! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1001810 Title: vdradmin-am preconfigured not to (auto)start in Ubuntu 12.04 LTS Status in linux-lts-trusty package in Ubuntu: New Status in vdradmin-am package in Ubuntu: New Bug description: Only the most experienced VDR users can be expected to figure out (let alone know) that vdradmin-am will not work because it needs to have its configuration changed to ENABLED="1" e.g. by: Ctrl-Alt-T sudo nano -w /etc/default/vdradmin-am Its weak default password on port 8001 is no reason to keep it this way, but rather to ask for a stronger one during installation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-trusty/+bug/1001810/+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 1579374] Re: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU
** Also affects: linux 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/1579374 Title: amdgpu causes NULL pointer dereference when trying to use Topaz (Radeon R7 M265) GPU Status in Linux: New Status in linux package in Ubuntu: Expired Bug description: A Dell Inspiron 5448 / 0YDTG3 laptop (BIOS A06 10/12/2015), which used to work well with Ubuntu trusty and Ubuntu wily releases (using fglrx driver), has an issue in Xenial where when the amdgpu driver tries to activate the Radeon GPU, a NULL pointer dereference occurs, causing the caller process to hang. This practically causes the system to hang when trying a logoff or shutdown. The bug can be easily reproduced by calling: DRI_PRIME=1 glxgears Which hangs the glxgears process and causes the stacktrace attached below. ---[cut]--- $ dmesg [...] [ 129.188685] [drm] PCIE GART of 2048M enabled (table at 0x0004). [ 129.429667] [drm] ring test on 0 succeeded in 14 usecs [ 131.087501] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 1 (-2). [ 131.087520] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 2 (-2). [ 131.087533] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 3 (-2). [ 131.087547] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 4 (-2). [ 131.087558] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 5 (-2). [ 131.087571] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 6 (-2). [ 131.087582] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 7 (-2). [ 131.087595] [drm:gfx_v8_0_ring_test_ring [amdgpu]] *ERROR* amdgpu: cp failed to lock ring 8 (-2). [ 131.191024] [drm:sdma_v2_4_ring_test_ring [amdgpu]] *ERROR* amdgpu: ring 9 test failed (0xCAFEDEAD) [ 131.191034] [drm:amdgpu_resume [amdgpu]] *ERROR* resume 5 failed -22 [ 131.191043] [drm:amdgpu_resume_kms [amdgpu]] *ERROR* amdgpu_resume failed (-22). [ 131.191149] amdgpu :04:00.0: couldn't schedule ib [ 131.191179] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.191203] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201417] amdgpu :04:00.0: couldn't schedule ib [ 131.201444] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201462] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201465] amdgpu :04:00.0: couldn't schedule ib [ 131.201479] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201493] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201494] amdgpu :04:00.0: couldn't schedule ib [ 131.201508] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201523] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201524] amdgpu :04:00.0: couldn't schedule ib [ 131.201535] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201546] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201548] amdgpu :04:00.0: couldn't schedule ib [ 131.201558] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201569] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201571] amdgpu :04:00.0: couldn't schedule ib [ 131.201581] [drm:amdgpu_sched_run_job [amdgpu]] *ERROR* Error scheduling IBs (-22) [ 131.201592] [drm:amd_sched_main [amdgpu]] *ERROR* Failed to run job! [ 131.201616] BUG: unable to handle kernel NULL pointer dereference at 0248 [ 131.201648] IP: [] amdgpu_vm_grab_id+0x122/0x310 [amdgpu] [ 131.201684] PGD 0 [ 131.201693] Oops: [#1] SMP [ 131.201707] Modules linked in: ctr ccm rfcomm pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc rtsx_usb_ms memstick nls_iso8859_1 dell_wmi sparse_keymap dell_laptop intel_rapl x86_pkg_temp_thermal arc4 intel_powerclamp dcdbas dell_smm_hwmon coretemp dell_led iwlmvm btusb uvcvideo btrtl btbcm btintel mac80211 bluetooth kvm_intel videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core snd_soc_rt5640 v4l2_common videodev snd_hda_codec_realtek snd_hda_codec_hdmi media snd_soc_ssm4567 snd_hda_codec_generic snd_soc_rl6231 kvm snd_soc_core snd_hda_intel hid_multitouch snd_hda_codec iwlwifi irqbypass snd_hda_core snd_compress ac97_bus snd_hwdep snd_pcm_dmaengine cfg80211 snd_pcm snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq joydev input_leds snd_seq_device mei_me [ 131.202004] serio_raw snd_timer mei snd shpchp lpc_ich elan_i2c soundcore spi_pxa2xx_platform snd_soc_sst_acpi dw_dmac acpi_pad dw_dmac_core dell_rbtn
[Kernel-packages] [Bug 1673333] Re: package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade: unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547
Are you running any virus scanner like Sophos? I had the same issue (the file that failed was different each time). I disabled sophos by running # sudo /opt/sophos-av/bin/savdctl disable before running apt. -- 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/167 Title: package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade: unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach- bf548/include/mach/defBF547.h.dpkg-new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: This error occurred at the final stages of installing updates. I had run sudo apt-get update followed by sudo apt-get dist-upgrade This seems to happen in one form or another periodically. The fix is to run sudo apt-get -f install until it doesn't fail. Sometimes once, in this case 5 or 6 times. Eventually, the install finished without errors, and then I restart, and everything tends to be ok. It seems that running it until it fixes the broken dependencies is just a normal part of updating? I've checked my drives for any signs of issues, and the smart utilities show no problems. If I'm doing something wrong, please let me know what it is, and I'll try and fix it. ProblemType: Package DistroRelease: Ubuntu 16.10 Package: linux-headers-4.8.0-42 4.8.0-42.45 ProcVersionSignature: Ubuntu 4.8.0-42.45-generic 4.8.17 Uname: Linux 4.8.0-42-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jerry.lumpkins 4213 F pulseaudio Date: Thu Mar 16 01:24:16 2017 DuplicateSignature: package:linux-headers-4.8.0-42:4.8.0-42.45 Unpacking linux-image-extra-4.8.0-42-generic (4.8.0-42.45) ... dpkg: error processing archive /tmp/apt-dpkg-install-rwCZmk/182-linux-image-extra-4.8.0-42-generic_4.8.0-42.45_amd64.deb (--unpack): unable to open '/lib/modules/4.8.0-42-generic/kernel/drivers/staging/lustre/lustre/lmv/lmv.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547.h.dpkg-new': Operation not permitted HibernationDevice: RESUME=UUID=4c1c5e08-0209-47f6-8250-d5e9218964b4 InstallationDate: Installed on 2014-12-08 (829 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name PackageArchitecture: all ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-42-generic root=UUID=58e4f4be-3dfc-4eaf-91b0-d70f9c1c7640 ro cgroup_enable=memory swapaccount=1 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-headers-4.8.0-42 4.8.0-42.45 failed to install/upgrade: unable to open '/usr/src/linux-headers-4.8.0-42/arch/blackfin/mach-bf548/include/mach/defBF547.h.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to yakkety on 2016-10-23 (144 days ago) dmi.bios.date: 10/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0502 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5G41T-M LX PLUS dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5G41T-MLXPLUS:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/167/+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 1657994] Re: Regression: HDMI audio produces no sound (Skylake NUC)
I had been trying to cherry-pick patches from the working Xenial kernel to mainline, and got bogged down with build issues. Back to the bisection: This kernel ... http://kernel.ubuntu.com/~jsalisbury/lp1657994/linux-image-4.4.0-040400-generic_4.4.0-040400.201702021530_amd64.deb .. does not work. Failure mode like 4.4 mainline. I can also update that mainline kernels 4.10.3 and 4.11-rc2 both fail like other recent mainline kernels. To recap, we have only two working data points, both Xenial kernels (4.4+i915 backport). 4.4.0-59 4.4.0-21 All mainline 4.4 kernels do not even enumerate HDMI audio. All mainline kernels from 4.5-rc1 and later enumerate HDMI audio but produce no sound. -- 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/1657994 Title: Regression: HDMI audio produces no sound (Skylake NUC) Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After upgrade from Xenial 16.04 to Yakkety 16.10, playing audio over HDMI no longer produces sound. * When booting with old kernel from Xenial (4.4.0-59), HDMI audio works fine * Audio from headphone jack works fine * Userspace seems to be happily playing to HDMI audio device, but no sound produced at HDMI sink (Samsung TV) Any of a wide range of pre-built mainline kernels fail to produce HDMI audio, but with a different failure mode (HDMI audio does not seem to be enumerated in the same way as in the Ubuntu kernels.) ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-34-generic 4.8.0-34.36 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: israel 1973 F pulseaudio /dev/snd/controlC1: israel 1973 F pulseaudio CurrentDesktop: Unity Date: Fri Jan 20 08:58:35 2017 HibernationDevice: RESUME=UUID=ca27f739-071f-4c25-974e-0d0f0614b21c InstallationDate: Installed on 2016-10-03 (108 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-34-generic.efi.signed root=UUID=90c3e094-e890-4c35-a0d2-0a358f5d2430 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.8.0-34-generic N/A linux-backports-modules-4.8.0-34-generic N/A linux-firmware1.161.1 SourcePackage: linux UpgradeStatus: Upgraded to yakkety on 2017-01-13 (6 days ago) dmi.bios.date: 06/03/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: KYSKLi70.86A.0037.2016.0603.1032 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-405 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrKYSKLi70.86A.0037.2016.0603.1032:bd06/03/2016:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-405:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657994/+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 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install
Installing the ndiswrapper 1.60-3 from the "proposed" repository solved the problem. But enabling the "proposed" repository or installing any of its packages is not a stable solution, there are too many unstable packages with side effects... -- 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/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic' --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: heiko 2688 F...m pulseaudio /dev/snd/controlC0: heiko 2688 F pulseaudio /dev/snd/controlC2: heiko 2688 F pulseaudio /dev/snd/controlC1: heiko 2688 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175 InstallationDate: Installed on 2015-12-03 (383 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115 MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.157.6 RfKill: Tags: serena Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably
[Kernel-packages] [Bug 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install
Error! Bad return status for module build on kernel: 4.8.0-41-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information. DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) Sa 18. Mär 10:21:55 CET 2017 make: Verzeichnis „/usr/src/linux-headers-4.8.0-41-generic“ wird betreten LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: die Regel für Ziel „/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o“ scheiterte make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Fehler 1 Makefile:1491: die Regel für Ziel „_module_/var/lib/dkms/ndiswrapper/1.59/build“ scheiterte make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Fehler 2 make: Verzeichnis „/usr/src/linux-headers-4.8.0-41-generic“ wird verlassen ** This bug is no longer a duplicate of bug 1625089 ndiswrapper <= 1.60-2 ADT test failure with linux 4.8.0-11.12 ** Also affects: linux-hwe (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe (Ubuntu) Status: New => Incomplete ** Changed in: linux-hwe (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install + ndiswrapper-1.59 for kernel 4.8.0-41.44~16.04.1 (x86_64) doesn't compile/install ** Summary changed: - ndiswrapper-1.59 for kernel 4.8.0-41.44~16.04.1 (x86_64) doesn't compile/install + ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install -- 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/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-41-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS
[Kernel-packages] [Bug 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install
*** This bug is a duplicate of bug 1625089 *** https://bugs.launchpad.net/bugs/1625089 ** This bug has been marked a duplicate of bug 1625089 ndiswrapper <= 1.60-2 ADT test failure with linux 4.8.0-11.12 -- 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/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic' --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: heiko 2688 F...m pulseaudio /dev/snd/controlC0: heiko 2688 F pulseaudio /dev/snd/controlC2: heiko 2688 F pulseaudio /dev/snd/controlC1: heiko 2688 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175 InstallationDate: Installed on 2015-12-03 (383 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115 MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.157.6 RfKill: Tags: serena Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo
[Kernel-packages] [Bug 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install
1.60 packages needs to be pushed from Proposed (universe) to Release (universe) in the repository of Ubuntu 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651846 Title: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install Status in linux package in Ubuntu: Confirmed Bug description: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: Installed: 1.59-6 Candidate: 1.59-6 Version table: *** 1.59-6 500 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ wnd->net_dev->trans_start = jiffies; ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: *** [_module_/var/lib/dkms/ndiswrapper/1.59/build] Error 2 make: Leaving directory '/usr/src/linux-headers-4.8.0-30-generic' --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: heiko 2688 F...m pulseaudio /dev/snd/controlC0: heiko 2688 F pulseaudio /dev/snd/controlC2: heiko 2688 F pulseaudio /dev/snd/controlC1: heiko 2688 F pulseaudio CurrentDesktop: MATE DistroRelease: Linux 18.1 HibernationDevice: RESUME=UUID=8102f808-7e26-489e-949b-978c20bc8175 InstallationDate: Installed on 2015-12-03 (383 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20151115 MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-30-generic root=/dev/mapper/lm13-root ro usbhid.quirks=0x058F:0x9410:0x2000 ipv6.disable=1 vga=893 modprobe.blacklist=nouveau quiet intel_iommu=on iommu=pt ProcVersionSignature: Ubuntu 4.8.0-30.32~16.04.1-generic 4.8.6 RelatedPackageVersions: linux-restricted-modules-4.8.0-30-generic N/A linux-backports-modules-4.8.0-30-generic N/A linux-firmware1.157.6 RfKill: Tags: serena Uname: Linux 4.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/25/2014 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1651846] Re: ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) doesn't compile/install
This Bug Also affects me! Also it is not a Linux Mint Bug. Same happens in the standard Ubuntu 16.04, too Look at https://people.canonical.com/~ubuntu-archive/pending-sru.html -> changelog bug #1625089 and https://launchpad.net/ubuntu/+source/ndiswrapper/ and https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/1625089 ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Description changed: Description: Linux Mint 18.1 Serena Ubuntu 16.04 Package: ndiswrapper: - Installed: 1.59-6 - Candidate: 1.59-6 - Version table: - *** 1.59-6 500 - 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1.59-6 + Candidate: 1.59-6 + Version table: + *** 1.59-6 500 + 500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages + 100 /var/lib/dpkg/status When installing kernel 4.8.0-30-generic on Linux Mint 18.1 (Ubuntu 16.04), ndiswrapper returns the following error: "Building initial module for 4.8.0-30-generic Error! Bad return status for module build on kernel: 4.8.0-30-generic (x86_64) Consult /var/lib/dkms/ndiswrapper/1.59/build/make.log for more information." The same happens when re-installing via Synaptic. Synaptic reports "Changes applied" (doesn't report failure), but in fact there is no ndiswrapper module in /var/lib/dkms/ndiswrapper. Here the content of /var/lib/dkms/ndiswrapper/1.59/build/make.log: DKMS make.log for ndiswrapper-1.59 for kernel 4.8.0-30-generic (x86_64) ד' דצמ 21 12:20:38 IST 2016 make: Entering directory '/usr/src/linux-headers-4.8.0-30-generic' - LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h - MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h - MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o - CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o + LD /var/lib/dkms/ndiswrapper/1.59/build/built-in.o + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/crt_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/hal_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ndis_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/rtl_exports.h + MKEXPORT /var/lib/dkms/ndiswrapper/1.59/build/usb_exports.h + MKSTUBS /var/lib/dkms/ndiswrapper/1.59/build/win2lin_stubs.h + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/crt.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/hal.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/iw_ndis.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/loader.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ndis.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/ntoskernel_io.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pe_linker.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/pnp.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/proc.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/rtl.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapmem.o + CC [M] /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c: In function ‘tx_worker’: /var/lib/dkms/ndiswrapper/1.59/build/wrapndis.c:707:16: error: ‘struct net_device’ has no member named ‘trans_start’ - wnd->net_dev->trans_start = jiffies; - ^ + wnd->net_dev->trans_start = jiffies; + ^ scripts/Makefile.build:289: recipe for target '/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o' failed make[1]: *** [/var/lib/dkms/ndiswrapper/1.59/build/wrapndis.o] Error 1 Makefile:1489: recipe for target '_module_/var/lib/dkms/ndiswrapper/1.59/build' failed make: ***
[Kernel-packages] [Bug 1673350] Re: dm-queue-length module is not included in installer/initramfs
This bug was fixed in the package multipath-tools - 0.6.4-3ubuntu2 --- multipath-tools (0.6.4-3ubuntu2) zesty; urgency=medium * debian/initramfs/hooks: - Remove old dm-emc module; it hasn't been in kernel since 2.6.27. - Add dm-queue-length: users may want to change from the default selector and should be able to do so. (LP: #1673350) * debian/patches/path_selector.patch, debian/patches/series: remove path_selector.patch to get back to the "right" default selector of service-time, which has been included in the kernel module packages for a while now and has better throughput than round-robin. It's also the default upstream. (LP: #1634161) -- Mathieu Trudel-LapierreFri, 17 Mar 2017 09:37:36 -0400 ** Changed in: multipath-tools (Ubuntu) Status: Triaged => 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/1673350 Title: dm-queue-length module is not included in installer/initramfs Status in hw-detect package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Triaged Status in linux package in Ubuntu: Fix Committed Status in multipath-tools package in Ubuntu: Fix Released Status in hw-detect source package in Xenial: New Status in initramfs-tools source package in Xenial: New Status in linux source package in Xenial: In Progress Status in multipath-tools source package in Xenial: New Status in hw-detect source package in Yakkety: New Status in initramfs-tools source package in Yakkety: New Status in linux source package in Yakkety: New Status in multipath-tools source package in Yakkety: New Bug description: [Impact] Multipath users using EMC XtremIO storage as boot device or at install time may run into this issue. With the module unavailable the device is more often than not unavailable. Any users changing path selector to 'queue-length' with other storage devices may also be affected. [Test case] 1) Install on multipath system using EMC XtremIO storage / OR: a) Start d-i install on qemu with multipath enabled b) exit to d-i menu c) modify /etc/multipath.conf to define path selector as 'queue-length' for the local qemu device. d) restart multipathd if necessary. 2) Try to complete the install, setting up storage as multipath and using the multipath device as boot disk. 3) Reboot to disk. In a success case, the install should complete successfully without requiring manual configuration from the user to support the multipath storage past the normal detection of multipath and partitioning. In a failure case, the install may not complete, or rebooting may fail or lead to a system booted on a single path of the multipath device (ie. / on /dev/sda2 rather than /dev/mpatha2). [Regression Potential] The inclusion of a new multipath path selector driver should not cause any regressions, but any failure to detect, configure or boot on multipath devices following this change on XtremIO hardware or otherwise would constitute a regression potentially caused by this change. --- ---Problem Description--- dm-queue-length module is not included in installer/initramfs On Ubuntu, multipath devices using the 'queue-length' path selector are non-functional on both the installer and initramfs environments; because the 'dm-queue-length' kernel module is not included in them. The multipath-modules.udeb (src:linux) does not include it in the installer, nor multipath-tools-boot (src:multipath-tools) installs it in the initramfs. One example is the EMC XtremIO storage, which has 'queue-length' defined as its path selector in the default multipath configuration, at least on 16.04. Other products may be affected if they are manually configured to use that path selector (e.g., via /etc/multipath.conf), and the mere switch of that might render the system _unbootable_ if booting from multipath, since the initramfs is affected. More recently this and another storage changed default path selectors out of 'queue-length', however, it's virtually possible for any storage system to be affected, with the described manual configuration change. So, this change is also desired on for the next stable release, 17.04, and later. Patches are provided for 16.04 and 17.04. Error logs in LP comment #6. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hw-detect/+bug/1673350/+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