[Kernel-packages] [Bug 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways
** Description changed: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == - Dell IoT 300x gateways support CAN peripherals over USB. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. + Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. -- 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1774394] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1774394 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774394/+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 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with X-LTS kernel
Could be found on X kernel as well. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - fcntl35 / fcntl35_64 in LTP syscall test failed with X-LTS kernel + fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774394/+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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
I have exactly the same issue with an MSI MS-1492 (GE40). I'll run the command and change the status. -- 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
Ah... while submitting the info I figured out it is apparently the idea to create a new bug and mark it as duplicate... Will do so. -- 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1774583] 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Confirmed Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583/+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 1774583] Re: Resuming does not work with kernel 3.13.0-149-generic
Probably related to / duplicate op #1774150 -- 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Confirmed Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583/+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 1774583] [NEW] Resuming does not work with kernel 3.13.0-149-generic
Public bug reported: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug staging trusty -- 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Confirmed Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bug
[Kernel-packages] [Bug 1774150] Re: 3.13.0-149-generic: suspend/resume issue on 14.04
New bugreport created: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583 -- 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/1774150 Title: 3.13.0-149-generic: suspend/resume issue on 14.04 Status in linux package in Ubuntu: Incomplete Bug description: On Ubuntu 14.04.5 LTS, the most recent kernel update to 3.13.0-149-generic means that my laptop (Acer Aspire V5) does not resume once suspended - all I get is a blank screen, unresponsive to keypresses, and I need to reboot. The 144 kernel is OK, and this question: https://askubuntu.com/questions/1040169/experiencing-suspend-resume-problem-after-latest-kernel-update-ubuntu-14-04 suggests that 147 is OK too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
https://extensions.gnome.org/extension/1222/oled-dimmer/ Found a smoother work around. Including keys it works out of the box. Best Regards Marvin Rueppel Mobile: +41 (0) 79 339 1121 Email : mruep...@gmail.com On Thu, May 31, 2018 at 4:15 PM, Marvin Rueppel wrote: > Ok. Here the result: > > > assuming you only need the log files. > > Executed as stated: > >- > >ls /sys/class/backlight > backlight >- > >grep -r . /proc/acpi > acpi >- > >sudo acpidump -o acpidump.txt >- > >acpixtract acpidump.txt >- Please note this must be done after the prior command, as it uses > the newly created acpidump.txt, in order to produce the files to attach > DSDT.dat, SSDT1.dat, SSDT2.dat, and SSDT3.dat. >- > >iasl -d DSDT.dat >- Please note this must be done after the prior command, as it uses > the newly created DSDT.dat to create the file to attach DSDT.dsl. >- > >sudo fwts > fwts >- > >sudo fwts method > fwts_method >- > >sudo dmidecode > dmidecode.log > > > > > > > > > > On Mon, May 28, 2018 at 9:43 PM, Christopher M. Penalver < > christopher.m.penal...@gmail.com> wrote: > >> marvin: >> >> 1) Regarding the scaling and mouse issues, these are outside the scope of >> this report. Hence, feel free to file a separate report about each one by >> ensuring you have the package xdiagnose installed, and that you click the >> Yes button for attaching additional debugging information via a terminal: >> ubuntu-bug xorg >> >> 2) Regarding the scope of this report, could you please provide the >> missing information from >> https://wiki.ubuntu.com/Kernel/Debugging/Backlight? >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1768208 >> >> Title: >> [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness >> >> Status in linux package in Ubuntu: >> Incomplete >> >> Bug description: >> The screen brightness cannot be changed. >> >> In 16.04, I could change the brightness via: >> xrandr --output eDP-1 --brightness 0.7 >> >> WORKAROUND: Execute at a terminal: >> xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 >> >> --- >> ApportVersion: 2.20.9-0ubuntu7 >> Architecture: amd64 >> AudioDevicesInUse: >>USERPID ACCESS COMMAND >>/dev/snd/controlC0: marvin 1768 F pulseaudio >> CurrentDesktop: ubuntu:GNOME >> DistroRelease: Ubuntu 18.04 >> HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 >> MachineType: LENOVO 20FRS2M600 >> Package: linux (not installed) >> ProcFB: 0 inteldrmfb >> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 >> ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 >> RelatedPackageVersions: >>linux-restricted-modules-4.15.0-20-generic N/A >>linux-backports-modules-4.15.0-20-generic N/A >>linux-firmware 1.173 >> Tags: bionic >> Uname: Linux 4.15.0-20-generic x86_64 >> UpgradeStatus: No upgrade log present (probably fresh install) >> UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo >> _MarkForUpload: True >> dmi.bios.date: 06/23/2016 >> dmi.bios.vendor: LENOVO >> dmi.bios.version: N1FET41W (1.15 ) >> dmi.board.asset.tag: Not Available >> dmi.board.name: 20FRS2M600 >> dmi.board.vendor: LENOVO >> dmi.board.version: Not Defined >> dmi.chassis.asset.tag: No Asset Information >> dmi.chassis.type: 10 >> dmi.chassis.vendor: LENOVO >> dmi.chassis.version: None >> dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15 >> ):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:r >> vnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: >> dmi.product.family: ThinkPad X1 Yoga 1st >> dmi.product.name: 20FRS2M600 >> dmi.product.version: ThinkPad X1 Yoga 1st >> dmi.sys.vendor: LENOVO >> >> To manage notifications about this bug go to: >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208 >> /+subscriptions >> > > -- 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/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/d
[Kernel-packages] [Bug 1774589] [NEW] System freeze
Public bug reported: System freeze ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-43-generic. ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohammad881 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf371 irq 30' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa5019,0013 HDA:80862806,80860101,0010' Controls : 34 Simple ctrls : 11 CurrentDesktop: LXDE Date: Fri Jun 1 10:29:53 2018 HibernationDevice: RESUME=UUID=c49322e5-423f-4d23-b603-862b40c1fa3f MachineType: LENOVO 6885DSG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=60cc0542-145d-4cbe-ab3a-664740f38105 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET40WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DSG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET40WW(1.21):bd01/17/2014:svnLENOVO:pn6885DSG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DSG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E531 dmi.product.name: 6885DSG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug artful i386 -- 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/1774589 Title: System freeze Status in linux package in Ubuntu: New Bug description: System freeze ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-43-generic. ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohammad881 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf371 irq 30' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa5019,0013 HDA:80862806,80860101,0010' Controls : 34 Simple ctrls : 11 CurrentDesktop: LXDE Date: Fri Jun 1 10:29:53 2018 HibernationDevice: RESUME=UUID=c49322e5-423f-4d23-b603-862b40c1fa3f MachineType: LENOVO 6885DSG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=60cc0542-145d-4cbe-ab3a-664740f38105 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET40WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DSG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET40WW(1.21):bd01/17/2014:svnLENOVO:pn6885DSG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DSG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E531 dmi.product.name: 6885DSG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774589/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1774595] [NEW] getxattr04 in LTP syscall test failed with X/X-LTS kernel
Public bug reported: The "getxattr04" from the LTP syscall tests has failed on a testing node with Xenial kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "getxattr04" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=getxattr04 stime=1527682633 cmdline="getxattr04" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute Summary: passed 0 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=2 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jun 1 03:06:15 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug package-from-proposed s390x third-party-packages 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/1774595 Title: getxattr04 in LTP syscall test failed with X/X-LTS kernel Status in linux package in Ubuntu: Confirmed Bug description: The "getxattr04" from the LTP syscall tests has failed on a testing node with Xenial kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "getxattr04" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=getxattr04 stime=1527682633 cmdline="getxattr04" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute Summary: passed 0 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=2 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jun 1 03:06:15 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine:
[Kernel-packages] [Bug 1774595] 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/1774595 Title: getxattr04 in LTP syscall test failed with X/X-LTS kernel Status in linux package in Ubuntu: Confirmed Bug description: The "getxattr04" from the LTP syscall tests has failed on a testing node with Xenial kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "getxattr04" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=getxattr04 stime=1527682633 cmdline="getxattr04" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute Summary: passed 0 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=2 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jun 1 03:06:15 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774595/+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 1774190] Re: linux: 3.13.0-151.201 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774190 Title: linux: 3.13.0-151.201 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774190/+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 1774589] 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/1774589 Title: System freeze Status in linux package in Ubuntu: Confirmed Bug description: System freeze ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-43-generic. ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohammad881 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf371 irq 30' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa5019,0013 HDA:80862806,80860101,0010' Controls : 34 Simple ctrls : 11 CurrentDesktop: LXDE Date: Fri Jun 1 10:29:53 2018 HibernationDevice: RESUME=UUID=c49322e5-423f-4d23-b603-862b40c1fa3f MachineType: LENOVO 6885DSG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=60cc0542-145d-4cbe-ab3a-664740f38105 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET40WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DSG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET40WW(1.21):bd01/17/2014:svnLENOVO:pn6885DSG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DSG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E531 dmi.product.name: 6885DSG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774589/+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 1774126] Re: linux-oem: 4.13.0-1030.33 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774126 Title: linux-oem: 4.13.0-1030.33 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774126/+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 1774606] [NEW] [Redpine] Wifi AP does not work
Public bug reported: WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver for 4.15 kernel. Several issues were observed in Redpine driver which supports RS9113 Wifi+BT combo chip: 1. 40Mhz connection issue 2. Mode 1,13,14,4,6 change issue 3. SoftAP failure issue This bug is of tracking purposes only, please don't triage. ** Affects: linux-oem (Ubuntu) Importance: High Status: Confirmed ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed ** Changed in: linux-oem (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774606 Title: [Redpine] Wifi AP does not work Status in linux-oem package in Ubuntu: Confirmed Bug description: WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver for 4.15 kernel. Several issues were observed in Redpine driver which supports RS9113 Wifi+BT combo chip: 1. 40Mhz connection issue 2. Mode 1,13,14,4,6 change issue 3. SoftAP failure issue This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem/+bug/1774606/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/snap-release-to-beta Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Friday, 01. June 2018 09:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Friday, 01. June 2018 09:32 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Confirmed Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: Confirmed Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1774606] Re: [Redpine] Wifi AP does not work
** Tags added: originate-from-1774299 plano -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774606 Title: [Redpine] Wifi AP does not work Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Bug description: WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver for 4.15 kernel. Several issues were observed in Redpine driver which supports RS9113 Wifi+BT combo chip: 1. 40Mhz connection issue 2. Mode 1,13,14,4,6 change issue 3. SoftAP failure issue This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774606/+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 1753941] Re: ubuntu_bpf_jit test failed on Bionic s390x systems
** Also affects: linux (Ubuntu Bionic) 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/1753941 Title: ubuntu_bpf_jit test failed on Bionic s390x systems Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: New Bug description: Not sure if this is related to bug 1751234 (error on AMD64 system is different) The ubuntu_bpf_jit test will fail with the following 5 test cases: test_bpf: #292 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #293 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #298 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #299 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 test_bpf: #300 BPF_MAXINSNS: jump around ld_abs FAIL to select_runtime err=-524 test_bpf: Summary: 337 PASSED, 5 FAILED, [329/329 JIT'ed] And modprobe error can be found in the report as well: modprobe: ERROR: could not insert 'test_bpf': Invalid argument Issue can be reproduce on both zVM and Ubuntu on LPAR s390x systems. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-11-generic 4.15.0-11.12 ProcVersionSignature: Ubuntu 4.15.0-11.12-generic 4.15.5 Uname: Linux 4.15.0-11-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed Mar 7 08:13:51 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=/dev/mapper/kl02vg01-root crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-11-generic N/A linux-backports-modules-4.15.0-11-generic N/A linux-firmware 1.172 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1753941/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Sorry, how do I install these kernels? They are conflicting with default versions (bionic) and dpkg refuses to install them. ** Bug watch added: Linux Kernel Bug Tracker #199855 https://bugzilla.kernel.org/show_bug.cgi?id=199855 -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Btw, there is another hardware issue with the laptop I got here, which is caused by the ideapad_laptop module. I have also prepared a patch for that: https://bugzilla.kernel.org/show_bug.cgi?id=199855. Could that also be included before being in the official kernel sources? Should I open a new issue for that? -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Ok, got the kernel installed and the touchpad is working as expected. -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1773906] Re: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick
In general, it is hard to test modern kernels on artful because of the header dependence on libssl1.1 (is it really a hard requirement?) In any case, the fact that 2.16 is OK makes me hope that on the upgrade to bionic, the issue will automatically be over. -- 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/1773906 Title: Upgraded artful kernel oopses with null pointer dereference on pkt_setup_dev on insertion of mobile usb stick Status in linux package in Ubuntu: Incomplete Bug description: On insertion of a Huawei E173 mobile internet USB stick the artful kernel now oopses: BUG: unable to handle kernel NULL pointer dereference at 03d0 [ 633.710837] IP: pkt_setup_dev+0x2af/0x650 [pktcdvd] Issue seems to be related to the setup of the cdrom-like device hosted on the stick together with the UMTS modem. May possibly be due to some race as the usb stick configuration keeps changing until the device is properly switched to operate as a modem. Some of the times, UMTS modem remains detected notwithstanding the issue. After the issue, the system has problems in shutting down, though. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-generic 4.13.0.43.46 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: callegar 2654 F pulseaudio /dev/snd/controlC1: callegar 2654 F pulseaudio CurrentDesktop: KDE Date: Tue May 29 08:27:52 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=c7dd5aac-abad-4cd0-9cac-552d49960853 InstallationDate: Installed on 2013-12-12 (1628 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Notebook W740SU ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/zagar_ssd--vg-root ro quiet splash resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-26 (214 days ago) dmi.bios.date: 10/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: Tag 12345 dmi.board.name: W740SU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: W740SU dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773906/+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 1720930] Re: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)
** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/1720930 Title: wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22) Status in Linux: Unknown Status in linux package in Ubuntu: In Progress Status in plymouth package in Ubuntu: Invalid Bug description: ===SRU Justification=== [Impact] Message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)" showed when the system shutdown. [Test] Users confirmed the patch fixes their issue. [Regression Potential] Low. It's in mainline Linux, limited to iwlwifi, trivial change. Sara Sharon (1): iwlwifi: mvm: fix "failed to remove key" message ==Original Bug Report=== When running artful on a new Zenbook Pro (uses Intel Wireless 8265), I get a hung shutdown with the message "wlp3s0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-22)". The kernel is also trying to load firmware versions that do not exist on the system i.e. versions 33 then 32 of the firmware. It then seems to load version 31 of the firmware. Wireless features seem to work normally. The issues are just at shutdown time. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dylan 1621 F pulseaudio CurrentDesktop: GNOME Date: Tue Oct 3 06:12:13 2017 HibernationDevice: RESUME=UUID=2b6908b4-d463-4170-9be5-556145c71a0e InstallationDate: Installed on 2017-10-02 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:5755 IMC Networks Bus 001 Device 004: ID 04f3:0903 Elan Microelectronics Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX550VE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic root=UUID=aa3dfd29-caf8-4882-906e-1b31b672d2c2 ro quiet splash threadirqs acpi_osi=! acpi_osi=Linux acpi_backlight=native vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX550VE.300 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX550VE 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.:bvrUX550VE.300:bd06/05/2017:svnASUSTeKCOMPUTERINC.:pnUX550VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX550VE dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1720930/+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 1774595] Re: getxattr04 in LTP syscall test failed with X/X-LTS kernel
** Also affects: ubuntu-kernel-tests 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/1774595 Title: getxattr04 in LTP syscall test failed with X/X-LTS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: The "getxattr04" from the LTP syscall tests has failed on a testing node with Xenial kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "getxattr04" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=getxattr04 stime=1527682633 cmdline="getxattr04" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute Summary: passed 0 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=2 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jun 1 03:06:15 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774595/+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 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
** Description changed: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 + + WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/ --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO -- 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/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/ --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1774571] Re: sigq test from stress-ng will get stuck with Artful kernel
Fixed by Colin: https://github.com/ColinIanKing/stress-ng/commit/481c448adf1b928b99b8221d6edba8ef5ff437f0 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Colin Ian King (colin-king) -- 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/1774571 Title: sigq test from stress-ng will get stuck with Artful kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Committed Bug description: This issue can be spotted on s390x, ARM64 and AMD64 Artful kernel. 10:02:39 DEBUG| [stdout] sigpending STARTING 10:02:44 DEBUG| [stdout] sigpending RETURNED 0 10:02:44 DEBUG| [stdout] sigpending PASSED 10:02:44 DEBUG| [stdout] sigpipe STARTING 10:02:49 DEBUG| [stdout] sigpipe RETURNED 0 10:02:49 DEBUG| [stdout] sigpipe PASSED 10:02:49 DEBUG| [stdout] sigq STARTING ... This is the last entry related to stress-ng in syslog of a s390x node: May 31 10:46:39 s2lp6g004 stress-ng: system: 's2lp6g004' Linux 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:21:19 UTC 2018 s390x May 31 10:46:39 s2lp6g004 stress-ng: memory (MB): total 1805.91, free 1409.97, shared 6.06, buffer 134.56, swap 2001.63, free swap 1890.19 May 31 10:46:39 s2lp6g004 stress-ng: info: [20125] dispatching hogs: 4 sigq No more stress-ng related message after this. ubuntu@s2lp6g004:/tmp$ cat stress-9234.log stress-ng: debug: [20125] 2 processors online, 2 processors configured stress-ng: info: [20125] dispatching hogs: 4 sigq stress-ng: debug: [20125] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [20125] cache allocate: default cache size: 2048K stress-ng: debug: [20125] starting stressors stress-ng: debug: [20126] stress-ng-sigq: started [20126] (instance 0) stress-ng: debug: [20125] 4 stressors spawned stress-ng: debug: [20129] stress-ng-sigq: started [20129] (instance 3) stress-ng: debug: [20128] stress-ng-sigq: started [20128] (instance 2) stress-ng: debug: [20127] stress-ng-sigq: started [20127] (instance 1) stress-ng: debug: [20126] stress-ng-sigq: parent sent termination notice stress-ng: debug: [20130] stress-ng-sigq: child got termination notice ubuntu@s2lp6g004:/tmp$ ps aux | grep stress-ng root 5948 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7654 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7728 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7740 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 20125 0.0 0.2 13612 5008 ?SL May31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20126 1.0 0.1 13612 1852 ?SMay31 12:03 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20127 1.0 0.1 13612 1852 ?SMay31 12:11 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20128 1.0 0.1 13612 1852 ?SMay31 12:04 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20129 1.0 0.1 13612 1852 ?SMay31 12:06 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20131 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20132 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20133 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-45-generic 4.13.0-45.50 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
[Kernel-packages] [Bug 1774571] Re: sigq test from stress-ng will get stuck with Artful kernel
** Also affects: stress-ng (Ubuntu) Importance: Undecided Status: New ** Changed in: stress-ng (Ubuntu) Status: New => Fix Released ** Changed in: stress-ng (Ubuntu) Status: Fix Released => Fix Committed ** Changed in: stress-ng (Ubuntu) Assignee: (unassigned) => Colin Ian King (colin-king) ** Changed in: stress-ng (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774571 Title: sigq test from stress-ng will get stuck with Artful kernel Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in stress-ng package in Ubuntu: Fix Committed Bug description: This issue can be spotted on s390x, ARM64 and AMD64 Artful kernel. 10:02:39 DEBUG| [stdout] sigpending STARTING 10:02:44 DEBUG| [stdout] sigpending RETURNED 0 10:02:44 DEBUG| [stdout] sigpending PASSED 10:02:44 DEBUG| [stdout] sigpipe STARTING 10:02:49 DEBUG| [stdout] sigpipe RETURNED 0 10:02:49 DEBUG| [stdout] sigpipe PASSED 10:02:49 DEBUG| [stdout] sigq STARTING ... This is the last entry related to stress-ng in syslog of a s390x node: May 31 10:46:39 s2lp6g004 stress-ng: system: 's2lp6g004' Linux 4.13.0-45-generic #50-Ubuntu SMP Wed May 30 08:21:19 UTC 2018 s390x May 31 10:46:39 s2lp6g004 stress-ng: memory (MB): total 1805.91, free 1409.97, shared 6.06, buffer 134.56, swap 2001.63, free swap 1890.19 May 31 10:46:39 s2lp6g004 stress-ng: info: [20125] dispatching hogs: 4 sigq No more stress-ng related message after this. ubuntu@s2lp6g004:/tmp$ cat stress-9234.log stress-ng: debug: [20125] 2 processors online, 2 processors configured stress-ng: info: [20125] dispatching hogs: 4 sigq stress-ng: debug: [20125] cache allocate: reducing cache level from L3 (too high) to L2 stress-ng: debug: [20125] cache allocate: default cache size: 2048K stress-ng: debug: [20125] starting stressors stress-ng: debug: [20126] stress-ng-sigq: started [20126] (instance 0) stress-ng: debug: [20125] 4 stressors spawned stress-ng: debug: [20129] stress-ng-sigq: started [20129] (instance 3) stress-ng: debug: [20128] stress-ng-sigq: started [20128] (instance 2) stress-ng: debug: [20127] stress-ng-sigq: started [20127] (instance 1) stress-ng: debug: [20126] stress-ng-sigq: parent sent termination notice stress-ng: debug: [20130] stress-ng-sigq: child got termination notice ubuntu@s2lp6g004:/tmp$ ps aux | grep stress-ng root 5948 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7654 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7728 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 7740 0.0 0.0 11456 712 ?SMay31 0:00 ./stress-ng -v -t 5 --enosys 4 --ignite-cpu --syslog --verbose --verify --oomable root 20125 0.0 0.2 13612 5008 ?SL May31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20126 1.0 0.1 13612 1852 ?SMay31 12:03 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20127 1.0 0.1 13612 1852 ?SMay31 12:11 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20128 1.0 0.1 13612 1852 ?SMay31 12:04 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20129 1.0 0.1 13612 1852 ?SMay31 12:06 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20131 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20132 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable root 20133 0.0 0.0 13612 312 ?SMay31 0:00 ./stress-ng -v -t 5 --sigq 4 --ignite-cpu --syslog --verbose --verify --oomable ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-45-generic 4.13.0-45.50 ProcVersionSignature: Ubuntu 4.13.0-45.50-generic 4.13.16 Uname: Linux 4.13.0-45-generic s390x NonfreeKernelModules: zfs zunicode zavl zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.9 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error:
[Kernel-packages] [Bug 1774394] Re: fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel
** Also affects: ubuntu-kernel-tests 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/1774394 Title: fcntl35 / fcntl35_64 in LTP syscall test failed with X/X-LTS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-lts-xenial package in Ubuntu: New Bug description: The "fcntl35" and "fcntl35_64" from the LTP syscall tests have failed on a testing node with X-LTS i386 kernel installed (they were not tested on amd64/arm64 because the test was not ready when the SRU starts). <>> tag=fcntl35 stime=1527764565 cmdline="fcntl35" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> <<>> tag=fcntl35_64 stime=1527764565 cmdline="fcntl35_64" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s fcntl35.c:98: FAIL: an unprivileged user init the capacity of a pipe to 65536 unexpectedly, expected 4096 fcntl35.c:101: PASS: a privileged user init the capacity of a pipe to 65536 successfully Summary: passed 1 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154~14.04.1 ProcVersionSignature: User Name 4.4.0-128.154~14.04.1-generic 4.4.131 Uname: Linux 4.4.0-128-generic i686 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: i386 Date: Thu May 31 11:05:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774394/+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 1765366] Re: Unable to build kvm-unit-test on i386 system
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Released => Invalid ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- 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/1765366 Title: Unable to build kvm-unit-test on i386 system Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: When trying to build the kvm-unit-test on i386 node, it will fail with: gcc -m32 -O1 -g -MMD -MF lib/x86/.usermode.d -Wall -Wwrite-strings -Wclobbered -Wempty-body -Wuninitialized -Wignored-qualifiers -Wunused-but-set-parameter -Werror -fno-omit-frame-pointer -Wno-frame-address -fno-pic -no-pie -Wmissing-parameter-type -Wold-style-declaration -Woverride-init -ffreestanding -I /home/ubuntu/autotest/client/tmp/ubuntu_kvm_unit_tests/src/kvm-unit-tests/lib -I lib -c -o lib/x86/usermode.o lib/x86/usermode.c : recipe for target 'lib/x86/usermode.o' failed stderr: lib/x86/usermode.c: In function ‘run_in_user’: lib/x86/usermode.c:49:2: error: inconsistent operand constraints in an ‘asm’ asm volatile ( ^~~ make: *** [lib/x86/usermode.o] Error 1 Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. ./configure 3. make This is a test suite issue, not a regression, as it can be reproduced on 4.13.0-38 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-38-generic 4.13.0-38.43 ProcVersionSignature: User Name 4.13.0-38.43-generic 4.13.16 Uname: Linux 4.13.0-38-generic i686 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 19 09:39 seq crw-rw 1 root audio 116, 33 Apr 19 09:39 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.7-0ubuntu3.8 Architecture: i386 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Thu Apr 19 10:12:48 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0424:2514 Standard Microsystems Corp. USB 2.0 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: Dell Inc. PowerEdge R310 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic root=UUID=7b91a2b8-2e02-407e-a51d-766f6d969020 ro RelatedPackageVersions: linux-restricted-modules-4.13.0-38-generic N/A linux-backports-modules-4.13.0-38-generic N/A linux-firmware 1.169.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.2 dmi.board.name: 05XKKK dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.2:bd08/17/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA05:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R310 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1765366/+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 1765279] Re: Unable to build libhugetlbfs test on 4.15 Bionic
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Fix Released => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Released => Invalid ** Changed in: linux-kvm (Ubuntu) Status: Fix Released => Invalid ** Changed in: linux-kvm (Ubuntu Bionic) Status: Fix Released => Invalid ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- 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/1765279 Title: Unable to build libhugetlbfs test on 4.15 Bionic Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-kvm source package in Bionic: Invalid Bug description: When trying to build the libhugetlbfs test Bionic, it will fail with: CC32 obj32/linkhuge_nofd.o LD32 (hugelink test) obj32/linkhuge_nofd CC32 obj32/linkshare.o LD32 (hugelink test) obj32/linkshare LD32 (xB test) obj32/xB.linkhuge /usr/bin/x86_64-linux-gnu-ld: unrecognized option '--hugetlbfs-link=B' /usr/bin/x86_64-linux-gnu-ld: use the --help option for usage information collect2: error: ld returned 1 exit status Makefile:227: recipe for target 'obj32/xB.linkhuge' failed make[1]: *** [obj32/xB.linkhuge] Error 1 Makefile:242: recipe for target 'tests/all' failed make: *** [tests/all] Error 2 Steps: 1. git clone --depth=1 -b next https://github.com/libhugetlbfs/libhugetlbfs.git 2. cd libhugetlbfs 3. make ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1003-kvm 4.15.0-1003.3 ProcVersionSignature: User Name 4.15.0-1003.3-kvm 4.15.10 Uname: Linux 4.15.0-1003-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 04:44:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1765279/+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 1751213] Re: kernel security test report that the lttng_probe_writeback module is tainted on Bionic s390x
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Fix Released => Invalid ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1751213 Title: kernel security test report that the lttng_probe_writeback module is tainted on Bionic s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This issue was only spotted on Bionic s390x instances. FAIL: test_140_kernel_modules_not_tainted (__main__.KernelSecurityTest) kernel modules are not marked with a taint flag (especially 'E' for TAINT_UNSIGNED_MODULE) -- Traceback (most recent call last): File "./test-kernel-security.py", line 1727, in test_140_kernel_modules_not_tainted self.fail('Module \'%s\' is tainted: %s' % (fields[0], last_field)) AssertionError: Module 'lttng_probe_writeback' is tainted: (OE) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-10-generic 4.15.0-10.11 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.8-0ubuntu10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Feb 23 07:43:00 2018 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.171 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1751213/+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 1712038] Re: ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64
** Also affects: ubuntu-kernel-tests 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/1712038 Title: ubuntu_qrt_kernel_security test_060_nx failed on Trusty ARM64 Status in QA Regression Testing: In Progress Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: From the error output, this bug was marked as Failed, instead of being skipped: NX bit is working ... (skipped: ARM64 older than 4.4 has READ_IMPLIES_EXEC personality set) FAIL FAIL: test_060_nx (__main__.KernelSecurityTest) NX bit is working -- Traceback (most recent call last): File "./test-kernel-security.py", line 460, in test_060_nx self.assertShellExitEquals(expected, ["./nx-test", "data"]) File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/testlib.py", line 1134, in assertShellExitEquals self.assertEqual(expected, rc, msg + result + report) AssertionError: Got exit code -11, expected 0 Command: './nx-test', 'data' Output: rodata:0x4010c0 data: 0x4120a8 bss: 0x4220c8 brk: 0x20de1010 rw:0x7f833a1000 rwx: 0x7f833a stack: 0x7fdd19bfd8 Dump of /proc/self/maps: 0040-00402000 r-xp 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test 00411000-00412000 r--p 1000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test 00412000-00413000 rw-p 2000 08:02 10096524 /home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_security/src/qa-regression-testing/scripts/kernel-security/nx/nx-test 00413000-00423000 rw-p 00:00 0 20de1000-20e03000 rw-p 00:00 0 [heap] 7f8320c000-7f8322c000 rw-p 00:00 0 7f8322c000-7f8335f000 r-xp 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so 7f8335f000-7f8336f000 ---p 00133000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so 7f8336f000-7f83373000 r--p 00133000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so 7f83373000-7f83375000 rw-p 00137000 08:02 4718846 /lib/aarch64-linux-gnu/libc-2.19.so 7f83375000-7f83379000 rw-p 00:00 0 7f83379000-7f83395000 r-xp 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so 7f83399000-7f8339b000 rw-p 00:00 0 7f833a-7f833a1000 rwxp 00:00 0 7f833a1000-7f833a2000 rw-p 00:00 0 7f833a2000-7f833a4000 r-xp 00:00 0 [vdso] 7f833a4000-7f833a5000 r--p 0001b000 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so 7f833a5000-7f833a7000 rw-p 0001c000 08:02 4718835 /lib/aarch64-linux-gnu/ld-2.19.so 7fdd17c000-7fdd19d000 rw-p 00:00 0 [stack] Attempting to execute function at 0x4120a8 If this program seg-faults, the region was enforced as non-executable... Compared to other skipped test, it should be marked as OK, like PR_SET_SECCOMP works ... (skipped: not available on ARM64) ok To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1712038/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
Thanks for testing. I'll submit an SRU request for the patch. I would suggest opening a new bug for the other issues you see. That way they can be tracked and fixes separately. -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1768430] Re: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- 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/1768430 Title: aio-dio-subblock-eof-read test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof-read eoftest' buffered read returned -1, should be 300 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-subblock-eof- read eoftest Exit status: 1 Duration: 0.00215792655945 stdout: buffered read returned -1, should be 300 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:21:12 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad
[Kernel-packages] [Bug 1689240] Re: scrashme failed to build on s390x
We're replacing it with LTP syscall test: http://kernel.ubuntu.com/git/ubuntu/autotest-client-tests.git/commit/?h=master-next&id=fb077e6e207fc37f9bd4cf0b0d33beaad3d80688 Trinity will take too much time and storage space for it. ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- 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/1689240 Title: scrashme failed to build on s390x Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Bug description: This test case failed to build on LPAR Ubuntu (s2lp4) Maybe we should disable it from the test suite. cc -Wall -W -Wshadow -g -O2 -o scrashme.o -c scrashme.c Makefile:13: recipe for target 'scrashme.o' failed stderr: scrashme.c: In function 'mkcall': scrashme.c:150:13: error: 'NR_SYSCALLS' undeclared (first use in this function) if (call > NR_SYSCALLS) ^~~ scrashme.c:150:13: note: each undeclared identifier is reported only once for each function it appears in scrashme.c: In function 'do_syscall': scrashme.c:258:27: error: 'NR_SYSCALLS' undeclared (first use in this function) cl = rand() / (RAND_MAX/NR_SYSCALLS); ^~~ scrashme.c: In function 'syscall_list': scrashme.c:293:15: error: 'NR_SYSCALLS' undeclared (first use in this function) for (i=0; i<=NR_SYSCALLS; i++) { ^~~ scrashme.c: In function 'parse_args': scrashme.c:337:18: error: 'NR_SYSCALLS' undeclared (first use in this function) for (i=0; i<=NR_SYSCALLS; i++) { ^~~ scrashme.c:371:13: error: 'KERNEL_ADDR' undeclared (first use in this function) regval = KERNEL_ADDR; ^~~ scrashme.c: In function 'run_mode': scrashme.c:522:15: error: 'NR_SYSCALLS' undeclared (first use in this function) if (rep > NR_SYSCALLS) { ^~~ scrashme.c: In function 'main': scrashme.c:588:13: error: 'syscalls_i386' undeclared (first use in this function) syscalls = syscalls_i386; ^ scrashme.c: In function 'run_setup': scrashme.c:467:2: warning: ignoring return value of 'seteuid', declared with attribute warn_unused_result [-Wunused-result] seteuid(65536); ^~ scrashme.c:468:2: warning: ignoring return value of 'seteuid', declared with attribute warn_unused_result [-Wunused-result] seteuid(65536); ^~ scrashme.c:469:2: warning: ignoring return value of 'setgid', declared with attribute warn_unused_result [-Wunused-result] (void)setgid(65536); ^~~ scrashme.c:470:2: warning: ignoring return value of 'seteuid', declared with attribute warn_unused_result [-Wunused-result] seteuid(65536); ^~ scrashme.c:486:2: warning: ignoring return value of 'chroot', declared with attribute warn_unused_result [-Wunused-result] chroot("tmp"); ^ make: *** [scrashme.o] Error 1 ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: linux-image-4.8.0-52-generic 4.8.0-52.55 ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17 Uname: Linux 4.8.0-52-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.3-0ubuntu8.2 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Mon May 8 03:25:31 2017 HibernationDevice: RESUME=UUID=46fcf640-03e2-4fd5-b7d6-321d6a11ff8d IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=4a1de891-d624-42df-be09-50199aec3d11 crashkernel=196M debug BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.8.0-52-generic N/A linux-backports-modules-4.8.0-52-generic N/A linux-firmware1.161.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1689240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel
[Kernel-packages] [Bug 1768435] Re: aio-dio-extend-stat test in aio_dio_bugs failed on s390x
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- 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/1768435 Title: aio-dio-extend-stat test in aio_dio_bugs failed on s390x Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: It can be reproduced on zVM, zKVM and Ubuntu on LPAR This should not be considered as a regression, the test suite stopped on the first test in this test suite before. Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-extend-stat file Running 'apt-get install --yes --force-yes build-essential gcc' Reading package lists... Building dependency tree... Reading state information... build-essential is already the newest version (12.1ubuntu2). gcc is already the newest version (4:5.3.1-1ubuntu1). The following packages were automatically installed and are no longer required: linux-headers-4.4.0-121 linux-headers-4.4.0-121-generic linux-image-4.4.0-121-generic linux-image-extra-4.4.0-121-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Running 'which gcc' /usr/bin/gcc Dependency libaio successfully built Running 'LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file' write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/aio_dio_bugs/aio_dio_bugs.py", line 42, in run_once utils.system(var_ld_path + ' ' + cmd) File "/home/ubuntu/autotest/client/shared/utils.py", line 1232, in system verbose=verbose).exit_status File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: LD_LIBRARY_PATH=/home/ubuntu/autotest/client/deps/libaio/lib/ /home/ubuntu/autotest/client/tmp/aio_dio_bugs/src/aio-dio-extend-stat file Exit status: 1 Duration: 0.10453414917 stdout: write of 1024 bytes @0 finished, expected filesize at least 1024, but got 0 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed May 2 02:24:25 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notificati
[Kernel-packages] [Bug 1768208] Re: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness
marvin, regarding comment #30: 1) >"assuming you only need the log files." Unfortunately, this isn't the case. 2) Regarding attachments, the article requested separate attachments for each command (not combined into one). This is to help developers know what it is they are looking at, versus guessing at what was attached, trying to deduce if something was missed, or figure out why something unexpected happen. -- 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/1768208 Title: [Lenovo ThinkPad X1 Yoga 1st Gen] Can't change brightness Status in linux package in Ubuntu: Incomplete Bug description: The screen brightness cannot be changed. In 16.04, I could change the brightness via: xrandr --output eDP-1 --brightness 0.7 WORKAROUND: Execute at a terminal: xrandr --output eDP-1 --scale 1.25x1.25 --brightness 0.8 WORKAROUND: https://extensions.gnome.org/extension/1222/oled-dimmer/ --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marvin 1768 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e81e811a-12aa-465d-ba3c-77e34b171b69 MachineType: LENOVO 20FRS2M600 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/nvme0n1p1 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/23/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET41W (1.15 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FRS2M600 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET41W(1.15):bd06/23/2016:svnLENOVO:pn20FRS2M600:pvrThinkPadX1Yoga1st:rvnLENOVO:rn20FRS2M600:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Yoga 1st dmi.product.name: 20FRS2M600 dmi.product.version: ThinkPad X1 Yoga 1st dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768208/+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 1730895] Re: aio-dio-invalidate-failure test failed with event res -22 on s390x
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Importance: Undecided => Medium -- 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/1730895 Title: aio-dio-invalidate-failure test failed with event res -22 on s390x Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: New Status in linux source package in Artful: New Status in linux source package in Bionic: New Bug description: This bug is for tracking purpose, this is not a regression for current cycle as this issue exists for a long time. It can be reproduced on zVM, zKVM and Ubuntu on LPAR Steps: 1. git clone --depth=1 https://github.com/autotest/autotest-client-tests.git 2. make -C autotest-client-tests/aio_dio_bugs/src 3. sudo ./autotest-client-tests/aio_dio_bugs/src/aio-dio-invalidate-failure poo Result: event res -22 From the code itself, it's expecting a -EIO return value: if (event.res == -EIO) { printf("invalidation returned -EIO, OK\n"); exit(0); } The actual return value is -22, which I think is -EINVAL ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-100-generic 4.4.0-100.123 ProcVersionSignature: Ubuntu 4.4.0-100.123-generic 4.4.95 Uname: Linux 4.4.0-100-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Wed Nov 8 01:57:40 2017 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-100-generic N/A linux-backports-modules-4.4.0-100-generic N/A linux-firmware 1.157.13 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1730895/+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 1770334] Re: inotify08 in ubuntu_ltp test failed on 4.15 kvm
** Also affects: ubuntu-kernel-tests 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/1770334 Title: inotify08 in ubuntu_ltp test failed on 4.15 kvm Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Triaged Status in linux-kvm source package in Bionic: New Bug description: Steps to run this test: git clone https://github.com/linux-test-project/ltp.git cd ltp sudo su make autotools ./configure make make install cd /opt/ltp/testcases/bin/ sudo ./inotify08 This issue could be found in 4.15.0-1008 kvm as well Test result: <<>> tag=inotify08 stime=1525874424 cmdline="inotify08" contacts="" analysis=exit <<>> tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s inotify08.c:201: INFO: ovl/test_file ino=11995, dev=0:44 inotify08.c:212: INFO: ovl/test_file ino=11995, dev=0:44 inotify08.c:150: FAIL: didn't get event: mask=4 inotify08.c:150: FAIL: didn't get event: mask=20 inotify08.c:150: FAIL: didn't get event: mask=8 Summary: passed 0 failed 3 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> --- AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux-kvm 4.15.0.1008.8 PackageArchitecture: amd64 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1008-kvm root=UUID=41f2a2b1-0082-4a56-ad3b-9f99ca574aeb ro ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-1008-kvm N/A linux-backports-modules-4.15.0-1008-kvm N/A linux-firmware 1.173 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic uec-images Uname: Linux 4.15.0-1008-kvm x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1770334/+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 1766823] Re: zram module not found in 4.4/4.15 KVM kernel
** Also affects: ubuntu-kernel-tests 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/1766823 Title: zram module not found in 4.4/4.15 KVM kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: The ubuntu_zram_smoke_test will fail due to the lack of the zram module. 07:32:19 DEBUG| Running '/home/ubuntu/autotest/client/tests/ubuntu_zram_smoke_test/ubuntu_zram_smoke_test.sh' 07:32:19 ERROR| [stderr] modprobe: FATAL: Module zram not found in directory /lib/modules/4.15.0-1008-kvm 07:32:19 DEBUG| [stdout] FAILED: cannot load zram module 07:32:19 ERROR| Exception escaping from test: There is no zram config in the Bionic KVM kernel config file. $ grep -i zram debian.kvm/config/config.common.ubuntu $ ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 07:32:47 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766823/+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 1765698] Re: Unable to insert test_bpf module on Xenial
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1765698 Title: Unable to insert test_bpf module on Xenial Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [SRU Justification] Impact: One of the self-tests which is run by test_bpf will always fail when JIT is turned on, causing the module load to fail. Fix: Picking two patches from upstream will fix this. Testcase: sudo modprobe test_bpf Risk of regression: Minimal, this modifies only a test module, no impact on normal operation. --- With 4.4.0-119, the ubuntu_bpf_jit test will pass: [ 127.177037] test_bpf: Summary: 291 PASSED, 0 FAILED, [0/283 JIT'ed] PASSED: 291 FAILED: 0 But with 4.4.0-121, one test will fail [ 221.361834] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] PASSED: 290 FAILED: 1 stderr: modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument $ dmesg|grep test_bpf|grep FAIL [ 45.286944] test_bpf: #248 BPF_MAXINSNS: Jump, gap, jump, ... FAIL to prog_create err=-524 len=4096 [ 45.619293] test_bpf: Summary: 290 PASSED, 1 FAILED, [282/282 JIT'ed] ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-121-generic 4.4.0-121.145 ProcVersionSignature: User Name 4.4.0-121.145-generic 4.4.117 Uname: Linux 4.4.0-121-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Apr 20 12:29 seq crw-rw 1 root audio 116, 33 Apr 20 12:29 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Apr 20 12:32:59 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Intel Corporation S1200RP PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic root=UUID=b0d2ae4e-12dd-423e-acea-272ee8b2a893 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-121-generic N/A linux-backports-modules-4.4.0-121-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2015 dmi.bios.vendor: Intel Corp. dmi.bios.version: S1200RP.86B.03.02.0003.070120151022 dmi.board.asset.tag: dmi.board.name: S1200RP dmi.board.vendor: Intel Corporation dmi.board.version: G62254-407 dmi.chassis.asset.tag: dmi.chassis.type: 17 dmi.chassis.vendor: .. dmi.chassis.version: .. dmi.modalias: dmi:bvnIntelCorp.:bvrS1200RP.86B.03.02.0003.070120151022:bd07/01/2015:svnIntelCorporation:pnS1200RP:pvr:rvnIntelCorporation:rnS1200RP:rvrG62254-407:cvn..:ct17:cvr..: dmi.product.name: S1200RP dmi.product.version: dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765698/+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 1765331] Re: ar in ubuntu_ltp test failed with 4.15 KVM
** Also affects: ubuntu-kernel-tests 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/1765331 Title: ar in ubuntu_ltp test failed with 4.15 KVM Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Confirmed Bug description: ar tests in ubuntu_ltp has failed with 4.15.0-1004.4 kvm kernel <<>> tag=ar stime=1523972462 cmdline="export TCdat=$LTPROOT/testcases/bin; ar01" contacts="" analysis=exit <<>> ar01 1 TPASS: ar added new file after another (-a) ar01 2 TPASS: ar moved file correctly (-ma) ar01 3 TPASS: ar added new file before another (-b) ar01 4 TPASS: ar moved file correctly (-mb) ar01 5 TPASS: ar haven't produced output (-c) ar01 6 TPASS: ar haven't produced output (-qc) ar01 7 TPASS: ar deleted files correctly (-d) ar01 8 TPASS: ar deleted nothing (-d with empty list) ar01 9 TPASS: ar added new file before another (-i) ar01 10 TPASS: ar moved file correctly (-mi) ar01 11 TPASS: ar moved file correctly (-m) ar01 12 TPASS: ar printed file content correctly (-p) ar01 13 TPASS: ar appended file correctly (-q) ar: `u' modifier ignored since `D' is the default (see `U') ar01 14 TFAIL: ar haven't updated modified file0 (-u) ar01 14 TPASS: ar haven't updated unmodified file1 (-u) ar01 15 TPASS: ar verbose listing works (-tv) ar01 16 TPASS: ar printed extracted filenames (-xv) ar01 16 TPASS: ar extracted files correctly ar01 17 TPASS: ar printed extracted filename (-xv) ar01 17 TPASS: ar extracted file correctly Summary: passed 19 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1004-kvm 4.15.0-1004.4 ProcVersionSignature: User Name 4.15.0-1004.4-kvm 4.15.15 Uname: Linux 4.15.0-1004-kvm x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 Date: Thu Apr 19 08:24:19 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1765331/+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 1768452] Re: Unable to insert test_bpf module on Xenial s390x
** Also affects: ubuntu-kernel-tests 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/1768452 Title: Unable to insert test_bpf module on Xenial s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: After the test_bpf insert issue for Xenial was fixed in bug 1765698 But it looks like the s390x needs some extra work. $ sudo modprobe test_bpf modprobe: ERROR: could not insert 'test_bpf': Invalid argument 4 tests failed here: test_bpf: #243 BPF_MAXINSNS: Ctx heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #244 BPF_MAXINSNS: Call heavy transformations FAIL to prog_create err=-524 len=4096 test_bpf: #249 BPF_MAXINSNS: ld_abs+get_processor_id FAIL to prog_create err=-524 len=4096 test_bpf: #250 BPF_MAXINSNS: ld_abs+vlan_push/pop FAIL to select_runtime err=-524 Complete test result: https://pastebin.ubuntu.com/p/zMDwVjwF7X/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-123-generic 4.4.0-123.147 ProcVersionSignature: Ubuntu 4.4.0-123.147-generic 4.4.128 Uname: Linux 4.4.0-123-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.16 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Wed May 2 03:45:22 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-123-generic N/A linux-backports-modules-4.4.0-123-generic N/A linux-firmware 1.157.17 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1768452/+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 1684776] Re: ubuntu_qrt_kernel_security test_050_personality failed on arm64 Trusty / X-hwe kernel
** Also affects: ubuntu-kernel-tests 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/1684776 Title: ubuntu_qrt_kernel_security test_050_personality failed on arm64 Trusty / X-hwe kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: With 4.4.0-74.95~14.04.1 kernel, this test case failed on arm64 node. (This issue was reported in bug 163 as well, in this cycle, only 050, 060 failed on this kernel) == FAIL: test_050_personality (__main__.KernelSecurityTest) init missing READ_IMPLIES_EXEC -- Traceback (most recent call last): File "./test-kernel-security.py", line 398, in test_050_personality self.assertEqual(output, expected, "/proc/1/personality contains %s (expected %s)" % (output, expected)) AssertionError: /proc/1/personality contains 0040 (expected ) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1684776/+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 1760643] Re: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => In Progress -- 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/1760643 Title: test_072_config_debug_rodata in kernel security test failed with 4.4 X-kvm Status in QA Regression Testing: Fix Released Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: In Progress Status in linux source package in Xenial: Invalid Status in linux-kvm source package in Xenial: Fix Committed Bug description: == Justification == In Xenial KVM kernel, the CONFIG_DEBUG_KERNEL is enabled, security team would like to see CONFIG_DEBUG_RODATA to be enabled as well. == Test == Before enabling the config the test_072_config_debug_rodata test from qa-regression-testing will fail. After that, the test will pass. A test kernel with CONFIG_DEBUG_RODATA enabled in Xenial KVM could be found here: http://people.canonical.com/~phlin/kernel/lp-1760643/ == Fix == Enable the CONFIG_DEBUG_RODATA. Some other configs were enabled just for skipping the interaction during the compilation. == Regression Potential == Minimal. No code changes, just one config enabled without disabling any other configs. The test failed with: FAIL: test_072_config_debug_rodata (__main__.KernelSecurityTest) CONFIG_DEBUG_RODATA/CONFIG_STRICT_KERNEL_RWX enabled -- Traceback (most recent call last): File "./test-kernel-security.py", line 642, in test_072_config_debug_rodata self.assertEqual(self._test_config(option), expected) AssertionError: False != True Steps to reproduce: Deploy the node with Xenial 4.4 kernel, install linux-kvm sudo apt-get install python-minimal git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests -b master-next git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_qrt_kernel_security/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1019-kvm 4.4.0-1019.24 ProcVersionSignature: User Name 4.4.0-1019.24-kvm 4.4.98 Uname: Linux 4.4.0-1019-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Mon Apr 2 16:54:36 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1760643/+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 1763323] Re: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel
** Also affects: ubuntu-kernel-tests 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/1763323 Title: ubuntu_fan_smoke_test failed on 4.4/4.15 kvm kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux-kvm package in Ubuntu: New Status in linux source package in Xenial: Triaged Status in linux-kvm source package in Xenial: New Bug description: The "enable disable fan test" will fail with Xenial KVM kernel Error message: RTNETLINK answers: Operation not supported /usr/sbin/fanctl: ip link add ftun0 type vxlan id 16384000 dev ens4 dstport 0 local 10.246.72.56 fan-map 250.0.0.0/8:10.246.0.0/16 /usr/sbin/fanctl: WARNING: ftun0: failed to configure address translation RTNETLINK answers: Cannot assign requested address iptables v1.6.0: Couldn't load target `fan-egress':No such file or directory Try `iptables -h' or 'iptables --help' for more information. iptables: Bad rule (does a matching rule exist in that chain?). iptables: Bad rule (does a matching rule exist in that chain?). iptables: No chain/target/match by that name. rm: cannot remove '/run/ubuntu-fan/nat-core': No such file or directory /usr/sbin/fanatic: unable to bring fan up, unable to configure ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1021-kvm 4.4.0-1021.26 ProcVersionSignature: User Name 4.4.0-1021.26-kvm 4.4.117 Uname: Linux 4.4.0-1021-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 Date: Thu Apr 12 10:22:57 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1763323/+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 1766780] Re: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766780 Title: test_250_config_security_perf_events_restrict in kernel security test failed with 4.15 KVM kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: test_250_config_security_perf_events_restrict from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_250_config_security_perf_events_restrict (__main__.KernelSecurityTest) Ensure CONFIG_SECURITY_PERF_EVENTS_RESTRICT is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2313, in test_250_config_security_perf_events_restrict self.assertEqual(expected, self._test_config(config_name)) AssertionError: True != False The CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_SECURITY_PERF_EVENTS_RESTRICT # CONFIG_SECURITY_PERF_EVENTS_RESTRICT is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:41:49 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1766780/+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 1766565] Re: Unable to insert sysdig_probe module on B-KVM kernel
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766565 Title: Unable to insert sysdig_probe module on B-KVM kernel Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: The sysdig-dkms module cannot be installed on the B-KVM kernel before (bug 1764693), but the installation works with 4.15.0-1007 However, when you try to insert the module, it will complain about: $ sudo modprobe sysdig-probe modprobe: ERROR: could not insert 'sysdig_probe': Unknown symbol in module, or unknown parameter (see dmesg) Log in dmesg: [ 1989.967807] sysdig_probe: loading out-of-tree module taints kernel. [ 1989.967924] sysdig_probe: module verification failed: signature and/or required key missing - tainting kernel [ 1989.967986] sysdig_probe: Unknown symbol tracepoint_probe_unregister (err 0) [ 1989.968090] sysdig_probe: Unknown symbol for_each_kernel_tracepoint (err 0) [ 1989.968094] sysdig_probe: Unknown symbol tracepoint_probe_register (err 0) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1007-kvm 4.15.0-1007.7 ProcVersionSignature: User Name 4.15.0-1007.7-kvm 4.15.17 Uname: Linux 4.15.0-1007-kvm x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 11:31:08 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1766565/+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 1766777] Re: test_182_config_hardened_usercopy in kernel security test failed with 4.15 KVM kernel
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766777 Title: test_182_config_hardened_usercopy in kernel security test failed with 4.15 KVM kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test test_182_config_hardened_usercopy from the kernel security test suite failed with 4.15.0-1008 KVM kernel. FAIL: test_182_config_hardened_usercopy (__main__.KernelSecurityTest) Ensure CONFIG_HARDENED_USERCOPY is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2176, in test_182_config_hardened_usercopy self.assertTrue(self._test_config(config_name)) AssertionError: False is not true The CONFIG_HARDENED_USERCOPY is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_HARDENED_USERCOPY # CONFIG_HARDENED_USERCOPY is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:36:58 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1766777/+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 1766774] Re: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1766774 Title: test_190_config_kernel_fortify in kernel security test failed with 4.15 KVM kernel Status in QA Regression Testing: New Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Bug description: Test test_190_config_kernel_fortify from the kernel security test suite failed with 4.15.0-1008 KVM kernel. == FAIL: test_190_config_kernel_fortify (__main__.KernelSecurityTest) Ensure CONFIG_FORTIFY_SOURCE is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2186, in test_190_config_kernel_fortify self.assertTrue(self._test_config(config_name)) AssertionError: False is not true The CONFIG_FORTIFY_SOURCE is not set. $ cat /boot/config-4.15.0-1008-kvm | grep CONFIG_FORTIFY_SOURCE # CONFIG_FORTIFY_SOURCE is not set ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1008-kvm 4.15.0-1008.8 ProcVersionSignature: User Name 4.15.0-1008.8-kvm 4.15.17 Uname: Linux 4.15.0-1008-kvm x86_64 NonfreeKernelModules: signpost ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 Date: Wed Apr 25 04:28:13 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/qa-regression-testing/+bug/1766774/+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 1716603] Re: [HP Proliant m400] hwclock change won't take effect immediately
** Also affects: ubuntu-kernel-tests 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/1716603 Title: [HP Proliant m400] hwclock change won't take effect immediately Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: So far this issue was only spotted on this specific hardware. And can be seen from kernel 3.13~4.12 Not sure if this is a bug to the software or the hardware. Test case: sudo /sbin/hwclock --set --date "2/2/80 03:04:00"; sudo LC_ALL=C /sbin/hwclock Expected result: * You should see the clock has been changed to 1980 Actual result: * It's still showing the current time and date. But if you check it again later (about 1 or 2 seconds) with "sudo hwclock", you will see the updated time and date. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-93-generic 4.4.0-93.116 ProcVersionSignature: User Name 4.4.0-93.116-generic 4.4.79 Uname: Linux 4.4.0-93-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 12 07:55 seq crw-rw 1 root audio 116, 33 Sep 12 07:55 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.10 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Date: Tue Sep 12 07:57:28 2017 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.4.0-93-generic N/A linux-backports-modules-4.4.0-93-generic N/A linux-firmware1.157.12 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1716603/+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 1684788] Re: extend-file-random.sh.btrfs from ubuntu_ecryptfs-test-suite failed on X-hwe
** Also affects: ubuntu-kernel-tests 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/1684788 Title: extend-file-random.sh.btrfs from ubuntu_ecryptfs-test-suite failed on X-hwe Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This test has failed on both amd64, i386 and arm64 X-hwe kernel 04/15 05:13:07 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:07 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:08 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:08 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:08 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:08 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:08 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 04/15 05:13:21 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:22 DEBUG| utils:0153| [stdout] extend-file-random FAIL 04/15 05:13:22 DEBUG| utils:0153| [stdout] 04/15 05:13:22 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:22 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:22 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t extend-file-random.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 14.147703886 stdout: extend-file-random FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name 4.4.0-74.95~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Thu Apr 20 13:53:40 2017 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1684788/+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 1715376] Re: ip link add command return: Error: either "dev" is duplicate, or "enp1s0" is a garbage.
** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1715376 Title: ip link add command return: Error: either "dev" is duplicate, or "enp1s0" is a garbage. Status in ubuntu-kernel-tests: New Status in iproute2 package in Ubuntu: New Bug description: With iproute2 3.12 on Trusty, command: sudo ip link add type veth peer enp1s0 name testveth0 Will return: Error: either "dev" is duplicate, or "enp1s0" is a garbage. However, this command works fine since Xenial (iproute2 4.3.0) As we will need this for kenrel SRU testing, it will be great to have this fixed on Trusty. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: iproute2 3.12.0-2ubuntu1 ProcVersionSignature: User Name 3.13.0-129.178-generic 3.13.11-ckt39 Uname: Linux 3.13.0-129-generic aarch64 ApportVersion: 2.14.1-0ubuntu3.25 Architecture: arm64 Date: Wed Sep 6 10:54:47 2017 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: iproute2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1715376/+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 1684789] Re: trunc-file.sh.btrfs from ubuntu_ecryptfs-test-suite failed on T-LTS
** Also affects: ubuntu-kernel-tests 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/1684789 Title: trunc-file.sh.btrfs from ubuntu_ecryptfs-test-suite failed on T-LTS Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: This test has failed on both amd64, i386 and arm64 T-LTS kernel For this test, it complains about the: size should be > 0 04/15 05:13:22 DEBUG| utils:0116| Running 'apt-get install --yes --force-yes build-essential libglib2.0-dev intltool keyutils libkeyutils-dev libpam0g-dev libnss3-dev libtool acl xfsprogs btrfs-tools libattr1-dev gcc-multilib' 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading package lists... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Building dependency tree... 04/15 05:13:22 DEBUG| utils:0153| [stdout] Reading state information... 04/15 05:13:22 DEBUG| utils:0153| [stdout] acl is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] build-essential is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] gcc-multilib is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] intltool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] keyutils is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libattr1-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libkeyutils-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libtool is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] xfsprogs is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] btrfs-tools is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libglib2.0-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libnss3-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] libpam0g-dev is already the newest version. 04/15 05:13:22 DEBUG| utils:0153| [stdout] 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 04/15 05:13:22 DEBUG| utils:0116| Running 'which gcc' 04/15 05:13:22 DEBUG| utils:0153| [stdout] /usr/bin/gcc 04/15 05:13:22 DEBUG| utils:0116| Running 'tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs' 04/15 05:13:34 ERROR| utils:0153| [stderr] size should be > 0 04/15 05:13:35 DEBUG| utils:0153| [stdout] trunc-file FAIL 04/15 05:13:35 DEBUG| utils:0153| [stdout] 04/15 05:13:35 DEBUG| utils:0153| [stdout] Test Summary: 04/15 05:13:35 DEBUG| utils:0153| [stdout] 0 passed 04/15 05:13:35 DEBUG| utils:0153| [stdout] 1 failed 04/15 05:13:35 ERROR| test:0414| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_ecryptfs/ubuntu_ecryptfs.py", line 45, in run_once self.results = utils.system_output(cmd, retain_output=True) File "/home/ubuntu/autotest/client/shared/utils.py", line 1267, in system_output verbose=verbose, args=args).stdout File "/home/ubuntu/autotest/client/shared/utils.py", line 918, in run "Command returned non-zero exit status") CmdError: Command failed, rc=1, Command returned non-zero exit status * Command: tests/run_one.sh -K -t trunc-file.sh -b 100 -D /mnt/image -l /mnt/lower -u /mnt/upper -f btrfs Exit status: 1 Duration: 12.9071211815 stdout: trunc-file FAIL Test Summary: 0 passed 1 failed stderr: size should be > 0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-4.4.0-74-generic 4.4.0-74.95~14.04.1 ProcVersionSignature: User Name 4.4.0-74.95~14.04.1-generic 4.4.59 Uname: Linux 4.4.0-74-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.23 Architecture: amd64 Date: Thu Apr 20 13:58:58 2017 SourcePackage: linux-lts-xenial UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1684789/+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 1774471] Comment bridged from LTC Bugzilla
--- Comment From bren...@br.ibm.com 2018-06-01 08:47 EDT--- Just to help the SRU justification, this is a POWER9 specific driver at this moment. -- 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/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+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 1774636] [NEW] Lenovo V330 needs patch in ideapad_laptop module for rfkill
Public bug reported: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: Incomplete Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+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 1774636] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1774636 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/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: Incomplete Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+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 1774640] [NEW] Bluetooth turns off automatically Ubuntu 18.04 LTS
Public bug reported: Whenever I start up my laptop and connect my JBL-speaker, the device stays connected. However, when I turn de speaker off, and try to reconnect to the speaker, the Bluetooth automatically turns off. I then need to restart my laptop and then only Bluetooth works again. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Bluetooth turns of automatically Ubuntu 18.04 LTS + Bluetooth turns off automatically Ubuntu 18.04 LTS -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1774640 Title: Bluetooth turns off automatically Ubuntu 18.04 LTS Status in bluez package in Ubuntu: New Bug description: Whenever I start up my laptop and connect my JBL-speaker, the device stays connected. However, when I turn de speaker off, and try to reconnect to the speaker, the Bluetooth automatically turns off. I then need to restart my laptop and then only Bluetooth works again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1774640/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
ok. done: https://bugs.launchpad.net/bugs/1774636 -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, would it be possible to include the patch in the ubuntu kernel packages until it is merged upstream? Especially, support in 18.04 would nice. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1774190] Re: linux: 3.13.0-151.201 -proposed tracker
** Tags added: kernel-block-proposed -- 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/1774190 Title: linux: 3.13.0-151.201 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1774191 (linux-lts-trusty) derivatives: -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774190/+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 1774124] Re: linux: 4.13.0-45.50 -proposed tracker
** Tags added: kernel-block-proposed -- 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/1774124 Title: linux: 4.13.0-45.50 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1774126 (linux-oem), bug 1774127 (linux-gcp), bug 1774129 (linux-hwe) derivatives: bug 1774125 (linux-raspi2) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774124/+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 1772960] Re: linux: 4.4.0-128.154 -proposed tracker
** Tags added: kernel-block-proposed -- 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/1772960 Title: linux: 4.4.0-128.154 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-certification-testing series: Fix Released Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772962 (linux-lts-xenial), bug 1772963 (linux-aws) derivatives: bug 1772964 (linux-kvm), bug 1772965 (linux-snapdragon), bug 1772966 (linux-aws), bug 1772968 (linux-raspi2), bug 1772969 (linux-euclid) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772960/+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 1772972] Re: linux: -proposed tracker
** Tags added: kernel-block-proposed -- 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/1772972 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-lbm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: derivatives: To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772972/+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 1772927] Re: linux: 4.15.0-23.25 -proposed tracker
** Tags added: kernel-block-proposed -- 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/1772927 Title: linux: 4.15.0-23.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1772935 (linux-hwe-edge), bug 1772940 (linux-azure), bug 1772942 (linux-azure-edge) derivatives: bug 1772929 (linux-raspi2), bug 1772930 (linux-azure), bug 1772931 (linux-aws), bug 1772932 (linux-kvm), bug 1772933 (linux-oem), bug 1772934 (linux-gcp) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1772927/+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 1774636] Re: Lenovo V330 needs patch in ideapad_laptop module for rfkill
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: kernel-da-key -- 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/1774636 Title: Lenovo V330 needs patch in ideapad_laptop module for rfkill Status in linux package in Ubuntu: Triaged Bug description: The quite new Lenovo V330 is not yet completely supported by the ideapad_laptop module. Without an explicit rule, this module assumes that a hardware kill switch for wireless devices exists and thus sometimes boots up with all devices hard blocked and no way to reenable them at runtime. I have provided a patch to the kernel developers upstream: https://bugzilla.kernel.org/show_bug.cgi?id=199855 However, there is not much activity at the moment. Since this laptop is available now and the bug is a real blocker for unexperienced users, would it be possible to add the (quite simple) fix to the ubuntu kernel until it is accepted upstream? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774636/+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 1774471] Re: Various fixes for CXL kernel module
** Tags added: kernel-da-key -- 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/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: New Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1768431] Re: Request to revert SAUCE patches in the 18.04 SRU and update with upstream version
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-June/092901.html ** Description changed: + + == SRU Justification == + This SRU was requested by IBM. It contains one SAUCE patch and three + commits from linux.next. + + IBM requested that we revert a set of SAUCE patches from 18.04 and + replace them with patches from linux-next. Based on review comments, + there has been minor changes from the original SAUCE patches and the + versions in linux-next. + + The first SAUCE patch contains all the changes between the current version + of SAUCE patches for latest cxlflash patches in bionic and the latest + version accepted by the community. This only has the needed changes and + makes it so we don't have to revert and re-apply a high number of patches. + In addition to the SAUCE patch, IBM requested the 3 additional new patches + from the linux-next tree. + + == Fixes == + UBUNTU: SAUCE: (no-up) cxlflash: OCXL diff between v2 and v3 + a3feb6ef50de ("scsi: cxlflash: Synchronize reset and remove ops") + 9a597cd4c0ce ("scsi: cxlflash: Remove commmands from pending list on timeout)" + d2d354a606d5 ("scsi: cxlflash: Handle spurious interrupts") + + == Regression Potential == + Medium. All the patches are specific to the cxlflash driver, but there + are four of them and one is a SAUCE patch. + + == Test Case == + A test kernel was built with these patches and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + == Comment: #0 - UMA KRISHNAN - 2018-04-30 14:41:30 == ---Problem Description--- Request to revert SAUCE patches from 18.04 and apply the patches from next/master. Below set of cxlflash patches were submitted to Canonical after they were sent to the community. Based on review comments, there has been minor changes from that version. This BZ is to request reverting those SAUCE patches with the ones that are queued in next/master tree for 4.18. - SAUCE: cxlflash: Preserve number of interrupts for master contexts - SAUCE: cxlflash: Avoid clobbering context control register value - SAUCE: cxlflash: Add argument identifier names - SAUCE: cxlflash: Introduce OCXL backend - SAUCE: cxlflash: Hardware AFU for OCXL - SAUCE: cxlflash: Read host function configuration - SAUCE: cxlflash: Setup function acTag range - SAUCE: cxlflash: Read host AFU configuration - SAUCE: cxlflash: Setup AFU acTag range - SAUCE: cxlflash: Setup AFU PASID - SAUCE: cxlflash: Adapter context support for OCXL - SAUCE: cxlflash: Use IDR to manage adapter contexts - SAUCE: cxlflash: Support adapter file descriptors for OCXL - SAUCE: cxlflash: Support adapter context discovery - SAUCE: cxlflash: Support image reload policy modification - SAUCE: cxlflash: MMIO map the AFU - SAUCE: cxlflash: Support starting an adapter context - SAUCE: cxlflash: Support process specific mappings - SAUCE: cxlflash: Support AFU state toggling - SAUCE: cxlflash: Support reading adapter VPD data - SAUCE: cxlflash: Setup function OCXL link - SAUCE: cxlflash: Setup OCXL transaction layer - SAUCE: cxlflash: Support process element lifecycle - SAUCE: cxlflash: Support AFU interrupt management - SAUCE: cxlflash: Support AFU interrupt mapping and registration - SAUCE: cxlflash: Support starting user contexts - SAUCE: cxlflash: Support adapter context polling - SAUCE: cxlflash: Support adapter context reading - SAUCE: cxlflash: Support adapter context mmap and release - SAUCE: cxlflash: Support file descriptor mapping - SAUCE: cxlflash: Introduce object handle fop - SAUCE: cxlflash: Setup LISNs for user contexts - SAUCE: cxlflash: Setup LISNs for master contexts - SAUCE: cxlflash: Update synchronous interrupt status bits - SAUCE: cxlflash: Introduce OCXL context state machine - SAUCE: cxlflash: Register for translation errors - SAUCE: cxlflash: Support AFU reset - SAUCE: cxlflash: Enable OCXL operations Also, there are 3 additional patches added to end of this series that we would like to request being pulled into the SRU stream. These 3 patches address bug fixes. The commit ids for the patches queued in next/master tree are, 768999d6b1eadc6a13b1fba1886f1708f433d82b scsi: cxlflash: Preserve number of interrupts for master contexts 6c2b116dd38e3fbda10c3e3d5ac80ea7442e4f4d scsi: cxlflash: Avoid clobbering context control register value fcace1d5e11f518c6f91dd245fa1ac37393b47d3 scsi: cxlflash: Add argument identifier names 863dbdc0552f8bc100df48bb231089c382b89004 scsi: cxlflash: Introduce OCXL backend f2180daa83950ff8183f70b1b78d67cb13fd90b2 scsi: cxlflash: Hardware AFU for OCXL 1042535633554592d7d95a9cf83d2940803689e0 scsi: cxlflash: Read host function configuration ba84823a8b448207659753ae4f9c8b956923bada scsi: cxlflash: Setup function acTag range f55ced2dcd00ab257a2bb25eee619b75cda24817 scsi: cxlflash: Read host AFU configuration c5a8fec11278e245136c7f696c91426
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
** No longer affects: linux (Ubuntu Cosmic) ** Description changed: + == SRU Justification == + The bug reporter states that after update to Kernel 4.13-43 the intel + graphics seem to really lag - especially noticeable in apps which are + using vsync, which, at least on his system, locks to 40fps unlike the + previous kernel. + + See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- + graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some + other users with the same issue + + This regression was introduced by upstream commit dc911f5bd8aa. A + revert of this commit fixes this bug. Upstream has already reverted + this commit in drm-tip tree and cc'd it to upstream stable. However, + the revert has not landed in mainline or stable yet, so it is being sent + as a SAUCE patch. + + The revert is also needed in Bionic. However, the Bionic revert is + slightly differant, so it will be SRU'd separately. + + == Fix == + UBUNTU: SAUCE: Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available." + + == Regression Potential == + Low. This revert is to fix a current regression. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue - In short + In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem - --- + --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: james 2835 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 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 8087:0a2a Intel Corp. - Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 8087:0a2a Intel Corp. + Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: - linux-restricted-modules-4.13.0-43-generic N/A - linux-backports-modules-4.13.0-43-generic N/A - linux-firmware 1.157.18 + linux-restricted-modules-4.13.0-43-generic N/A + linux-backports-modules-4.13.0-43-generic N/A + linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP -- 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == The bug reporter states that after update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on his system, locks
[Kernel-packages] [Bug 1773520] Re: After update to 4.13-43 Intel Graphics are Laggy
SRU request submitted for Artful: https://lists.ubuntu.com/archives/kernel-team/2018-June/092906.html Bionic SRU request: https://lists.ubuntu.com/archives/kernel-team/2018-June/092908.html -- 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/1773520 Title: After update to 4.13-43 Intel Graphics are Laggy Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == The bug reporter states that after update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on his system, locks to 40fps unlike the previous kernel. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue This regression was introduced by upstream commit dc911f5bd8aa. A revert of this commit fixes this bug. Upstream has already reverted this commit in drm-tip tree and cc'd it to upstream stable. However, the revert has not landed in mainline or stable yet, so it is being sent as a SAUCE patch. The revert is also needed in Bionic. However, the Bionic revert is slightly differant, so it will be SRU'd separately. == Fix == UBUNTU: SAUCE: Revert "drm/i915/edp: Allow alternate fixed mode for eDP if available." == Regression Potential == Low. This revert is to fix a current regression. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. After update to Kernel 4.13-43 the intel graphics seem to really lag - especially noticeable in apps which are using vsync, which, at least on my system, locks to 40fps unlike the previous kernel I have installed (4.13-41) which locks at a steady 60fps. See https://askubuntu.com/questions/1039189/today-i-got-an-update-and- graphics-are-not-working-right-on-ubuntu-16-04/1040545#1040545 for some other users with the same issue In short 4.13-41 doesn't have the problem 4.13-43 has the laggy problem --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: james 2835 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=ac1331a0-15f2-4832-aebc-48e3ad655add InstallationDate: Installed on 2016-05-31 (724 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 8087:0a2a Intel Corp. Bus 001 Device 002: ID 04f2:b50d Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Gaming Notebook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-43-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.157.18 Tags: xenial Uname: Linux 4.13.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker libvirtd lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/16/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.53 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 80A9 dmi.board.vendor: HP dmi.board.version: 91.18 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.53:bd09/16/2015:svnHP:pnHPPavilionGamingNotebook:pvrType1ProductConfigId:rvnHP:rn80A9:rvr91.18:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion Gaming Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773520/+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 1773509] Re: ELANPAD ELAN0612 does not work, patch available
SRU requested: https://lists.ubuntu.com/archives/kernel-team/2018-June/092918.html ** Description changed: + == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, - would it be possible to include the patch in the ubuntu kernel packages - until it is merged upstream? Especially, support in 18.04 would nice. + this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 + + == Fix == + UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table + + == Regression Potential == + Low. One liner to add a device id. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. ** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- 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/1773509 Title: ELANPAD ELAN0612 does not work, patch available Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Artful: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Seems there is a new version of the ELANPAD touchpad with identifier ELAN0612 that is being included in newer laptops. The kernel itself doesn't have support for this touchpad yet. However, the patch to get this working is trivial. Since people start being affected by this, this patch is being sent as a SAUCE patch until it lands upstream. The upstream bug at the Kernel project, including the patch is here: https://bugzilla.kernel.org/show_bug.cgi?id=199253 == Fix == UBUNTU: SAUCE: Input: elan_i2c - add ELAN0612 to the ACPI table == Regression Potential == Low. One liner to add a device id. == Test Case == A test kernel was built with this patch and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773509/+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 1768143] Re: vmxnet3: update to latest ToT
Bionic SRU request: https://lists.ubuntu.com/archives/kernel-team/2018-June/092911.html Xenial SRU request: https://lists.ubuntu.com/archives/kernel-team/2018-June/092915.html ** Description changed: + == SRU Justification == + Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit + reset and rxvlan disabled fix. VMWare is requesting these fixes in + Bionic and Xenial. + + A backport was needed to update version info in vmxnet3_int.h + + == Fixes == + 7a4c003d6921 ("vmxnet3: avoid xmit reset due to a race in vmxnet3)" + 034f40579389 ("vmxnet3: use correct flag to indicate LRO feature") + 65ec0bd1c7c1 ("vmxnet3: fix incorrect dereference when rxvlan is disabled") + + == Regression Potential == + Low. Limited to vmxnet3 driver. + + == Test Case == + A test kernel was built with these patches and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit reset and rxvlan disabled fix. Below are the commits: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases? Thanks, Ronak -- 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/1768143 Title: vmxnet3: update to latest ToT Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Bug description: == SRU Justification == Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit reset and rxvlan disabled fix. VMWare is requesting these fixes in Bionic and Xenial. A backport was needed to update version info in vmxnet3_int.h == Fixes == 7a4c003d6921 ("vmxnet3: avoid xmit reset due to a race in vmxnet3)" 034f40579389 ("vmxnet3: use correct flag to indicate LRO feature") 65ec0bd1c7c1 ("vmxnet3: fix incorrect dereference when rxvlan is disabled") == Regression Potential == Low. Limited to vmxnet3 driver. == Test Case == A test kernel was built with these patches and tested by the original bug reporter. The bug reporter states the test kernel resolved the bug. Recently, a couple of fixes went in vmxnet3 driver related to LRO, transmit reset and rxvlan disabled fix. Below are the commits: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=7a4c003d6921e2af215f4790aa43a292bdc78be0 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=034f405793897a3c8f642935f5494b86c340cde7 https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=65ec0bd1c7c14522670a5294de35710fb577a7fd This is a request to bring Ubuntu vmxnet3 driver up to date with ToT Linux kernel. Could you please backport it to 16.04 and 18.04 LTS releases? Thanks, Ronak To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768143/+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 1772031] Re: kernel backtrace when receiving large UDP packages
SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2018-June/092921.html ** Description changed: + == SRU Justification == + Artful is missing commit a90bcb86ae70, which was sent + to upstream stable. Since upstream 4.13 is EOL, Artful never got it. + + Because Artful does not have this commit when receiving large UDP packages + with a small MTU there are backtraces, examples posted in the bug. + + Commit a90bcb86ae70 is in mainline as ov v4.14-rc2 and is only needed in + Artful. + + == Fix == + a90bcb86ae70 ("iov_iter: fix page_copy_sane for compound pages") + + == Regression Potential == + Low. This commit fixes a current regression in Artful. It was also + cc'd to stable, so it has had additional upstream review. + + == Test Case == + A test kernel was built with this patch and tested by the original bug reporter. + The bug reporter states the test kernel resolved the bug. + + + + + + kernel 4.13.0-41-generic is missing commit a90bcb86ae70: Author: Petar Penkov Date: Tue Aug 29 11:20:32 2017 -0700 - iov_iter: fix page_copy_sane for compound pages - - Issue is that if the data crosses a page boundary inside a compound - page, this check will incorrectly trigger a WARN_ON. - - To fix this, compute the order using the head of the compound page and - adjust the offset to be relative to that head. - - Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page - primitives") - - Signed-off-by: Petar Penkov - CC: Al Viro - CC: Eric Dumazet - Signed-off-by: Al Viro + iov_iter: fix page_copy_sane for compound pages + + Issue is that if the data crosses a page boundary inside a compound + page, this check will incorrectly trigger a WARN_ON. + + To fix this, compute the order using the head of the compound page and + adjust the offset to be relative to that head. + + Fixes: 72e809ed81ed ("iov_iter: sanity checks for copy to/from page + primitives") + + Signed-off-by: Petar Penkov + CC: Al Viro + CC: Eric Dumazet + Signed-off-by: Al Viro Commit 72e809ed81ed is in kernel 4.13.0-41-generic. As a result, when receiving large UDP packages with a small MTU we get backtraces like: [ 361.260969] [ cut here ] [ 361.260974] WARNING: CPU: 4 PID: 2541 at /build/linux-hwe-v6kHHF/linux-hwe-4.13.0/lib/iov_iter.c:693 copy_page_to_iter+0x194/0x2d0 [ 361.260975] Modules linked in: cmdlinepart sfc(OE) hwmon_vid crc32_generic mii rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache 8021q garp mrp stp llc intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm i] [ 361.261002] CPU: 4 PID: 2541 Comm: udp_recv Tainted: G OE 4.13.0-39-generic #44~16.04.1-Ubuntu [ 361.261003] Hardware name: Dell Inc. PowerEdge R220/05Y15N, BIOS 1.4.0 10/23/2014 [ 361.261004] task: 91630b2bae80 task.stack: bb19c2bfc000 [ 361.261005] RIP: 0010:copy_page_to_iter+0x194/0x2d0 [ 361.261006] RSP: 0018:bb19c2bffc60 EFLAGS: 00010202 [ 361.261007] RAX: 1000 RBX: 00df RCX: 0017c000 [ 361.261008] RDX: 00df RSI: 0f8e RDI: f666895279c0 [ 361.261009] RBP: bb19c2bffca0 R08: 106d R09: 1024 [ 361.261009] R10: R11: 91630ccc9b00 R12: 91630d27a300 [ 361.261010] R13: bb19c2bffde0 R14: 00df R15: 0175 [ 361.261011] FS: 7fb8e7649700() GS:91631fd0() knlGS: [ 361.261012] CS: 0010 DS: ES: CR0: 80050033 [ 361.261013] CR2: 14588da85624 CR3: 00024bad2002 CR4: 001606e0 [ 361.261013] Call Trace: [ 361.261017] ? proto_init_net+0x40/0x40 [ 361.261019] skb_copy_datagram_iter+0x171/0x270 [ 361.261022] udp_recvmsg+0x108/0x490 [ 361.261024] inet_recvmsg+0x51/0xc0 [ 361.261026] sock_recvmsg+0x43/0x50 [ 361.261028] sock_read_iter+0x90/0xe0 [ 361.261030] new_sync_read+0xe2/0x130 [ 361.261032] __vfs_read+0x29/0x40 [ 361.261033] vfs_read+0x93/0x130 [ 361.261034] SyS_read+0x55/0xc0 [ 361.261037] entry_SYSCALL_64_fastpath+0x24/0xab [ 361.261038] RIP: 0033:0x7fb8e7160260 [ 361.261039] RSP: 002b:7ffed9dd9e38 EFLAGS: 0246 ORIG_RAX: [ 361.261040] RAX: ffda RBX: RCX: 7fb8e7160260 [ 361.261041] RDX: ffe3 RSI: 5622ad02f0a0 RDI: 0003 [ 361.261041] RBP: 7ffed9dd9e70 R08: R09: 0011 [ 361.261042] R10: R11: 0246 R12: 5622ace2e800 [ 361.261043] R13: 7ffed9dd9f50 R14: R15: - [ 361.261044] Code: de 4c 89 e7 e8 be fa ff ff 41 83 af a0 12 00 00 01 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 8b 4f 6c 48 d3 e0 e9 9d fe ff ff <0f> ff
[Kernel-packages] [Bug 1709590] Re: linux 4.11.0-13.19 ADT test failure with linux 4.11.0-13.19
** Changed in: linux Status: New => 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/1709590 Title: linux 4.11.0-13.19 ADT test failure with linux 4.11.0-13.19 Status in Linux: Fix Released Status in linux package in Ubuntu: Won't Fix Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/amd64/l/linux/20170808_005440_496d8@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/i386/l/linux/20170808_034227_496d8@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/ppc64el/l/linux/20170807_234110_496d8@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1709590/+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 1774127] Re: linux-gcp: 4.13.0-1019.23 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1774127 Title: linux-gcp: 4.13.0-1019.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1774124 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1774127/+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 1774606] Re: [Redpine] Wifi AP does not work
** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1774606 Title: [Redpine] Wifi AP does not work Status in HWE Next: New Status in linux-oem package in Ubuntu: Confirmed Status in linux-oem source package in Bionic: Fix Committed Bug description: WiFi AP can not be enabled in Ubuntu Server 18.04 with Redpine driver for 4.15 kernel. Several issues were observed in Redpine driver which supports RS9113 Wifi+BT combo chip: 1. 40Mhz connection issue 2. Mode 1,13,14,4,6 change issue 3. SoftAP failure issue This bug is of tracking purposes only, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1774606/+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 1768974] Re: Several hisi_sas bug fixes
Tested on D05 & D06. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1768974 Title: Several hisi_sas bug fixes Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Several issues have been fixed upstream in the hisi_sas driver: - Driver may configure the wrong signal attenuation setting - Driver may not negotiate the correct max link rate supported by the phy - phy must be disabled before trying to change its link rate - Internal abort timeout doesn't take into account link negotiation time - Driver returns incorrect values to upper levels [Test Case] Regression testing on D05 and D06 systems, which have different versions of this controller. [Regression Risk] Code changes are restricted to the hisi_sas driver, and the HisSilicon D05 and D06 are the only two boards Ubuntu supports that use this driver. Explicit testing on these two boards should mitigate the regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768974/+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 1768948] Re: Hotplugging a SATA disk into a SAS controller may cause crash
Smoke tested on HiSilicon D05 & D06 systems (I don't have physical access to do the hot-pull/plug) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1768948 Title: Hotplugging a SATA disk into a SAS controller may cause crash Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] Hotplugging a SATA disk into a SAS controller may trigger a NULL pointer dereference, leading to a crash: [ 2366.923208] Unable to handle kernel NULL pointer dereference at virtual address 07b8 ... [ 2368.766334] Call trace: [ 2368.781712] [] sas_find_dev_by_rphy+0x48/0x118 [ 2368.800394] [] sas_target_alloc+0x28/0x98 [ 2368.817975] [] scsi_alloc_target+0x248/0x308 [ 2368.835570] [] __scsi_add_device+0xb8/0x160 [ 2368.853034] [] ata_scsi_scan_host+0x190/0x230 [ 2368.871614] [] ata_scsi_hotplug+0xc8/0xe8 [ 2368.889152] [] process_one_work+0x164/0x438 [ 2368.908003] [] worker_thread+0x144/0x4b0 [ 2368.924613] [] kthread+0xfc/0x110 [Test Case] Unplug a SATA disk from a SAS controller and insert a new SATA disk in its place. [Fix] The ATA_PFLAG_SCSI_HOTPLUG flag is what causes libsas to attempt to handle hot add/remove. However, for ata devices on a SAS controller, this should be handled by libata. The solution is to not set this flag for ATA devices on a SAS controller. [Regression Risk] The fix is a clean cherry-pick from upstream that is tagged for stable. No subsequent patches in linux-next have a "Fixes:" marker referencing this patch, suggesting no regressions have been found since its introduction. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768948/+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 1768971] Re: Warnings/hang during error handling of SATA disks on SAS controller
Smoke tested on HiSilicon D05 & D06 systems (I don't have physical access to yank disks). ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1768971 Title: Warnings/hang during error handling of SATA disks on SAS controller Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: [Impact] When a SATA device, attached to a SAS controller, begins generating errors (e.g. device failing, or someone yanked it), the SAS error handling will complete, but may leave zombie ATA commands that never get properly processed/freed. This can cause some ugly messages on the console, and eventually leads to a system hang-up. WARNING: CPU: 0 PID: 28512 at drivers/ata/libata-eh.c:4037 ata_eh_finish+0xb4/0xcc CPU: 0 PID: 28512 Comm: kworker/u32:2 Tainted: G W OE 4.14.0#1 .. Call trace: [] ata_eh_finish+0xb4/0xcc [] ata_do_eh+0xc4/0xd8 [] ata_std_error_handler+0x44/0x8c [] ata_scsi_port_error_handler+0x480/0x694 [] async_sas_ata_eh+0x4c/0x80 [] async_run_entry_fn+0x4c/0x170 [] process_one_work+0x144/0x390 [] worker_thread+0x144/0x418 [] kthread+0x10c/0x138 [] ret_from_fork+0x10/0x18 [Test Case] I don't have a reliable reproducer for this, but one possible test is to yank an active/hotpluggable SATA disk from its controller and see if the above symptoms occur. [Fix] The solution here is to call into libata to have it process the remaining commands, allowing us to free up the zombie commands, preventing the leak and eventual starvation. [Regression Risk] This is a clean cherry-pick from upstream, so any regressions should have upstream support. As of this writing, there are no changesets in linux-next marked as Fixing this commit, implying that upstream has not yet found/fixed any bugs related to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1768971/+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 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts
ubuntu@d05-1:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 enahisic2i0-tx3 enahisic2i0-tx4 enahisic2i0-tx5 enahisic2i0-tx6 enahisic2i0-tx7 enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 -- 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/1765977 Title: HiSilicon HNS NIC names are truncated in /proc/interrupts Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult for an admin to associate activity among adapters in the system. [Test Case] $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' Without the fix: enahisic2i0-tx0 enahisic2i0-tx1 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 With the fix: enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 [Regression Risk] Upstream patch, restricted to a single driver for a system we can directly test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765977/+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 1765977] Re: HiSilicon HNS NIC names are truncated in /proc/interrupts
Previous comment was verification w/ the following kernel: ubuntu@d05-1:~$ cat /proc/version Linux version 4.15.0-23-generic (buildd@bos02-arm64-002) (gcc version 7.3.0 (Ubuntu/Linaro 7.3.0-16ubuntu3)) #25-Ubuntu SMP Wed May 23 17:59:52 UTC 2018 ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1765977 Title: HiSilicon HNS NIC names are truncated in /proc/interrupts Status in linux package in Ubuntu: In Progress Status in linux source package in Artful: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] HiSilicon HNS NIC names are truncated in /proc/interrupts, making it difficult for an admin to associate activity among adapters in the system. [Test Case] $ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //' Without the fix: enahisic2i0-tx0 enahisic2i0-tx1 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 enahisic2i0-tx1 With the fix: enahisic2i0-tx0 enahisic2i0-tx1 enahisic2i0-tx2 [...] enahisic2i0-tx8 enahisic2i0-tx9 enahisic2i0-tx10 enahisic2i0-tx11 enahisic2i0-tx12 enahisic2i0-tx13 enahisic2i0-tx14 enahisic2i0-tx15 [Regression Risk] Upstream patch, restricted to a single driver for a system we can directly test. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1765977/+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 1750038] Re: user space process hung in 'D' state waiting for disk io to complete
I have confirmation from the user who reported this that they have tested the new kernel 4.4.0-128.154 in their test environment for a 24 hours stress test and could not reproduce the issue. I changed the tag to verification done. ** Tags removed: verification-needed-xenial ** Tags added: verification-done-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/1750038 Title: user space process hung in 'D' state waiting for disk io to complete Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Bug description: == SRU Justification == [Impact] Occasionally an application gets stuck in "D" state on NFS reads/sync and close system calls. All the subsequent operations on the NFS mounts are stuck and reboot is required to rectify the situation. [Fix] Use GPF_NOIO in some allocations in writeback to avoid a deadlock. This is upstream in: ae97aa524ef4 ("NFS: Use GFP_NOIO for two allocations in writeback") [Testcase] See Test scenario in previous description. A test kernel with this patch was tested heavily (>100hrs of test suite) without issue. [Regression Potential] This changes memory allocation in NFS to use a different policy. This could potentially affect NFS. However, the patch is already in Artful and Bionic without issue. The patch does not apply to Trusty. == Previous Description == Using Ubuntu Xenial user reports processes hang in D state waiting for disk io. Ocassionally one of the applications gets into "D" state on NFS reads/sync and close system calls. based on the kernel backtraces seems to be stuck in kmalloc allocation during cleanup of dirty NFS pages. All the subsequent operations on the NFS mounts are stuck and reboot is required to rectify the situation. [Test scenario] 1) Applications running in Docker environment 2) Application have cgroup limits --cpu-shares --memory -shm-limit 3) python and C++ based applications (torch and caffe) 4) Applications read big lmdb files and write results to NFS shares 5) use NFS v3 , hard and fscache is enabled 6) now swap space is configured This prevents all other I/O activity on that mount to hang. we are running into this issue more frequently and identified few applications causing this problem. As updated in the description, the problem seems to be happening when exercising the stack try_to_free_mem_cgroup_pages+0xba/0x1a0 we see this with docker containers with cgroup option --memory . whenever there is a deadlock, we see that the process that is hung has reached the maximum cgroup limit, multiple times and typically cleans up dirty data and caches to bring the usage under the limit. This reclaim path happens many times and finally we hit probably a race get into deadlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750038/+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 1774563] Re: Support SocketCAN over USB on Dell IoT 300x Gateways
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Confirmed ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- 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/1774563 Title: Support SocketCAN over USB on Dell IoT 300x Gateways Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: Confirmed Bug description: This driver is from IXXAT and supports SocketCAN over USB. (https://www.ixxat.com) == SRU Justification == Dell IoT 300x gateways support USB-CAN peripherals. Dell expects these devices also support the SocketCAN over USB and is working with HMS to develop and upstream the driver. Meanwhile, we'll have to carry this driver as a SAUCE patch to support our Ubuntu Core 16 release. == Fix == UBUNTU: SAUCE: (no-up) Support IXXAT USB SocketCAN device == Regression Potential == Low. The driver will be built only for amd64 kernels and attach itself to IXXAT USB-CAN adapters with VID 0x08d8. This bug is for tracking purposes only, please do not triage. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774563/+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 1774442] Re: wireless hardblocked and wireless enable button not functional
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Package changed: linux-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774442 Title: wireless hardblocked and wireless enable button not functional Status in linux package in Ubuntu: Incomplete Bug description: Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu. In Windows, system boots with wireless disabled and then pressing the wireless enable button twice enables WiFi. In ubuntu, system boots with wireless disabled and wireless enable button has no functionality either directly or in combination with the fn-key. Module hp_wmi may be the culprit? But disabling this has no effect on hardblock. reference forum post for more detailed info: https://ubuntuforums.org/showthread.php?t=2392934&p=13772159#post13772159 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-43-generic 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 31 10:19:32 2018 InstallationDate: Installed on 2018-05-19 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774442/+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 1774442] [NEW] wireless hardblocked and wireless enable button not functional
You have been subscribed to a public bug: Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu. In Windows, system boots with wireless disabled and then pressing the wireless enable button twice enables WiFi. In ubuntu, system boots with wireless disabled and wireless enable button has no functionality either directly or in combination with the fn-key. Module hp_wmi may be the culprit? But disabling this has no effect on hardblock. reference forum post for more detailed info: https://ubuntuforums.org/showthread.php?t=2392934&p=13772159#post13772159 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.13.0-43-generic 4.13.0-43.48~16.04.1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 31 10:19:32 2018 InstallationDate: Installed on 2018-05-19 (11 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Medium Status: Incomplete ** Tags: amd64 apport-bug xenial -- wireless hardblocked and wireless enable button not functional https://bugs.launchpad.net/bugs/1774442 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1774575] Re: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1774575 Title: hwinfo --framebuffer | VirtualBox 5.2.12 | empty output Status in linux package in Ubuntu: Incomplete Bug description: 1) Ubuntu 4.15.0-22.24-generic 4.15.17; Description:Ubuntu 18.04 LTS Release:18.04 2) lspci-vnvn+hwinfo_policy.log attached 3) What happens: The command "sudo hwinfo --framebuffer" provides an empty output. (Possibly can't find framebuffer info.) 4) Expected: a list of supported video modes (https://askubuntu.com/a/824182/621093) Some additional info A) Enviroment: A1) Ubuntu 18.04 server A2) VirtualBox 5.2.12; installing guest packages and host extensions didn't help. B) VGA compatible controller [0300]: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774575/+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 1774531] Re: [Dell Inspiron 7577] shutdown/reboot hangs
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774531 Title: [Dell Inspiron 7577] shutdown/reboot hangs Status in linux package in Ubuntu: Incomplete Bug description: https://answers.launchpad.net/ubuntu-certification/+question/669743 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 1 01:19:51 2018 InstallationDate: Installed on 2018-05-30 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774531/+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 1774337] Re: touchpad not working
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1774337 Title: touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: I have accessed the virtual terminal tty and then onwards my touchpad has stopped working completely.However an external usb mouse works fine.I have done all the operations and tried my level best to solve the issue but none of them are giving the result.Please go through this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774337/+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 1774425] Re: i915 driver limits virtual resolution to 8192x8192
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- 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/1774425 Title: i915 driver limits virtual resolution to 8192x8192 Status in linux package in Ubuntu: Incomplete Bug description: I have an Intel Iris Pro 580 in my Intel Skull Canyon NUC6I7KYK, a nice little device that has 3 video outputs: * HDMI 2.0 * Mini DisplayPort * Thunderbolt USB-C The product specifications states that the device is able to output three 4K signals. Unfortunately, whenever I tried this in Ubuntu it failed, without any clear error message. After fiddling with other DEs, Kubuntu told me the virtual resolution was not supported. And indeed, as soon as I limited the virtual resolution of the 3 screens to fit in 8192x8192 pixels, all screens worked. Apparently, the i915 driver (in "drivers/gpu/drm/i915/intel_display.c") has not been updated for newer devices when reporting the maximum resolution. As you can see here: https://github.com/torvalds/linux/blob/master/drivers/gpu/drm/i915/intel_display.c#L14671 Only GEN_2 & GEN_3 are checked for, but since the 7th generation max virtual resolutions of 16384x16384 are supported. This issue has been reported to the i915 maintainers a few times, but nothing has changed yet :/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774425/+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 1774282] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1774282 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/1774282 Title: Bluetooth adapter not recognized Status in linux package in Ubuntu: Incomplete Bug description: I have tried with both ubuntu 16.04 and today with 18.04 and the problem persists. I had the blueman installed and nothing works. On windows it works fine, so the adapter is not the issue. piero@piero-dev:/var/log$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 Ubuntu Software 3.28.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-22-generic 4.15.0-22.24 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 19:23:41 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2017-10-17 (224 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) SourcePackage: linux-signed UpgradeStatus: Upgraded to bionic on 2018-05-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774282/+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 1774471] Re: Various fixes for CXL kernel module
** Changed in: linux (Ubuntu) Status: New => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- 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/1774471 Title: Various fixes for CXL kernel module Status in The Ubuntu-power-systems project: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: ---Problem Description--- Couple of CXL patches need to be merged to Ubuntu 18.04.1 kernel source tree. They fix various issues found after the 18.04 kernel freeze: 401dca8cbd14 cxl: Set the PBCQ Tunnel BAR register when enabling capi mode 497a0790e2c6 cxl: Report the tunneled operations status ad7b4e8022b9 cxl: Fix possible deadlock when processing page faults from cxllib 02b63b420223 cxl: Remove function write_timebase_ctrl_psl9() for PSL9 cxl: Configure PSL to not use APC virtual machines : http://patchwork.ozlabs.org/patch/899062/ cxl: Disable prefault_mode in Radix mode : http://patchwork.ozlabs.org/patch/916159/ ---uname output--- 4.15.0-12-generic ---Additional Hardware Info--- a compatible capi FPGA adapter Machine Type = Boston-LC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1774471/+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 1774583] Re: Resuming does not work with kernel 3.13.0-149-generic
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: needs-bisect -- 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/1774583 Title: Resuming does not work with kernel 3.13.0-149-generic Status in linux package in Ubuntu: Incomplete Bug description: On my laptop MSI GE40 (MS-1492) with Ubuntu 14.04.5 LTS and kernel 3.13.0-149-generic resuming after a suspend no longer works. It hangs on a blank screen and is unresponsive. The only option is to hold the power button for 6 seconds to shut it down. It worked fine on 3.13.0-147-generic. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-149-generic 3.13.0-149.199 ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39 Uname: Linux 3.13.0-149-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.28 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-p3041 F pulseaudio /dev/snd/controlC1: j-p3041 F pulseaudio CurrentDesktop: Unity Date: Fri Jun 1 09:22:59 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d0b66801-6479-4dc4-aae2-9bd97799b4a4 InstallationDate: Installed on 2013-11-20 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MachineType: Micro-Star International Co., Ltd. CR42 2M/GE40 2OC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic root=UUID=3a8ce5b7-2d9e-441f-a3a6-16627d17cfa0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-149-generic N/A linux-backports-modules-3.13.0-149-generic N/A linux-firmware 1.127.24 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: Upgraded to trusty on 2014-11-17 (1291 days ago) dmi.bios.date: 08/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1492IMS.10H dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-1492 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: CR42 2M/GE40 2OC dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1492IMS.10H:bd08/05/2013:svnMicro-StarInternationalCo.,Ltd.:pnCR422M/GE402OC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1492:rvrREV1.0:cvnCR422M/GE402OC:ct10:cvrN/A: dmi.product.name: CR42 2M/GE40 2OC dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774583/+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 1774589] Re: System freeze
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.17 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1774589 Title: System freeze Status in linux package in Ubuntu: Incomplete Bug description: System freeze ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-43-generic 4.13.0-43.48 ProcVersionSignature: Ubuntu 4.13.0-43.48-generic 4.13.16 Uname: Linux 4.13.0-43-generic i686 NonfreeKernelModules: wl AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.13.0-43-generic. ApportVersion: 2.20.7-0ubuntu3.9 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CX20590 Analog [CX20590 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mohammad881 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0xf371 irq 30' Mixer name : 'Conexant CX20590' Components : 'HDA:14f1506e,17aa5019,0013 HDA:80862806,80860101,0010' Controls : 34 Simple ctrls : 11 CurrentDesktop: LXDE Date: Fri Jun 1 10:29:53 2018 HibernationDevice: RESUME=UUID=c49322e5-423f-4d23-b603-862b40c1fa3f MachineType: LENOVO 6885DSG ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic root=UUID=60cc0542-145d-4cbe-ab3a-664740f38105 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-43-generic N/A linux-backports-modules-4.13.0-43-generic N/A linux-firmware 1.169.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2014 dmi.bios.vendor: LENOVO dmi.bios.version: HEET40WW (1.21 ) dmi.board.asset.tag: Not Available dmi.board.name: 6885DSG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrHEET40WW(1.21):bd01/17/2014:svnLENOVO:pn6885DSG:pvrThinkPadEdgeE531:rvnLENOVO:rn6885DSG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad Edge E531 dmi.product.name: 6885DSG dmi.product.version: ThinkPad Edge E531 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774589/+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 1774595] Re: getxattr04 in LTP syscall test failed with X/X-LTS kernel
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Tags added: kernel-da-key -- 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/1774595 Title: getxattr04 in LTP syscall test failed with X/X-LTS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: The "getxattr04" from the LTP syscall tests has failed on a testing node with Xenial kernel installed. Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo "getxattr04" > /tmp/jobs 9. ./runltp -f /tmp/jobs <<>> tag=getxattr04 stime=1527682633 cmdline="getxattr04" contacts="" analysis=exit <<>> tst_device.c:230: INFO: Using test device LTP_DEV='/dev/loop0' tst_mkfs.c:83: INFO: Formatting /dev/loop0 with xfs opts='' extra opts='' tst_test.c:1015: INFO: Timeout per run is 0h 05m 00s getxattr04.c:72: FAIL: getxattr() failed to get an existing attribute Summary: passed 0 failed 1 skipped 0 warnings 0 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=2 <<>> ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-128-generic 4.4.0-128.154 ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131 Uname: Linux 4.4.0-128-generic s390x NonfreeKernelModules: zfs zunicode zcommon znvpair zavl AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Fri Jun 1 03:06:15 2018 HibernationDevice: RESUME=UUID=f578fa27-1d57-41c9-bb1d-7ff64c1c9345 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=f26894a2-496d-4891-aa9a-f66344c9 crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-4.4.0-128-generic N/A linux-backports-modules-4.4.0-128-generic N/A linux-firmware 1.157.19 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1774595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1774337] Re: touchpad not working
The problem so solved.Thanks for the reply On Sat, Jun 2, 2018, 12:41 AM Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.17 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.17-rc7 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1774337 > > Title: > touchpad not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > I have accessed the virtual terminal tty and then onwards my touchpad > has stopped working completely.However an external usb mouse works > fine.I have done all the operations and tried my level best to solve > the issue but none of them are giving the result.Please go through > this issue. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774337/+subscriptions > -- 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/1774337 Title: touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: I have accessed the virtual terminal tty and then onwards my touchpad has stopped working completely.However an external usb mouse works fine.I have done all the operations and tried my level best to solve the issue but none of them are giving the result.Please go through this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774337/+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 1774225] Re: netns: unable to follow an interface that moves to another netns
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: bionic kernel-da-key ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium -- 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/1774225 Title: netns: unable to follow an interface that moves to another netns Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: The following upstream patches are missing (v4.16): 6621dd29eb9b ("dev: advertise the new nsid when the netns iface changes") c36ac8e23073 ("dev: always advertise the new nsid when the netns iface changes") 38e01b30563a ("dev: advertise the new ifindex when the netns iface changes") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6621dd29eb9b https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c36ac8e23073 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=38e01b30563a To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774225/+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