[Kernel-packages] [Bug 1691180] s2lp3 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-79.100-generic/s2lp3__4.4.0-79.100__2017-05-23_06-34-00/results-index.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/1691180 Title: linux: 4.4.0-79.100 -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: In Progress 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 Xenial: New 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: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: 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/1691180/+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 1691180] kernel01 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-79.100-generic/kernel01__4.4.0-79.100__2017-05-23_06-52-00/results-index.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/1691180 Title: linux: 4.4.0-79.100 -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: In Progress 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 Xenial: New 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: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: 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/1691180/+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 1691180] kernel01 (s390x.zVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.4.0-79.100-generic/kernel01__4.4.0-79.100__2017-05-23_06-17-00/results-index.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/1691180 Title: linux: 4.4.0-79.100 -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: In Progress 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 Xenial: New 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: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: 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/1691180/+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 1691180] kernel01 (s390x.zVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.4.0-79.100-generic/kernel01__4.4.0-79.100__2017-05-23_06-54-00/results-index.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/1691180 Title: linux: 4.4.0-79.100 -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: In Progress 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 Xenial: New 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: 1691181 derivatives: 1691182,1691183,1691184,1691186 -- swm properties -- boot-testing-requested: 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/1691180/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
This bug affects my laptop running 17.04, which is an upgrade from an earlier installation. I appear to have no other kernels available in the repository that do not have this bug, and there's no way I'm installing an untrusted kernel. Considering how long this bug has been open, this is getting ridiculous. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1691485] Re: fanatic disable-fan fails without docker installed
SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+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 1691490] Re: fanatic needs to provide storage option for LXD tests
** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691490 Title: fanatic needs to provide storage option for LXD tests Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 The lxc interface changed and now requires --storage when creating a new container. Fix: Get the list of available storages and if this succeeds, use the first one as default for creating the test container. SRU justification: Impact: In Zesty (and later) the CLI of LXD changed. There is now a storage command and creating a container expects the storage pool which should be used to be provided via the --pool argument. Fix: Added a function which returns the first storage pool found by calling "lxc storage list". For older versions of LXD this command fails and returns an error (+ empty string). In that case the "lxc launch" command, which is called later will be used without any --pool option (which is as it was before the CLI change). With this things should work with the old CLI and the new one and regression potential should be low. Testcase: - [with LXD installed and configured] - fanatic enable-fan ... - fanatic enable-lxd ... - fanatic test-local-lxd ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691490/+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 1691485] Re: fanatic disable-fan fails without docker installed
** Also affects: ubuntu-fan (Ubuntu Zesty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+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 1691490] Re: fanatic needs to provide storage option for LXD tests
SRU justification: Impact: In Zesty (and later) the CLI of LXD changed. There is now a storage command and creating a container expects the storage pool which should be used to be provided via the --pool argument. Fix: Added a function which returns the first storage pool found by calling "lxc storage list". For older versions of LXD this command fails and returns an error (+ empty string). In that case the "lxc launch" command, which is called later will be used without any --pool option (which is as it was before the CLI change). With this things should work with the old CLI and the new one and regression potential should be low. Testcase: - [with LXD installed and configured] - fanatic enable-fan ... - fanatic enable-lxd ... - fanatic test-local-lxd ... ** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691490 Title: fanatic needs to provide storage option for LXD tests Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 The lxc interface changed and now requires --storage when creating a new container. Fix: Get the list of available storages and if this succeeds, use the first one as default for creating the test container. SRU justification: Impact: In Zesty (and later) the CLI of LXD changed. There is now a storage command and creating a container expects the storage pool which should be used to be provided via the --pool argument. Fix: Added a function which returns the first storage pool found by calling "lxc storage list". For older versions of LXD this command fails and returns an error (+ empty string). In that case the "lxc launch" command, which is called later will be used without any --pool option (which is as it was before the CLI change). With this things should work with the old CLI and the new one and regression potential should be low. Testcase: - [with LXD installed and configured] - fanatic enable-fan ... - fanatic enable-lxd ... - fanatic test-local-lxd ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691490/+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 1690956] amaura (amd64) - tests ran: 64, failed: 64
tests ran: 64, failed: 64; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/amaura__4.8.0-53.56__2017-05-23_07-19-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1691485] Re: fanatic disable-fan fails without docker installed
** Changed in: ubuntu-fan (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: ubuntu-fan (Ubuntu Zesty) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+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 1690956] kernel02 (s390x.zVM) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_07-26-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] kernel02 (s390x.zVM) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_06-53-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
I second question #56. However, Xenial is not present in the list at the top so maybe it is being overlooked right now? I could not find out how to add it, though. -- 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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1283003] Re: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates
** Also affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- 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/1283003 Title: [Bluetooth + 14.04] Bluetooth headsets are not working after last couple of updates Status in Blueman: New Status in blueman package in Ubuntu: Fix Released Status in bluez package in Ubuntu: Confirmed Status in gnome-bluetooth package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: Hi, I found a bug in Ubuntu 14.04 ! I tried to pair a bluetooth stereo headset (A2DP compatible). The pairing process goes well, but after that I can't select it on the audio preferences. When I select it, it only shows the last selected item options and don't do anything. (he should switch to the headset output). I must mention that it worked very well on Ubuntu 12.04. This bug can be in the bluetooth stack or in unity-control-center or maybe pulseaudio. I actually have no idea. To manage notifications about this bug go to: https://bugs.launchpad.net/blueman/+bug/1283003/+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 1691485] Re: fanatic disable-fan fails without docker installed
** Description changed: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. + + SRU Justification: + + Impact: The function which does docker config updates/tests currently + does not check for the presence of the docker command itself. And while + there are error messages to stderr a call to check for fan being + configured for docker accidentally results in returning true. + + Fix: Adding a check for the docker command being present early in the + function and return an error in that case (which is a false in the is- + docker-configured case). Since the function should really always fail if + there is no docker present the risk of regressions should be low. + + Testcase: + - [docker is not installed] + - fanatic enable-fan ... + - fanatic disable-fan ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+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 1691490] Re: fanatic needs to provide storage option for LXD tests
** Description changed: Release: 17.04/Zesty Version: 0.12.2 The lxc interface changed and now requires --storage when creating a new container. Fix: Get the list of available storages and if this succeeds, use the first one as default for creating the test container. + + SRU justification: + + Impact: In Zesty (and later) the CLI of LXD changed. There is now a + storage command and creating a container expects the storage pool which + should be used to be provided via the --pool argument. + + Fix: Added a function which returns the first storage pool found by + calling "lxc storage list". For older versions of LXD this command fails + and returns an error (+ empty string). In that case the "lxc launch" + command, which is called later will be used without any --pool option + (which is as it was before the CLI change). With this things should work + with the old CLI and the new one and regression potential should be low. + + Testcase: + - [with LXD installed and configured] + - fanatic enable-fan ... + - fanatic enable-lxd ... + - fanatic test-local-lxd ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691490 Title: fanatic needs to provide storage option for LXD tests Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 The lxc interface changed and now requires --storage when creating a new container. Fix: Get the list of available storages and if this succeeds, use the first one as default for creating the test container. SRU justification: Impact: In Zesty (and later) the CLI of LXD changed. There is now a storage command and creating a container expects the storage pool which should be used to be provided via the --pool argument. Fix: Added a function which returns the first storage pool found by calling "lxc storage list". For older versions of LXD this command fails and returns an error (+ empty string). In that case the "lxc launch" command, which is called later will be used without any --pool option (which is as it was before the CLI change). With this things should work with the old CLI and the new one and regression potential should be low. Testcase: - [with LXD installed and configured] - fanatic enable-fan ... - fanatic enable-lxd ... - fanatic test-local-lxd ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691490/+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 1690999] michael (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/michael__4.11.0-3.8__2017-05-23_07-48-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1690999] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/fozzie__4.11.0-3.8__2017-05-23_07-43-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1691490] Re: fanatic needs to provide storage option for LXD tests
Hello Stefan, or anyone else affected, Accepted ubuntu-fan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-fan/0.12.2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691490 Title: fanatic needs to provide storage option for LXD tests Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 The lxc interface changed and now requires --storage when creating a new container. Fix: Get the list of available storages and if this succeeds, use the first one as default for creating the test container. SRU justification: Impact: In Zesty (and later) the CLI of LXD changed. There is now a storage command and creating a container expects the storage pool which should be used to be provided via the --pool argument. Fix: Added a function which returns the first storage pool found by calling "lxc storage list". For older versions of LXD this command fails and returns an error (+ empty string). In that case the "lxc launch" command, which is called later will be used without any --pool option (which is as it was before the CLI change). With this things should work with the old CLI and the new one and regression potential should be low. Testcase: - [with LXD installed and configured] - fanatic enable-fan ... - fanatic enable-lxd ... - fanatic test-local-lxd ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691490/+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 1690956] secchi (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/secchi__4.8.0-53.56__2017-05-23_07-37-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] kernel02 (s390x.zVM) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_07-28-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1691485] Re: fanatic disable-fan fails without docker installed
Hello Stefan, or anyone else affected, Accepted ubuntu-fan into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-fan/0.12.2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to ubuntu-fan in Ubuntu. https://bugs.launchpad.net/bugs/1691485 Title: fanatic disable-fan fails without docker installed Status in ubuntu-fan package in Ubuntu: Fix Committed Status in ubuntu-fan source package in Zesty: Fix Committed Bug description: Release: 17.04/Zesty Version: 0.12.2 When disabling fan, the code tries to check whether docker is configured. However that test is attempting to decide which docker version is installed (in order to handle the new network options). This fails but is incorrectly evaluated as docker being configured. And that prevents fan from being de-configured. Fix: Test for docker being installed and if not return false to the configured check. SRU Justification: Impact: The function which does docker config updates/tests currently does not check for the presence of the docker command itself. And while there are error messages to stderr a call to check for fan being configured for docker accidentally results in returning true. Fix: Adding a check for the docker command being present early in the function and return an error in that case (which is a false in the is- docker-configured case). Since the function should really always fail if there is no docker present the risk of regressions should be low. Testcase: - [docker is not installed] - fanatic enable-fan ... - fanatic disable-fan ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1691485/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_07-44-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] amaura (amd64) - tests ran: 2, failed: 0
tests ran: 2, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/amaura__4.8.0-53.56__2017-05-23_07-39-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Hello Guys Just compiled a new version (4.11.2) for Ubuntu: http://www.nextized.net/repo/linux/ubuntu- linux-4.11.2_ryzen01_amd64_generic.tar.gz Please test it on your plattform. Confirmed works with nvidia 381 Answer from AMD developers who created this module: Hi nextized, This issue has been reported by a few of them, all on the Gigabyte Platform. We aren’t seeing this issue on our reference platform. We are working with other teams to resolve this issue. Thanks, Regards, - Ram -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 64, failed: 0
tests ran: 64, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_07-46-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690999] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/amaura__4.11.0-3.8__2017-05-23_08-00-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
That is great news Marc, thank you for keeping us posted -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1691146] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/gonzo__4.10.0-22.24__2017-05-23_08-11-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: New 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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 kernel-stable-phase-changed:Monday, 22. May 2017 17:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691146/+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 1690956] kernel02 (s390x.zVM) - tests ran: 10, failed: 1
tests ran: 10, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_07-41-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
Hi, Guys, it should be there for both the Yakkety kernel and linux-generic- hwe-16.04: http://kernel.ubuntu.com/git/ubuntu/ubuntu- xenial.git/commit/?id=7570ffb5145abf4413421c154077bc31abad1264 http://kernel.ubuntu.com/git/ubuntu/ubuntu- yakkety.git/commit/?id=5e0bc558603351c8ce573913ba64b16908269b67 There are no HWE packages for non-LTS releases so the fix-commited for Yakkety belongs to both linux-generic in yakkety and linux-generic- hwe-16.04 in xenial as I understand it. $ lsb_release -r Release:16.04 $ apt update $ apt show linux-generic-hwe-16.04 Package: linux-generic-hwe-16.04 Version: 4.8.0.52.23 # <--- the same version as in the ubuntu-xenial git repo tag Priority: optional Section: kernel Source: linux-meta-hwe Origin: Ubuntu Maintainer: Ubuntu Kernel Team Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 10.2 kB Depends: linux-image-generic-hwe-16.04 (= 4.8.0.52.23), linux-headers-generic-hwe-16.04 (= 4.8.0.52.23) Supported: 5y Download-Size: 1,808 B APT-Sources: http://ru.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages Description: Complete Generic Linux kernel and headers This package will always depend on the latest complete generic Linux kernel and headers. -- Or are you saying that this issue is present in 4.4 as well? -- 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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1671360] Re: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen)
Good to know AMD and Gigabyte are working on this issue. So I don't need to send the patch to upstream, but as an Ubuntu sauce patch. -- 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/1671360 Title: System doesn't boot properly on Gigabyte AM4 motherboards (AMD Ryzen) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: I'm trying to run ubuntu on Ryzen 1700x with Gigabyte GA-AB350-gaming-3 motherboard, and it has a load of problems, starting with not being able to boot normally. During normal boot, on 16.10 as well as 17.04 beta: system doesn't boot normally, hangs with a lot of "unexpected irq trap at vector 07" messages displayed. Following advice from various places, I've tried:disable cpu freq governor and cpu handling in acpi settings 1. add "acpi=off" to boot params That helps, allowing me to boot into recovery mode, though it leaves me with system seeing only one core, is really slow and still only boots in recovery mode. 2. Compile own kernel using 4.11.rc1 and disabling cpu freq governor and cpu handling in acpi settings. Boot with "quiet loglevel=3" option. That gets me even further - system sees all cores now. Still only recovery mode though, but its enough to get info for this bug report. Some observed problems: 1. dmesg reports *a lot* of messages like this all the time: [ 163.362068] ->handle_irq(): 87a7e090, [ 163.362081] bad_chained_irq+0x0/0x40 [ 163.362089] ->handle_irq(): 87a7e090, [ 163.362090] amd_gpio_irq_handler+0x0/0x200 [ 163.362090] ->irq_data.chip(): 88587e20, [ 163.362090] ioapic_ir_chip+0x0/0x120 [ 163.362090] ->action(): 884601c0 [ 163.362091]IRQ_NOPROBE set [ 163.362099] ->handle_irq(): 87a7e090, [ 163.362099] amd_gpio_irq_handler+0x0/0x200 [ 163.362100] ->irq_data.chip(): 88587e20, [ 163.362100] ioapic_ir_chip+0x0/0x120 [ 163.362101] ->action(): 884601c0 I've tried to redirect dmesg to a file, stopped after a short while, it generated 400M of those. 2. Systemd cannot start journald. Perhaps because it cannot cope with amount of kernel logs? 3. Looking at pci, I've noticed something called AMDI0040 (/sys/bus/acpi/devices/AMDI0040, path=_SB_.EMMC), among AMDI0010, AMDI0020, AMDI0030. Those however are mentioned in kernel source, kernel and google are completely silent about AMDI0040. Phoronix tested ryzen using different motherboard, and it worked better (though not well), so I suspect it is an issue with motherboard. --- ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2015-08-06 (581 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150728.1) Package: linux (not installed) ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-rc1-custom x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to zesty on 2017-03-03 (6 days ago) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1671360/+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 1690999] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/fozzie__4.11.0-3.8__2017-05-23_08-11-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1690956] kernel02 (s390x.zVM) - tests ran: 15, failed: 3
tests ran: 15, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_08-10-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] kernel02 (s390x.zVM) - tests ran: 16, failed: 0
tests ran: 16, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_08-22-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_07-58-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1692836] [NEW] Dell XPS 9360 wifi 5G performance is poor
Public bug reported: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu) 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/1692836 Title: Dell XPS 9360 wifi 5G performance is poor Status in linux package in Ubuntu: In Progress Bug description: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692836/+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 1691741] Re: Execute NX-protected page - 4.4.0-78-generic - kernel panic
I could be on a wild goose chase here.
But one of the prominent changes between 77 and 78 is the
backing_dev_info element of the queue turning into a pointer.
Part of the "bdi" changes in this bit:
++ * UbuntuKVM guest crashed while running I/O stress test with Ubuntu kernel
++4.4.0-47-generic (LP: #1659111)
I believe from here: https://patchwork.kernel.org/patch/9547199/
For example this:
--- a/drivers/block/drbd/drbd_main.c
+++ b/drivers/block/drbd/drbd_main.c
@@ -2462,7 +2462,7 @@ static int drbd_congested(void *congested_data, int
bdi_bits)
if (get_ldev(device)) {
q = bdev_get_queue(device->ldev->backing_bdev);
- r = bdi_congested(&q->backing_dev_info, bdi_bits);
+ r = bdi_congested(q->backing_dev_info, bdi_bits);
put_ldev(device);
if (r)
reason = 'b';
But if I check the Ubuntu-specific code, that change does not seem to be
done everywhere:
$ zcat linux_4.4.0-78.99.diff.gz | grep bdi_congested.*backing_dev -B2 |
tail -n8
struct request_queue *q = bdev_get_queue(rdev->bdev);
- ret |= bdi_congested(&q->backing_dev_info, bits);
+ ret |= bdi_congested(q->backing_dev_info, bits);
--
+ struct request_queue *q = bdev_get_queue(rs->dev[p].dev->bdev);
+
+ r |= bdi_congested(&q->backing_dev_info, bdi_bits);
Extracting only the "new" files, I find it here indeed:
$ mkdir foo; cd foo
$ patch -tp1 < ../linux_4.4.0-78.99.diff.gz
$ find . -name '*.c' | xargs grep -B2 bdi_congested.*backing_dev_info
./ubuntu/dm-raid4-5/dm-raid4-5.c- struct request_queue *q =
bdev_get_queue(rs->dev[p].dev->bdev);
./ubuntu/dm-raid4-5/dm-raid4-5.c-
./ubuntu/dm-raid4-5/dm-raid4-5.c: r |=
bdi_congested(&q->backing_dev_info, bdi_bits);
This is just an example of course, I believe there could be more "bdi" changes
like that one that haven't been made.
Correct me if I'm wrong though. I've never done any kernel dev, so I
could be way off base here.
--
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/1691741
Title:
Execute NX-protected page - 4.4.0-78-generic - kernel panic
Status in linux package in Ubuntu:
Confirmed
Bug description:
After upgrading from 4.4.0-77 to 4.4.0-78 I started getting kernel
panics.
The crashes do not happen immediately, but have happened generally
after a couple of minutes, sometimes more.
After enabling linux-crashdump stuff, I managed to extract this dmesg.
[ 995.103846] kernel tried to execute NX-protected page - exploit attempt?
(uid: 0)
[ 995.104141] BUG: unable to handle kernel paging request at 88042a284000
[ 995.104407] IP: [] 0x88042a284000
[ 995.104594] PGD 43f20b067 PUD 43f20e067 PMD 42a3da063 PTE 80042a284163
[ 995.104946] Oops: 0011 [#1] SMP
[ 995.105143] Modules linked in: zfs(PO) zunicode(PO) zcommon(PO)
znvpair(PO) spl(O) zavl(PO) ppdev input_leds shpchp serio_raw i2c_piix4 mac_hid
parport_pc parport 8250_fintek autofs4 ttm drm_kms_helper syscopyarea
sysfillrect sysimgblt fb_sys_fops drm psmouse floppy pata_acpi
[ 995.107081] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P O
4.4.0-78-generic #99-Ubuntu
[ 995.107299] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
rel-1.9.3-0-ge2fc41e-prebuilt.qemu-project.org 04/01/2014
[ 995.107573] task: 88042a278000 ti: 88042a28 task.ti:
88042a28
[ 995.108070] RIP: 0010:[] []
0x88042a284000
[ 995.108637] RSP: 0018:88042a283ed0 EFLAGS: 00010082
[ 995.109116] RAX: 0001 RBX: 00e797438af0 RCX:
[ 995.109638] RDX: 0001 RSI: 0083 RDI:
0083
[ 995.110143] RBP: 81f38d40 R08: 000a R09:
[ 995.110665] R10: 00010002a665 R11: 4c00 R12:
88042a283ed0
[ 995.82] R13: 810ff75e R14: R15:
88042a28
[ 995.111733] FS: () GS:88043fc8()
knlGS:
[ 995.112486] CS: 0010 DS: ES: CR0: 8005003b
[ 995.112978] CR2: 88042a284000 CR3: 00043d246000 CR4:
06e0
[ 995.113497] DR0: DR1: DR2:
[ 995.114085] DR3: DR6: fffe0ff0 DR7:
0400
[ 995.114612] Stack:
[ 995.114965] 88042a283f28 810c4736 88042a28
88042a284000
[ 995.116204] ee041b0196f77cc4 a1abbcd2b8b123ce
[ 995.117389]
88042a283f48
[ 995.118425] Call Trace:
[ 995.118811] [] ? cpu_startup_entry+0x176/0x350
[ 995.119293] [] ? start_secondary+0x154/0x190
[ 995.119775]
[Kernel-packages] [Bug 1691146] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/gonzo__4.10.0-22.24__2017-05-23_08-40-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: New 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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 kernel-stable-phase-changed:Monday, 22. May 2017 17:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691146/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
I am running Ubuntu 16.04.2 LTS with 4.8.0-52-generic (#55~16.04.1-Ubuntu) and still have the problem as reported in [#6](https://bugs.launchpad.net/ubuntu/+source/linux-hwe- edge/+bug/1679823/comments/6). Everything should be up to date on my side, linux-generic-hwe-16.04 is of version 4.8.0.52.23. -- 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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1692836] Re: Dell XPS 9360 wifi 5G performance is poor
Test result without patch on comment #1: 11n: Client connecting to 192.168.158.106, TCP port 5001 TCP window size: 416 KByte (WARNING: requested 100 MByte) [ 3] local 192.168.158.107 port 36578 connected with 192.168.158.106 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 24.0 MBytes 20.1 Mbits/sec [ 3] 10.0-20.0 sec 23.5 MBytes 19.7 Mbits/sec [ 3] 20.0-30.0 sec 23.8 MBytes 19.9 Mbits/sec [ 3] 30.0-40.0 sec 22.9 MBytes 19.2 Mbits/sec [ 3] 40.0-50.0 sec 24.1 MBytes 20.2 Mbits/sec [ 3] 50.0-60.0 sec 24.0 MBytes 20.1 Mbits/sec [ 3] 60.0-70.0 sec 19.2 MBytes 16.1 Mbits/sec [ 3] 70.0-80.0 sec 16.0 MBytes 13.4 Mbits/sec [ 3] 80.0-90.0 sec 23.8 MBytes 19.9 Mbits/sec [ 3] 90.0-100.0 sec 23.2 MBytes 19.5 Mbits/sec [ 3] 100.0-110.0 sec 23.1 MBytes 19.4 Mbits/sec [ 3] 110.0-120.0 sec 23.4 MBytes 19.6 Mbits/sec [ 3] 0.0-120.1 sec 271 MBytes 18.9 Mbits/sec 11AC: Client connecting to 192.168.158.106, TCP port 5001 TCP window size: 416 KByte (WARNING: requested 100 MByte) [ 3] local 192.168.158.107 port 36594 connected with 192.168.158.106 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 12.0 MBytes 10.1 Mbits/sec [ 3] 10.0-20.0 sec 12.1 MBytes 10.2 Mbits/sec [ 3] 20.0-30.0 sec 12.6 MBytes 10.6 Mbits/sec [ 3] 30.0-40.0 sec 12.8 MBytes 10.7 Mbits/sec [ 3] 40.0-50.0 sec 9.12 MBytes 7.65 Mbits/sec [ 3] 50.0-60.0 sec 11.8 MBytes 9.86 Mbits/sec [ 3] 60.0-70.0 sec 12.2 MBytes 10.3 Mbits/sec [ 3] 70.0-80.0 sec 11.1 MBytes 9.33 Mbits/sec [ 3] 80.0-90.0 sec 11.8 MBytes 9.86 Mbits/sec [ 3] 90.0-100.0 sec 11.5 MBytes 9.65 Mbits/sec [ 3] 100.0-110.0 sec 11.6 MBytes 9.75 Mbits/sec [ 3] 110.0-120.0 sec 12.5 MBytes 10.5 Mbits/sec [ 3] 0.0-120.2 sec 141 MBytes 9.86 Mbits/sec Test result with the patch on comment #1: 11n: Client connecting to 192.168.158.106, TCP port 5001 TCP window size: 416 KByte (WARNING: requested 100 MByte) [ 3] local 192.168.158.107 port 57252 connected with 192.168.158.106 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 172 MBytes 144 Mbits/sec [ 3] 10.0-20.0 sec 184 MBytes 154 Mbits/sec [ 3] 20.0-30.0 sec 100 MBytes 84.3 Mbits/sec [ 3] 30.0-40.0 sec 172 MBytes 144 Mbits/sec [ 3] 40.0-50.0 sec 187 MBytes 157 Mbits/sec [ 3] 50.0-60.0 sec 180 MBytes 151 Mbits/sec [ 3] 60.0-70.0 sec 177 MBytes 148 Mbits/sec [ 3] 70.0-80.0 sec 190 MBytes 159 Mbits/sec [ 3] 80.0-90.0 sec 179 MBytes 150 Mbits/sec [ 3] 90.0-100.0 sec 183 MBytes 153 Mbits/sec [ 3] 100.0-110.0 sec 180 MBytes 151 Mbits/sec [ 3] 110.0-120.0 sec 185 MBytes 155 Mbits/sec [ 3] 0.0-120.0 sec 2.04 GBytes 146 Mbits/sec 11AC: Client connecting to 192.168.158.106, TCP port 5001 TCP window size: 416 KByte (WARNING: requested 100 MByte) [ 3] local 192.168.158.107 port 57236 connected with 192.168.158.106 port 5001 [ ID] Interval Transfer Bandwidth [ 3] 0.0-10.0 sec 102 MBytes 85.5 Mbits/sec [ 3] 10.0-20.0 sec 79.0 MBytes 66.3 Mbits/sec [ 3] 20.0-30.0 sec 96.0 MBytes 80.5 Mbits/sec [ 3] 30.0-40.0 sec 103 MBytes 86.3 Mbits/sec [ 3] 40.0-50.0 sec 99.0 MBytes 83.0 Mbits/sec [ 3] 50.0-60.0 sec 93.8 MBytes 78.6 Mbits/sec [ 3] 60.0-70.0 sec 93.1 MBytes 78.1 Mbits/sec [ 3] 70.0-80.0 sec 104 MBytes 87.5 Mbits/sec [ 3] 80.0-90.0 sec 107 MBytes 89.9 Mbits/sec [ 3] 90.0-100.0 sec 107 MBytes 89.7 Mbits/sec [ 3] 100.0-110.0 sec 106 MBytes 89.3 Mbits/sec [ 3] 110.0-120.0 sec 106 MBytes 88.7 Mbits/sec [ 3] 0.0-120.0 sec 1.17 GBytes 83.6 Mbits/sec Test comment on client side: u@u-XPS-13-9360:~$ iperf -c serverip -w 100M -t 120 -i 10 -- 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/1692836 Title: Dell XPS 9360 wifi 5G performance is poor Status in linux package in Ubuntu: In Progress Bug description: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692836/+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 1692836] Re: Dell XPS 9360 wifi 5G performance is poor
This patch seems to fix the issue on Ubuntu 4.4 kernel. The ath10k driver structure has been changed after 4.4, so this fix can't apply to 4.8+ kernel, and it looks like should stay in 4.4 kernel only. --- a/drivers/net/wireless/ath/ath10k/mac.c +++ b/drivers/net/wireless/ath/ath10k/mac.c @@ -3563,6 +3563,8 @@ static void ath10k_tx(struct ieee80211_hw *hw, struct ieee80211_hdr *hdr = (struct ieee80211_hdr *)skb->data; __le16 fc = hdr->frame_control; + skb_orphan(skb); + /* We should disable CCK RATE due to P2P */ if (info->flags & IEEE80211_TX_CTL_NO_CCK_RATE) -- 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/1692836 Title: Dell XPS 9360 wifi 5G performance is poor Status in linux package in Ubuntu: In Progress Bug description: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692836/+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 1686268] Re: Backlight brightness level not restored after reboot
I now have Precision 5520 and I can reproduce the issue. I'll take a deeper look on this issue. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1686268 Title: Backlight brightness level not restored after reboot Status in linux package in Ubuntu: In Progress Bug description: I am not sure if this is the right place to report this, so feel free to move it elsewhere. It looks like the systemd-backlight service (/lib/systemd/system /systemd-backlight@.service) does not restore the brightness level (although it saves it before shut-down). However the following command does restore the saved brightness: sudo /lib/systemd/systemd-backlight load backlight:intel_backlight As a temporary solution to automate it at boot I am using the following line added to the root cron: @reboot /lib/systemd/systemd-backlight load backlight:intel_backlight - Ubuntu 4.10.0-20.22-generic 4.10.8 - Gnome 3.24 Please, let me know if you need more info. Thanks. --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dd 1540 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-04-12 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170411) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed root=/dev/mapper/nvme-ubuntu_gnome ro systemd.restore_state=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/29/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.4 dmi.board.name: 06X96V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn06X96V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1686268/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 16, failed: 0
tests ran: 16, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_08-42-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 3, failed: 0
tests ran: 3, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_08-28-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1691973] Re: Ubuntu16.04.03: POWER9 XIVE: msgsnd/doorbell IPI support (backport)
** Also affects: linux (Ubuntu Zesty) 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/1691973 Title: Ubuntu16.04.03: POWER9 XIVE: msgsnd/doorbell IPI support (backport) Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: New Status in linux source package in Zesty: New Bug description: == Comment: #0 - Mauricio Faria De Oliveira - 2017-05-17 09:22:57 == Backport request for 16.04.3 HWE (via 17.04). Commit list: 6b3edefefa67 powerpc/powernv: POWER9 support for msgsnd/doorbell IPI a5adf282461f powerpc/64s: Avoid a branch for ppc_msgsnd b87ac0218355 powerpc: Introduce msgsnd/doorbell barrier primitives b866cc2199d6 powerpc: Change the doorbell IPI calling convention 9b7ff0c6586b powerpc/64s: Add SCV FSCR bit for ISA v3.0 794464f4dea0 powerpc/64s: Add msgp facility unavailable log string Contacts (in CC list): - Breno Leitao == Comment: #1 - Mauricio Faria De Oliveira - 2017-05-17 09:25:16 == Gustavo has been working on this request, and has identified other commits required. He has a working patched kernel and is performing stress test for validating it before submission. == Comment: #2 - Gustavo Luiz Ferreira Walbon - 2017-05-18 15:48:52 == I will submit a patch set in the kernel-team mailing list. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1691973/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
These patches are in 4.8.0-53, which is in -proposed right now. It will be available in -updates with next SRU release if everything goes well. -- 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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1690956] kernel02 (s390x.zVM) - tests ran: 19, failed: 0
tests ran: 19, failed: 0; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_08-26-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 15, failed: 3
tests ran: 15, failed: 3; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_08-45-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1692589] Re: linux: 4.8.0-54.57 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1692589 Title: linux: 4.8.0-54.57 -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: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 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: 1692590 derivatives: 1692592 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1692589/+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 1501884] Re: linux-image-extra-*-generic postrm script runs install actions
@Andy, can you give more information about the trigger implementation you referred to? -- 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/1501884 Title: linux-image-extra-*-generic postrm script runs install actions Status in linux package in Ubuntu: Confirmed Status in linux-lts-trusty package in Ubuntu: Confirmed Bug description: Hi, The postrm maintainer script in the binary packages linux-image- extra-*-generic runs the scripts in /etc/kernel/postinst.d instead of those in /etc/kernel/postrm.d. This can have all sorts of undesirable consequences depending on what other packages add to those directories, but I noticed it because it caused /etc/kernel/postinst.d/apt-auto-removal to make the wrong decisions leaving my servers with only one installed kernel left. Cheers, Seb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1501884/+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 1690999] gonzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/gonzo__4.11.0-3.8__2017-05-23_09-11-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1692836] Re: Dell XPS 9360 wifi 5G performance is poor
** Tags added: originate-from-1669351 somerville -- 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/1692836 Title: Dell XPS 9360 wifi 5G performance is poor Status in HWE Next: New Status in linux package in Ubuntu: In Progress Bug description: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1692836/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
Sorry about the confusion: the commits are tagged with -53 and I mentioned -52 in the apt output. -- 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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1690956] kernel02 (s390x.zVM) - tests ran: 3, failed: 1
tests ran: 3, failed: 1; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/kernel02__4.8.0-53.56__2017-05-23_08-58-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690956] s2lp4 (s390x.LPAR) - tests ran: 141, failed: 28
tests ran: 141, failed: 28; http://kernel.ubuntu.com/testing/4.8.0-53.56-generic/s2lp4__4.8.0-53.56__2017-05-23_08-57-00/results-index.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/1690956 Title: linux: 4.8.0-53.56 -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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1690999] gonzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.11.0-3.8-generic/gonzo__4.11.0-3.8__2017-05-23_09-42-00/results-index.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/1690999 Title: linux: 4.11.0-3.8 -proposed tracker Status in Kernel Development Workflow: In Progress Status in Kernel Development Workflow automated-testing series: New Status in Kernel Development Workflow prepare-package series: Fix Released Status in Kernel Development Workflow prepare-package-meta series: Fix Released Status in Kernel Development Workflow prepare-package-signed series: Fix Released Status in Kernel Development Workflow promote-to-proposed series: Incomplete Status in Kernel Development Workflow promote-to-release series: New Status in Kernel Development Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Artful: Confirmed Bug description: This bug is for tracking the 4.11.0-3.8 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 kernel-phase-changed:Thursday, 18. May 2017 21:50 UTC kernel-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-development-workflow/+bug/1690999/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
The fixes for this issue are also included on Xenial linux-hwe 4.8.0-53.56~16.04.1 which is currently on -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/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1691146] Re: linux: 4.10.0-22.24 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz Zemczak (sil2100) -- 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/1691146 Title: linux: 4.10.0-22.24 -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: New 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 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 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 kernel-stable-phase-changed:Monday, 22. May 2017 17:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691146/+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 1690956] Re: linux: 4.8.0-53.56 -proposed tracker
Regression tests completed successfully. http://kernel.ubuntu.com/testing/delta.html Issues to note: * amd64 - ubuntu_zfs_xfs_generic: failed only on 'amaura' system; dpkg issue. - monotonic_time: gtod failed on some systems, passed on others. * arm64 - ubuntu_lxc: failed on 'ms10-35-mcdivittB0-kernel', passed on 'wright-kernel'. * s390x (zVM) - ubuntu_lxc: failed with 'Too many open files'. Failed before, not a regression. ** Tags added: regression-testing-passed ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690956 Title: linux: 4.8.0-53.56 -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: Fix Released 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 Yakkety: New 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: 1690957 derivatives: 1690958 -- swm properties -- boot-testing-requested: true phase: Uploaded proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1690956/+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 1458204] Re: removing kernels should not require a restart afterward
An exception for linux-image-extra packages can be added in /etc/kernel/postinst.d/update-notifier and in /etc/kernel/postinst.d /unattended-upgrades ** Attachment added: "code to add before touching /var/run/reboot-required in post-installation scripts" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/4881881/+files/addition -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1690796] Re: Kernel bug causes hang
I had a default swapfile as set up by the 17.04 installer. Suspecting that might be the cause I changed and made a swap partition instead. So far so good, haven't had this problem since. @baszoetekouw, am I reading your UdevDB.txt correctly, you're using a swap partition in a LUKS container? Is that a LVM in-between? I don't use LVM. Because if so, my suspicion is that extra layering would cause this. I had swapfile over ext4 over LUKS. You (if I'm reading correctly) have swap partition over LVM over LUKS. Having moved to swap partition over LUKS directly solved my problem, it appears. -- 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/1690796 Title: Kernel bug causes hang Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Very strange bug - occurred several times with the 4.10.0-20 and 4.10.0-21 kernels on the Intel Core i5-2400, but did not appear with the same kernels on the Intel Core 2 Duo E6700. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Just as an FYI to everyone still commenting in this bug, this is fixed in kernel 4.10.0-22.24: https://launchpad.net/ubuntu/+source/linux/4.10.0-22.24 which is in the -proposed repository: https://wiki.ubuntu.com/Testing/EnableProposed and as Seth said in comments above, is scheduled for general release to the -updates repository on June 5: https://lists.ubuntu.com/archives/kernel-sru-announce/2017-May/96.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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- yakkety' to 'verification-done-yakkety'. If the problem still exists, change the tag 'verification-needed-yakkety' to 'verification-failed- yakkety'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-yakkety -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Thanks. Installed and being used on a system that didn't display the fault, to check before inflicting on my other half. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
@ddstreet: It seems it's not yet in the xenial-proposed repo yet, but probably will be there soon-ish I guess? -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1691146] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/amaura__4.10.0-22.24__2017-05-23_12-00-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: New 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 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 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 kernel-stable-phase-changed:Monday, 22. May 2017 17:31 UTC kernel-stable-phase:Uploaded -- swm properties -- boot-testing-requested: true phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1691146/+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 1680904] Re: zesty unable to handle kernel NULL pointer dereference
I've experienced apparently random freezes on 17.04 (kernel 4.10.0-21). It appears to happen when Chrome is active, although Chrome is probably active all the time. There's nothing out of the ordinary in kern.log, but syslog has: May 23 12:44:34 thornback unity-panel-ser[2612]: menus_destroyed: assertion 'IS_WINDOW_MENU(wm)' failed May 23 12:44:34 thornback compiz[2603]: WARN 2017-05-23 12:44:34 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files May 23 12:44:34 thornback systemd[2058]: Stopped target A target that, when running, represents the screen being locked. May 23 12:44:34 thornback systemd[2058]: Stopping Backing Service for the Unity Panel in Lockscreen mode... May 23 12:44:35 thornback systemd[2058]: Stopped Backing Service for the Unity Panel in Lockscreen mode. May 23 12:44:37 thornback systemd-resolved[1197]: Grace period over, resuming full feature set (UDP+EDNS0+DO+LARGE) for DNS server 192.168.0.254. May 23 12:44:37 thornback systemd-resolved[1197]: Using degraded feature set (UDP) for DNS server 192.168.0.254. May 23 12:44:37 thornback compiz[2603]: [4773:4773:0523/124437.777470:ERROR:gpu_child_thread.cc(324)] Exiting GPU process due to errors during initialization I also notice that there are a number of lines containing: compiz[2237]: [1:1:0522/101734.457030:ERROR:KeyboardEventManager.cpp(427)] Not implemented reached in static bool blink::KeyboardEventManager::currentCapsLockState() -- 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/1680904 Title: zesty unable to handle kernel NULL pointer dereference Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: Upgraded to zesty about a week ago. Ran into this on latest kernel. (during high load, nothing in particular seems to cause it to happen). Did not happen with previous (4.10.0.14.16) kernel. Only after update to 4.10.0.15.17, has happened about 3 times since then (or other crashes), this is the one I could capture. kern.log entries below. Let me know if you need anything else from me. Thanks! Apr 7 11:20:28 doe kernel: [26003.796278] BUG: unable to handle kernel NULL pointer dereference at 0018 Apr 7 11:20:28 doe kernel: [26003.796375] IP: gen8_ppgtt_alloc_page_directories.isra.38+0x115/0x250 [i915] Apr 7 11:20:28 doe kernel: [26003.796404] PGD 0 Apr 7 11:20:28 doe kernel: [26003.796405] Apr 7 11:20:28 doe kernel: [26003.796427] Oops: 0002 [#1] SMP Apr 7 11:20:28 doe kernel: [26003.796441] Modules linked in: xt_REDIRECT nf_nat_redirect xt_hl scsi_transport_iscsi binfmt_misc veth ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_filter ccm rfcomm bridge stp llc cmac bnep zfs(PO) zunicode(PO) zavl(PO) zcommon(PO) znvpair(PO) spl(O) nls_iso8859_1 hid_multitouch joydev i2c_designware_platform i2c_designware_core snd_hda_codec_hdmi snd_soc_skl snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_hda_codec_realtek snd_hda_ext_core snd_soc_sst_match snd_hda_codec_generic snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core asus_nb_wmi Apr 7 11:20:28 doe kernel: [26003.796722] snd_hwdep asus_wmi sparse_keymap snd_pcm arc4 snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device iwlmvm snd_timer mac80211 intel_rapl x86_pkg_temp_thermal snd intel_powerclamp uvcvideo coretemp kvm_intel iwlwifi videobuf2_vmalloc kvm videobuf2_memops irqbypass videobuf2_v4l2 intel_cstate videobuf2_core intel_rapl_perf cfg80211 videodev input_leds serio_raw media shpchp soundcore btusb btrtl hci_uart btbcm elan_i2c btqca btintel acpi_als int3403_thermal bluetooth kfifo_buf industrialio mac_hid idma64 mei_me virt_dma intel_pch_thermal acpi_pad int3400_thermal intel_lpss_pci int3402_thermal mei intel_lpss_acpi acpi_thermal_rel processor_thermal_device intel_lpss tpm_crb int340x_thermal_zone int3406_thermal intel_soc_dts_iosf asus_wireless parport_pc ppdev lp parport ip_tables Apr 7 11:20:28 doe kernel: [26003.797026] x_tables autofs4 algif_skcipher af_alg dm_crypt crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc i915 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd i2c_algo_bit drm_kms_helper syscopyarea sysfillrect ahci sysimgblt libahci fb_sys_fops drm wmi i2c_hid hid pinctrl_sunrisepoint video pinctrl_intel fjes Apr 7 11:20:28 doe kernel: [26003.797142] CPU: 0 PID: 8418 Comm: chromium-browse Tainted: P O
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
Is there anyone can help me to answer this problem? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646277 Title: Xenial server 16.04.x will have a black screen after PXE installation Status in debian-installer package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in debian-installer source package in Xenial: Confirmed Status in linux source package in Xenial: Confirmed Bug description: The display will keep black screen after install 16.04.x via PXE(need use "Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen) Quanta team is installing Xenial server using PXE boot. After the installation, the console will show a black screen. Hitting ctl- alt-f1 displays the text mode screen OK. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1646277/+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 1458204] Re: removing kernels should not require a restart afterward
The attachment "code to add before touching /var/run/reboot-required in post-installation scripts" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
I followed the instructions at https://wiki.ubuntu.com/Testing/EnableProposed . I did the "Selective upgrading from -proposed" section before "enabling proposed", then installed 4.10.0-22.24 via synaptic. This went smoothly for me. Thanks @ddstreet for the link. @kwang-m-yi I can't speak for xenial yet, this was for zesty. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
> It seems it's not yet in the xenial-proposed repo yet, but probably will be > there > soon-ish I guess? Yes, there was a technical issue with the build, but it seems minor and so looks like it should be ready soon-ish. It will be listed here when it's in the -proposed repository: https://launchpad.net/ubuntu/+source/linux-hwe-edge/+publishinghistory -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1692896] [NEW] The driver rtl8723be wifi and bt support is very bad for the device [103c:804c]
Public bug reported: HP Notebook 14 Ubuntu 16.04.1 Kernel: 4.4.0-79.100 The wifi and bt support are very bad from 4.4 GA kernel of Xenial. It does not work at all even with the latest proposed kernel 4.4.0-79.100. -- 05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] DeviceName: Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be Kernel modules: rtl8723be ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2161 F pulseaudio /dev/snd/controlC0: ubuntu 2161 F pulseaudio Date: Tue May 23 09:11:44 2017 HibernationDevice: RESUME=UUID=db52001b-dabd-4024-9ce3-8c5151d8dd85 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard Test product name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=c72ae249-273c-4f10-9ce8-5151a0ce2a22 ro rootdelay=60 quiet splash initcall_debug net.ifnames=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-79-generic N/A linux-backports-modules-4.4.0-79-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: Insyde dmi.bios.version: B.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 98.0C dmi.chassis.asset.tag: 75214P108U dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Test product name dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 201505-18323 amd64 apport-bug package-from-proposed taipei-lab 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/1692896 Title: The driver rtl8723be wifi and bt support is very bad for the device [103c:804c] Status in linux package in Ubuntu: New Bug description: HP Notebook 14 Ubuntu 16.04.1 Kernel: 4.4.0-79.100 The wifi and bt support are very bad from 4.4 GA kernel of Xenial. It does not work at all even with the latest proposed kernel 4.4.0-79.100. -- 05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] DeviceName: Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be Kernel modules: rtl8723be ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2161 F pulseaudio /dev/snd/controlC0: ubuntu 2161 F pulseaudio Date: Tue May 23 09:11:44 2017 HibernationDevice: RESUME=UUID=db52001b-dabd-4024-9ce3-8c5151d8dd85 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard Test product name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=c72ae249-273c-4f10-9ce8-5151a0ce2a22 ro rootdelay=60 quiet splash initcall_debug net.ifnames=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-79-generic N/A linux-backports-modules-4.4.0-79-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: Insyde dmi.bios.version: B.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 98.0C dmi.chassis.asset.tag: 75214P108U dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.18:bd07/15/2
[Kernel-packages] [Bug 1690796] Re: Kernel bug causes hang
Yes, I have swap on LVM, of which the PVs are on a crypted fs. So: - /dev/nvme0n1p3 --> cryptsetup(luks) --> /dev/mapper/nvme0n1p3_crypt - /dev/mapper/nvme0n1p3_crypt is the physical volume in my LVM setup - swap is a logical volume in the LVM So that would be quite a curious bug, caused by encrypted swap. -- 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/1690796 Title: Kernel bug causes hang Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1692898] [NEW] Zesty update to 4.10.17 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.17 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.17 stable release shall be applied: * xen: adjust early dom0 p2m handling to xen hypervisor behavior * target: Fix compare_and_write_callback handling for non GOOD status * target/fileio: Fix zero-length READ and WRITE handling * iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement * usb: xhci: bInterval quirk for TI TUSB73x0 * usb: host: xhci: print correct command ring address * USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit * USB: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously * USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications" * staging: vt6656: use off stack for in buffer USB transfers. * staging: vt6656: use off stack for out buffer USB transfers. * staging: gdm724x: gdm_mux: fix use-after-free on module unload * staging: wilc1000: Fix problem with wrong vif index * staging: comedi: jr3_pci: fix possible null pointer dereference * staging: comedi: jr3_pci: cope with jiffies wraparound * usb: misc: add missing continue in switch * usb: gadget: legacy gadgets are optional * usb: Make sure usb/phy/of gets built-in * usb: hub: Fix error loop seen after hub communication errors * usb: hub: Do not attempt to autosuspend disconnected devices * x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup * selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug * x86, pmem: Fix cache flushing for iovec write < 8 bytes * um: Fix PTRACE_POKEUSER on x86_64 * perf/x86: Fix Broadwell-EP DRAM RAPL events * KVM: x86: fix user triggerable warning in kvm_apic_accept_events() * KVM: arm/arm64: fix races in kvm_psci_vcpu_on * arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses * block: fix blk_integrity_register to use template's interval_exp if not 0 * crypto: s5p-sss - Close possible race for completed requests * crypto: algif_aead - Require setkey before accept(2) * crypto: ccp - Use only the relevant interrupt bits * crypto: ccp - Disable interrupts early on unload * crypto: ccp - Change ISR handler method for a v3 CCP * crypto: ccp - Change ISR handler method for a v5 CCP * dm crypt: rewrite (wipe) key in crypto layer using random data * dm era: save spacemap metadata root after the pre-commit * dm rq: check blk_mq_register_dev() return value in dm_mq_init_request_queue() * dm thin: fix a memory leak when passing discard bio down * vfio/type1: Remove locked page accounting workqueue * iov_iter: don't revert iov buffer if csum error * IB/core: Fix sysfs registration error flow * IB/core: For multicast functions, verify that LIDs are multicast LIDs * IB/IPoIB: ibX: failed to create mcg debug file * IB/mlx4: Fix ib device initialization error flow * IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level * IB/hfi1: Prevent kernel QP post send hard lockups * perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms() * perf annotate s390: Fix perf annotate error -95 (4.10 regression) * perf annotate s390: Implement jump types for perf annotate * jbd2: fix dbench4 performance regression for 'nobarrier' mounts * ext4: evict inline data when writing to memory map * orangefs: fix bounds check for listxattr * orangefs: clean up oversize xattr validation * orangefs: do not set getattr_time on orangefs_lookup * orangefs: do not check possibly stale size on truncate * fs/xattr.c: zero out memory copied to userspace in getxattr * ceph: fix memory leak in __ceph_setxattr() * fs/block_dev: always invalidate cleancache in invalidate_bdev() * mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC * Fix match_prepath() * Set unicode flag on cifs echo request to avoid Mac error * SMB3: Work around mount failure when using SMB3 dialect to Macs * CIFS: fix mapping of SFM_SPACE and SFM_PERIOD * cifs: fix leak in FSCTL_ENUM_SNAPS response handling * cifs: fix CIFS_ENUMERATE_SNAPSHOTS oops * CIFS: fix oplock break deadlocks * cifs: fix CIFS_IOC_GET_MNT_INFO oops * CIFS: add misssing SFM mapping for doublequote * ovl: do not set overlay.opaque on non-dir create * padata: free correct variable * md/raid1: avoid reusing a resync bio after error handling. * device-dax: fix cdev leak * device-dax: fix sysfs attribute deadlock * dax: prevent invalidation of mapped DAX entries * mm: fix data corruption due to stale mmap reads * f2fs: fix fs corruption due to zero inode pag
[Kernel-packages] [Bug 1692896] 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/1692896 Title: The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] Status in linux package in Ubuntu: Confirmed Bug description: HP Notebook 14 Ubuntu 16.04.1 Kernel: 4.4.0-79.100 The wifi and bt support are very bad from 4.4 GA kernel of Xenial. It does not work at all even with the latest proposed kernel 4.4.0-79.100. The wireless AP could be shown by network manager, however, the connection will not be established ever. -- 05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] DeviceName: Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be Kernel modules: rtl8723be ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 2161 F pulseaudio /dev/snd/controlC0: ubuntu 2161 F pulseaudio Date: Tue May 23 09:11:44 2017 HibernationDevice: RESUME=UUID=db52001b-dabd-4024-9ce3-8c5151d8dd85 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard Test product name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=c72ae249-273c-4f10-9ce8-5151a0ce2a22 ro rootdelay=60 quiet splash initcall_debug net.ifnames=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-79-generic N/A linux-backports-modules-4.4.0-79-generic N/A linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: Insyde dmi.bios.version: B.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 98.0C dmi.chassis.asset.tag: 75214P108U dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Test product name dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1692896/+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 1692898] Re: Zesty update to 4.10.17 stable release
Skipping "ipmi: Fix kernel panic at ipmi_ssif_thread()" because it was already applied fo bug #1689886 "[SRU][Zesty]QDF2400 kernel oops on ipmitool fru write 0 fru.bin". -- 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/1692898 Title: Zesty update to 4.10.17 stable release Status in linux package in Ubuntu: New Status in linux source package in Zesty: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.17 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.17 stable release shall be applied: * xen: adjust early dom0 p2m handling to xen hypervisor behavior * target: Fix compare_and_write_callback handling for non GOOD status * target/fileio: Fix zero-length READ and WRITE handling * iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement * usb: xhci: bInterval quirk for TI TUSB73x0 * usb: host: xhci: print correct command ring address * USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit * USB: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously * USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications" * staging: vt6656: use off stack for in buffer USB transfers. * staging: vt6656: use off stack for out buffer USB transfers. * staging: gdm724x: gdm_mux: fix use-after-free on module unload * staging: wilc1000: Fix problem with wrong vif index * staging: comedi: jr3_pci: fix possible null pointer dereference * staging: comedi: jr3_pci: cope with jiffies wraparound * usb: misc: add missing continue in switch * usb: gadget: legacy gadgets are optional * usb: Make sure usb/phy/of gets built-in * usb: hub: Fix error loop seen after hub communication errors * usb: hub: Do not attempt to autosuspend disconnected devices * x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup * selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug * x86, pmem: Fix cache flushing for iovec write < 8 bytes * um: Fix PTRACE_POKEUSER on x86_64 * perf/x86: Fix Broadwell-EP DRAM RAPL events * KVM: x86: fix user triggerable warning in kvm_apic_accept_events() * KVM: arm/arm64: fix races in kvm_psci_vcpu_on * arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses * block: fix blk_integrity_register to use template's interval_exp if not 0 * crypto: s5p-sss - Close possible race for completed requests * crypto: algif_aead - Require setkey before accept(2) * crypto: ccp - Use only the relevant interrupt bits * crypto: ccp - Disable interrupts early on unload * crypto: ccp - Change ISR handler method for a v3 CCP * crypto: ccp - Change ISR handler method for a v5 CCP * dm crypt: rewrite (wipe) key in crypto layer using random data * dm era: save spacemap metadata root after the pre-commit * dm rq: check blk_mq_register_dev() return value in dm_mq_init_request_queue() * dm thin: fix a memory leak when passing discard bio down * vfio/type1: Remove locked page accounting workqueue * iov_iter: don't revert iov buffer if csum error * IB/core: Fix sysfs registration error flow * IB/core: For multicast functions, verify that LIDs are multicast LIDs * IB/IPoIB: ibX: failed to create mcg debug file * IB/mlx4: Fix ib device initialization error flow * IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level * IB/hfi1: Prevent kernel QP post send hard lockups * perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms() * perf annotate s390: Fix perf annotate error -95 (4.10 regression) * perf annotate s390: Implement jump types for perf annotate * jbd2: fix dbench4 performance regression for 'nobarrier' mounts * ext4: evict inline data when writing to memory map * orangefs: fix bounds check for listxattr * orangefs: clean up oversize xattr validation * orangefs: do not set getattr_time on orangefs_lookup * orangefs: do not check possibly stale size on truncate * fs/xattr.c: zero out memory copied to userspace in getxattr * ceph: fix memory leak in __ceph_setxattr() * fs/block_dev: always invalidate cleancache in invalidate_bdev() * mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC * Fix match_prepath() * Set unicode flag on cifs echo request to avoid Mac error * SMB3: Work around mount failure when using SMB3 dialect to Macs * CIF
[Kernel-packages] [Bug 1692896] Re: The driver rtl8723be wifi and bt support is very bad for the device [103c:804c]
** Description changed: HP Notebook 14 Ubuntu 16.04.1 Kernel: 4.4.0-79.100 The wifi and bt support are very bad from 4.4 GA kernel of Xenial. It does not work at all even with the latest proposed kernel 4.4.0-79.100. + The wireless AP could be shown by network manager, however, the + connection will not be established ever. + -- 05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] - DeviceName: - Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] - Kernel driver in use: rtl8723be - Kernel modules: rtl8723be + DeviceName: + Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] + Kernel driver in use: rtl8723be + Kernel modules: rtl8723be ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linux 4.4.0-79-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.6 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: ubuntu 2161 F pulseaudio - /dev/snd/controlC0: ubuntu 2161 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: ubuntu 2161 F pulseaudio + /dev/snd/controlC0: ubuntu 2161 F pulseaudio Date: Tue May 23 09:11:44 2017 HibernationDevice: RESUME=UUID=db52001b-dabd-4024-9ce3-8c5151d8dd85 InstallationDate: Installed on 2017-05-21 (1 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard Test product name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic root=UUID=c72ae249-273c-4f10-9ce8-5151a0ce2a22 ro rootdelay=60 quiet splash initcall_debug net.ifnames=0 vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-4.4.0-79-generic N/A - linux-backports-modules-4.4.0-79-generic N/A - linux-firmware1.157.10 + linux-restricted-modules-4.4.0-79-generic N/A + linux-backports-modules-4.4.0-79-generic N/A + linux-firmware1.157.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2015 dmi.bios.vendor: Insyde dmi.bios.version: B.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8133 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 98.0C dmi.chassis.asset.tag: 75214P108U dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrB.18:bd07/15/2015:svnHewlett-Packard:pnTestproductname:pvrType1ProductConfigId:rvnHewlett-Packard:rn8133:rvrKBCVersion98.0C:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: Test product name dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard ** Summary changed: - The driver rtl8723be wifi and bt support is very bad for the device [103c:804c] + The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] ** Summary changed: - The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] + [HP Notebook 14] The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] ** Summary changed: - [HP Notebook 14] The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] + [HP Notebook 14] [Realtek wireless 103c:804c] The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] -- 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/1692896 Title: [HP Notebook 14] [Realtek wireless 103c:804c] The driver rtl8723be wifi and bt support is very bad for the Realtek device [103c:804c] Status in linux package in Ubuntu: Confirmed Bug description: HP Notebook 14 Ubuntu 16.04.1 Kernel: 4.4.0-79.100 The wifi and bt support are very bad from 4.4 GA kernel of Xenial. It does not work at all even with the latest proposed kernel 4.4.0-79.100. The wireless AP could be shown by network manager, however, the connection will not be established ever. -- 05:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723BE PCIe Wireless Network Adapter [10ec:b723] DeviceName: Subsystem: Hewlett-Packard Company RTL8723BE PCIe Wireless Network Adapter [103c:804c] Kernel driver in use: rtl8723be Kernel modules: rtl8723be ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-79-generic 4.4.0-79.100 ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67 Uname: Linu
[Kernel-packages] [Bug 1674838] Re: kernel BUG at /build/linux-7LGLH_/linux-4.10.0/include/linux/swapops.h:129
Not that I can recommend it to anyone else, but I did update to 4.10.0-22.24 on xenial 16.04.2 by pointing the to the zesty 17.04 proposed repo. Hasn't crashed in the 5 minutes I've been running it. Caveat emptor. -- 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/1674838 Title: kernel BUG at /build/linux- 7LGLH_/linux-4.10.0/include/linux/swapops.h:129 Status in linux package in Ubuntu: Fix Committed Status in linux-hwe-edge package in Ubuntu: In Progress Status in linux source package in Zesty: Fix Committed Status in linux-hwe-edge source package in Zesty: Fix Committed Bug description: Randomly, khugepaged process will take 100% CPU, and I can only restart the computer to recover it. Relevant dmesg attached (dmesg_crash.txt). ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-14-generic 4.10.0-14.16 ProcVersionSignature: Ubuntu 4.10.0-14.16-generic 4.10.3 Uname: Linux 4.10.0-14-generic x86_64 ApportVersion: 2.20.4-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mathieu2221 F pulseaudio /dev/snd/pcmC1D0p: mathieu2221 F...m pulseaudio /dev/snd/controlC1: mathieu2221 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Tue Mar 21 23:03:23 2017 HibernationDevice: RESUME=UUID=67e78e4c-94ee-447c-ae60-4387dae296dd InstallationDate: Installed on 2016-01-31 (415 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160131) MachineType: LENOVO 20344 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic root=UUID=b982929e-11d0-4984-885c-6c9daba24836 ro noprompt quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-14-generic N/A linux-backports-modules-4.10.0-14-generic N/A linux-firmware 1.164 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-03-02 (19 days ago) dmi.bios.date: 10/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 96CN29WW(V1.15) dmi.board.asset.tag: 31900058WIN dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 13 dmi.modalias: dmi:bvnLENOVO:bvr96CN29WW(V1.15):bd10/16/2014:svnLENOVO:pn20344:pvrLenovoYoga213:rvnLENOVO:rnINVALID:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoYoga213: dmi.product.name: 20344 dmi.product.version: Lenovo Yoga 2 13 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838/+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 1692900] [NEW] Xenial update to 4.4.69 stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.4.69 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.4.69 stable release shall be applied: * xen: adjust early dom0 p2m handling to xen hypervisor behavior * target: Fix compare_and_write_callback handling for non GOOD status * target/fileio: Fix zero-length READ and WRITE handling * target: Convert ACL change queue_depth se_session reference usage * iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement * usb: host: xhci: print correct command ring address * USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit * USB: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously * staging: vt6656: use off stack for in buffer USB transfers. * staging: vt6656: use off stack for out buffer USB transfers. * staging: gdm724x: gdm_mux: fix use-after-free on module unload * staging: comedi: jr3_pci: fix possible null pointer dereference * staging: comedi: jr3_pci: cope with jiffies wraparound * usb: misc: add missing continue in switch * usb: Make sure usb/phy/of gets built-in * usb: hub: Fix error loop seen after hub communication errors * usb: hub: Do not attempt to autosuspend disconnected devices * x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup * selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug * x86, pmem: Fix cache flushing for iovec write < 8 bytes * um: Fix PTRACE_POKEUSER on x86_64 * KVM: x86: fix user triggerable warning in kvm_apic_accept_events() * KVM: arm/arm64: fix races in kvm_psci_vcpu_on * block: fix blk_integrity_register to use template's interval_exp if not 0 * crypto: algif_aead - Require setkey before accept(2) * dm era: save spacemap metadata root after the pre-commit * vfio/type1: Remove locked page accounting workqueue * IB/core: Fix sysfs registration error flow * IB/IPoIB: ibX: failed to create mcg debug file * IB/mlx4: Fix ib device initialization error flow * IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level * ext4: evict inline data when writing to memory map * fs/xattr.c: zero out memory copied to userspace in getxattr * ceph: fix memory leak in __ceph_setxattr() * fs/block_dev: always invalidate cleancache in invalidate_bdev() * Set unicode flag on cifs echo request to avoid Mac error * SMB3: Work around mount failure when using SMB3 dialect to Macs * CIFS: fix mapping of SFM_SPACE and SFM_PERIOD * cifs: fix CIFS_IOC_GET_MNT_INFO oops * CIFS: add misssing SFM mapping for doublequote * padata: free correct variable * arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses * serial: samsung: Use right device for DMA-mapping calls * serial: omap: fix runtime-pm handling on unbind * serial: omap: suspend device on probe errors * tty: pty: Fix ldisc flush after userspace become aware of the data already * Bluetooth: Fix user channel for 32bit userspace on 64bit kernel * Bluetooth: hci_bcm: add missing tty-device sanity check * Bluetooth: hci_intel: add missing tty-device sanity check * mac80211: pass RX aggregation window size to driver * mac80211: pass block ack session timeout to to driver * mac80211: RX BA support for sta max_rx_aggregation_subframes * wlcore: Pass win_size taken from ieee80211_sta to FW * wlcore: Add RX_BA_WIN_SIZE_CHANGE_EVENT event * ipmi: Fix kernel panic at ipmi_ssif_thread() * Linux 4.4.69 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Stefan Bader (smb) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The 4.4.69 upstream stable + patch set is now available. It should be included in the Ubuntu + kernel as well. - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is
[Kernel-packages] [Bug 1692898] Re: Zesty update to 4.10.17 stable release
** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Status: New => In Progress ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Stefan Bader (smb) -- 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/1692898 Title: Zesty update to 4.10.17 stable release Status in linux package in Ubuntu: New Status in linux source package in Zesty: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The 4.10.17 upstream stable patch set is now available. It should be included in the Ubuntu kernel as well. git://git.kernel.org/ TEST CASE: TBD The following patches from the 4.10.17 stable release shall be applied: * xen: adjust early dom0 p2m handling to xen hypervisor behavior * target: Fix compare_and_write_callback handling for non GOOD status * target/fileio: Fix zero-length READ and WRITE handling * iscsi-target: Set session_fall_back_to_erl0 when forcing reinstatement * usb: xhci: bInterval quirk for TI TUSB73x0 * usb: host: xhci: print correct command ring address * USB: serial: ftdi_sio: add device ID for Microsemi/Arrow SF2PLUS Dev Kit * USB: Proper handling of Race Condition when two USB class drivers try to call init_usb_class simultaneously * USB: Revert "cdc-wdm: fix "out-of-sync" due to missing notifications" * staging: vt6656: use off stack for in buffer USB transfers. * staging: vt6656: use off stack for out buffer USB transfers. * staging: gdm724x: gdm_mux: fix use-after-free on module unload * staging: wilc1000: Fix problem with wrong vif index * staging: comedi: jr3_pci: fix possible null pointer dereference * staging: comedi: jr3_pci: cope with jiffies wraparound * usb: misc: add missing continue in switch * usb: gadget: legacy gadgets are optional * usb: Make sure usb/phy/of gets built-in * usb: hub: Fix error loop seen after hub communication errors * usb: hub: Do not attempt to autosuspend disconnected devices * x86/boot: Fix BSS corruption/overwrite bug in early x86 kernel startup * selftests/x86/ldt_gdt_32: Work around a glibc sigaction() bug * x86, pmem: Fix cache flushing for iovec write < 8 bytes * um: Fix PTRACE_POKEUSER on x86_64 * perf/x86: Fix Broadwell-EP DRAM RAPL events * KVM: x86: fix user triggerable warning in kvm_apic_accept_events() * KVM: arm/arm64: fix races in kvm_psci_vcpu_on * arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses * block: fix blk_integrity_register to use template's interval_exp if not 0 * crypto: s5p-sss - Close possible race for completed requests * crypto: algif_aead - Require setkey before accept(2) * crypto: ccp - Use only the relevant interrupt bits * crypto: ccp - Disable interrupts early on unload * crypto: ccp - Change ISR handler method for a v3 CCP * crypto: ccp - Change ISR handler method for a v5 CCP * dm crypt: rewrite (wipe) key in crypto layer using random data * dm era: save spacemap metadata root after the pre-commit * dm rq: check blk_mq_register_dev() return value in dm_mq_init_request_queue() * dm thin: fix a memory leak when passing discard bio down * vfio/type1: Remove locked page accounting workqueue * iov_iter: don't revert iov buffer if csum error * IB/core: Fix sysfs registration error flow * IB/core: For multicast functions, verify that LIDs are multicast LIDs * IB/IPoIB: ibX: failed to create mcg debug file * IB/mlx4: Fix ib device initialization error flow * IB/mlx4: Reduce SRIOV multicast cleanup warning message to debug level * IB/hfi1: Prevent kernel QP post send hard lockups * perf auxtrace: Fix no_size logic in addr_filter__resolve_kernel_syms() * perf annotate s390: Fix perf annotate error -95 (4.10 regression) * perf annotate s390: Implement jump types for perf annotate * jbd2: fix dbench4 performance regression for 'nobarrier' mounts * ext4: evict inline data when writing to memory map * orangefs: fix bounds check for listxattr * orangefs: clean up oversize xattr validation * orangefs: do not set getattr_time on orangefs_lookup * orangefs: do not check possibly stale size on truncate * fs/xattr.c: zero out memory copied to userspace in getxattr * ceph: fix memory leak in __ceph_setxattr() * fs/block_dev: always invalidate cleancache in invalidate_bdev() * mm: prevent potential recursive reclaim due to clearing PF_MEMALLOC * Fix match_prepath() * Set unicode flag on cifs echo request to avoid Mac error * SMB3
[Kernel-packages] [Bug 1690796] Re: Kernel bug causes hang
I don't think it's encrypted swap per se, as I also have it, I think it's additional layering. In my case: * sw -> LUKS -> sda5 = OK * swapfile -> ext4 (root fs) -> LUKS -> sda2 = problem And from what I see in your case: * sw -> LUKS -> LVM -> nvme0n1p3 = problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690796 Title: Kernel bug causes hang Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1690796] Re: Kernel bug causes hang
Oh also another common thing we have is, both devices are SSDs. My LUKS containers are open with 'discard' option. -- 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/1690796 Title: Kernel bug causes hang Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1690796] Re: Kernel bug causes hang
Pardon the comment spam, I made a mistake, your use case is * sw -> LVM -> LUKS -> nvme so both our failure cases have an extra layer between swap and LUKS -- 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/1690796 Title: Kernel bug causes hang Status in linux package in Ubuntu: Incomplete Bug description: My machine just crashed. Looking at the journalctl output (after a reboot, as the machine was unresponsive), I got this: mei 15 12:53:23 regan kernel: kernel BUG at /build/linux- 2NWldV/linux-4.10.0/include/linux/swapops.h:129! I'll attach the full log. I'm running Zesty with this kernel: Linux regan 4.10.0-20-generic #22-Ubuntu SMP Thu Apr 20 09:22:42 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux --- ApportVersion: 2.20.4-0ubuntu4.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bas2203 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.04 HibernationDevice: RESUME=UUID=ca0f5952-e241-4ec9-80c0-f7c596dbad03 InstallationDate: Installed on 2016-12-22 (143 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: Dell Inc. Latitude E7470 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic root=/dev/mapper/hostname-root ro nosplash acpi_backlight=vendor ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8 RelatedPackageVersions: linux-restricted-modules-4.10.0-20-generic N/A linux-backports-modules-4.10.0-20-generic N/A linux-firmware 1.164.1 Tags: zesty Uname: Linux 4.10.0-20-generic x86_64 UnreportableReason: The report belongs to a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare src sudo vboxusers wireshark _MarkForUpload: False dmi.bios.date: 11/09/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.3 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.3:bd11/09/2016:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7470 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1690796/+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 1692907] [NEW] blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument
You have been subscribed to a public bug: > ---Problem Description--- > Getting the following error during ziomon execution: > > ziomon -i 2 -d 1 -l 1M -o ziomonlog /dev/sdb /dev/sda > Check devices...done > Estimated maximum disk space required for log data: approx. <1 MBytes > Collecting configuration data...done > Start data collection processes...done > Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument > FAILED to start thread on CPU 7: 22/Invalid argument > FAILED to start thread on CPU 8: 22/Invalid argument > FAILED to start thread on CPU 9: 22/Invalid argument Could you ensure that the cpuplugd is not running while using ziomon? == >Yes, cpuplugd is not running during ziomon execution. I have also called blktrace directly and got the same errors: s35lp49:~ # blktrace -w 1 -d /dev/sda FAILED to start thread on CPU 6: 22/Invalid argument FAILED to start thread on CPU 7: 22/Invalid argument FAILED to start thread on CPU 8: 22/Invalid argument FAILED to start thread on CPU 9: 22/Invalid argument I found an interesting thing. I installed the blktrace source and I found several patches in there, one of them is exactly the opposite of what this patch proposes: use configured cpus instead of online cpus: blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch Without applying the patches: s35lp49:/usr/src/packages/SOURCES # ls -l b*patch -rw-r--r-- 1 root root 3171 Dec 15 2008 blkparse-track-smallest-sequence-read-per-device.patch -rw-r--r-- 1 root root 3748 Aug 20 2015 blktrace-blkreplay-convert-to-use-a-dynamic-cpu_set_t.patch -rw-r--r-- 1 root root 1223 Aug 20 2015 blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch -rw-r--r-- 1 root root 1155 Aug 20 2015 btreplay-fix-typo-in-scaling-up-the-dynamic-cpu-set-size.patch -rw-r--r-- 1 root root 1593 Aug 20 2015 btreplay-machines-are-now-large-enough-that-holes-need-to-be-dealt-with.patch -rw-r--r-- 1 root root 1292 Aug 20 2015 btreplay-use-sysconf-to-get-the-number-of-configured-cpus.patch or if I apply the patch proposed in: http://git.kernel.dk/?p=blktrace.git;a=commit;h=80c4041b2e7a7d5afb75df563bf51bb27773c095 after applying the patches mentioned above, blktrace works: s35lp49:/usr/src/packages/SOURCES/blktrace-1.0.5 # ./blktrace -w 1 -d /dev/sda === sda === CPU 0:0 events,0 KiB data CPU 1:1 events,1 KiB data CPU 2:0 events,0 KiB data CPU 3:0 events,0 KiB data CPU 4:0 events,0 KiB data CPU 5:0 events,0 KiB data Total: 1 events (dropped 0),1 KiB data It seems to me that blktrace-use-number-of-configured-cpus-instead-of- online-cpus.patch was the cause of this bug. > Common code specific ! ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-152254 severity-medium targetmilestone-inin--- -- blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument https://bugs.launchpad.net/bugs/1692907 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 1692907] [NEW] blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument
Public bug reported: > ---Problem Description--- > Getting the following error during ziomon execution: > > ziomon -i 2 -d 1 -l 1M -o ziomonlog /dev/sdb /dev/sda > Check devices...done > Estimated maximum disk space required for log data: approx. <1 MBytes > Collecting configuration data...done > Start data collection processes...done > Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument > FAILED to start thread on CPU 7: 22/Invalid argument > FAILED to start thread on CPU 8: 22/Invalid argument > FAILED to start thread on CPU 9: 22/Invalid argument Could you ensure that the cpuplugd is not running while using ziomon? == >Yes, cpuplugd is not running during ziomon execution. I have also called blktrace directly and got the same errors: s35lp49:~ # blktrace -w 1 -d /dev/sda FAILED to start thread on CPU 6: 22/Invalid argument FAILED to start thread on CPU 7: 22/Invalid argument FAILED to start thread on CPU 8: 22/Invalid argument FAILED to start thread on CPU 9: 22/Invalid argument I found an interesting thing. I installed the blktrace source and I found several patches in there, one of them is exactly the opposite of what this patch proposes: use configured cpus instead of online cpus: blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch Without applying the patches: s35lp49:/usr/src/packages/SOURCES # ls -l b*patch -rw-r--r-- 1 root root 3171 Dec 15 2008 blkparse-track-smallest-sequence-read-per-device.patch -rw-r--r-- 1 root root 3748 Aug 20 2015 blktrace-blkreplay-convert-to-use-a-dynamic-cpu_set_t.patch -rw-r--r-- 1 root root 1223 Aug 20 2015 blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch -rw-r--r-- 1 root root 1155 Aug 20 2015 btreplay-fix-typo-in-scaling-up-the-dynamic-cpu-set-size.patch -rw-r--r-- 1 root root 1593 Aug 20 2015 btreplay-machines-are-now-large-enough-that-holes-need-to-be-dealt-with.patch -rw-r--r-- 1 root root 1292 Aug 20 2015 btreplay-use-sysconf-to-get-the-number-of-configured-cpus.patch or if I apply the patch proposed in: http://git.kernel.dk/?p=blktrace.git;a=commit;h=80c4041b2e7a7d5afb75df563bf51bb27773c095 after applying the patches mentioned above, blktrace works: s35lp49:/usr/src/packages/SOURCES/blktrace-1.0.5 # ./blktrace -w 1 -d /dev/sda === sda === CPU 0:0 events,0 KiB data CPU 1:1 events,1 KiB data CPU 2:0 events,0 KiB data CPU 3:0 events,0 KiB data CPU 4:0 events,0 KiB data CPU 5:0 events,0 KiB data Total: 1 events (dropped 0),1 KiB data It seems to me that blktrace-use-number-of-configured-cpus-instead-of- online-cpus.patch was the cause of this bug. > Common code specific ! ** Affects: ubuntu-z-systems Importance: Undecided Status: New ** Affects: blktrace (Ubuntu) Importance: Undecided Assignee: Skipper Bug Screeners (skipper-screen-team) Status: New ** Tags: architecture-s39064 bugnameltc-152254 severity-medium targetmilestone-inin--- ** Tags added: architecture-s39064 bugnameltc-152254 severity-medium targetmilestone-inin--- ** Changed in: ubuntu Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team) ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1692907 Title: blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument Status in Ubuntu on IBM z Systems: New Status in blktrace package in Ubuntu: New Bug description: > ---Problem Description--- > Getting the following error during ziomon execution: > > ziomon -i 2 -d 1 -l 1M -o ziomonlog /dev/sdb /dev/sda > Check devices...done > Estimated maximum disk space required for log data: approx. <1 MBytes > Collecting configuration data...done > Start data collection processes...done > Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument > FAILED to start thread on CPU 7: 22/Invalid argument > FAILED to start thread on CPU 8: 22/Invalid argument > FAILED to start thread on CPU 9: 22/Invalid argument Could you ensure that the cpuplugd is not running while using ziomon? == >Yes, cpuplugd is not running during ziomon execution. I have also called blktrace directly and got the same errors: s35lp49:~ # blktrace -w 1 -d /dev/sda FAILED to start thread on CPU 6: 22/Invalid argument FAILED to start thread on CPU 7: 22/Invalid argument FAILED to start thread on CPU 8: 22/Invalid argument FAILED to start thread on CPU 9: 22/Invalid argument I found an interesting thing. I installed the blktrace source and I found several patches in there, one of them is exactly the opposite of what this patch proposes: use configured cpus instead o
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
The new kernel fixed all of my FN keys on a G752VS, however the Elantech 1203 touchpad is still dead. As the user above me, the following lines appear while booting: [6.110760] i2c_designware i2c_designware.1: controller timed out [6.110768] i2c_hid i2c-ELAN1203:00: hid_descr_cmd failed Once booted I no longer see this in xinput: ELAN1203:00 04F3:301E Touchpad id=15 [slave pointer (2)] With the previous kernel 4.10 this was still present in xinput. Also when I press the FN key F9 to enable/disable touchpad, the system displays only disable. -- 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/1653456 Title: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04) Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Non-Optimus laptop ASUS G752VS-GC063D-CST256. 17.3" FHD LED 1920x1080, Intel Core i7-6700HQ (3.50Ghz), 16GB DDR4, 256GB M.2 NVMe SSD + 1TB HDD 7200rpm, DVDRW-DL, Nvidia GTX1070 8GB GDDR5, Wifi 802.11ac+Bluetooth 4.1 (Dual band) 2*2, Gb LAN, HDMI, mDP, Intel WiDi, USB3.0 x4, USB3.1-Type C(Gen2) with Thunderbolt, HD webcam, Illuminated KB, no OS. Hello, after experimenting few days ago with Ubuntu 16.04.1, 16.10 and 17.04, among other problems I found that touchpad and Fn keys (all except volume control) doesn't work on my brand new ASUS G752VS. It is very hard even to try Ubuntu 16.10 and 17.04 because of the missing mouse pointer. This problem must be related to a video driver because if after installing one is capable to install Nvidia drivers - problem is solved. This problem doesn't exist both while trying and installing Ubuntu 16.04.1! I'm currently on Windows 10, and this bug report is made from Ubuntu 16.04.1 LiveCD. dmesg | grep -i elan [ 101.082929] input: ELAN1203:00 04F3:3043 Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1203:00/0018:04F3:3043.0007/input/input11 [ 101.082998] hid-multitouch 0018:04F3:3043.0007: input,hidraw6: I2C HID v1.00 Mouse [ELAN1203:00 04F3:3043] on i2c-ELAN1203:00 xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ G-SPY USB Gaming Mouse id=10 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=13 [slave pointer (2)] ⎜ ↳ ASASTeK COMPUTER INC. ROG MacroKey id=14 [slave pointer (2)] ⎜ ↳ ELAN1203:00 04F3:3043 Touchpad id=15 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ G-SPY USB Gaming Mouse id=9[slave keyboard (3)] ↳ USB2.0 HD UVC WebCamid=11 [slave keyboard (3)] ↳ ASASTeK COMPUTER INC. ROG MacroKey id=12 [slave keyboard (3)] ↳ Asus WMI hotkeysid=16 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=17 [slave keyboard (3)] cat /proc/bus/input/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:12/LNXVIDEO:01/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0
[Kernel-packages] [Bug 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
With 4.8.0-53 in -proposed, e1000e works without any problem. $ uname -a Linux cola 4.8.0-53-generic #56-Ubuntu SMP Tue May 16 00:23:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux $ ifconfig eth1 ... UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1692907] Re: blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument
** Package changed: linux (Ubuntu) => blktrace (Ubuntu) ** Also affects: ubuntu-z-systems 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/1692907 Title: blktrace: ziomon FAILED to start thread on CPU x: 22/Invalid argument Status in Ubuntu on IBM z Systems: New Status in blktrace package in Ubuntu: New Bug description: > ---Problem Description--- > Getting the following error during ziomon execution: > > ziomon -i 2 -d 1 -l 1M -o ziomonlog /dev/sdb /dev/sda > Check devices...done > Estimated maximum disk space required for log data: approx. <1 MBytes > Collecting configuration data...done > Start data collection processes...done > Collecting data...FAILED to start thread on CPU 6: 22/Invalid argument > FAILED to start thread on CPU 7: 22/Invalid argument > FAILED to start thread on CPU 8: 22/Invalid argument > FAILED to start thread on CPU 9: 22/Invalid argument Could you ensure that the cpuplugd is not running while using ziomon? == >Yes, cpuplugd is not running during ziomon execution. I have also called blktrace directly and got the same errors: s35lp49:~ # blktrace -w 1 -d /dev/sda FAILED to start thread on CPU 6: 22/Invalid argument FAILED to start thread on CPU 7: 22/Invalid argument FAILED to start thread on CPU 8: 22/Invalid argument FAILED to start thread on CPU 9: 22/Invalid argument I found an interesting thing. I installed the blktrace source and I found several patches in there, one of them is exactly the opposite of what this patch proposes: use configured cpus instead of online cpus: blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch Without applying the patches: s35lp49:/usr/src/packages/SOURCES # ls -l b*patch -rw-r--r-- 1 root root 3171 Dec 15 2008 blkparse-track-smallest-sequence-read-per-device.patch -rw-r--r-- 1 root root 3748 Aug 20 2015 blktrace-blkreplay-convert-to-use-a-dynamic-cpu_set_t.patch -rw-r--r-- 1 root root 1223 Aug 20 2015 blktrace-use-number-of-configured-cpus-instead-of-online-cpus.patch -rw-r--r-- 1 root root 1155 Aug 20 2015 btreplay-fix-typo-in-scaling-up-the-dynamic-cpu-set-size.patch -rw-r--r-- 1 root root 1593 Aug 20 2015 btreplay-machines-are-now-large-enough-that-holes-need-to-be-dealt-with.patch -rw-r--r-- 1 root root 1292 Aug 20 2015 btreplay-use-sysconf-to-get-the-number-of-configured-cpus.patch or if I apply the patch proposed in: http://git.kernel.dk/?p=blktrace.git;a=commit;h=80c4041b2e7a7d5afb75df563bf51bb27773c095 after applying the patches mentioned above, blktrace works: s35lp49:/usr/src/packages/SOURCES/blktrace-1.0.5 # ./blktrace -w 1 -d /dev/sda === sda === CPU 0:0 events,0 KiB data CPU 1:1 events,1 KiB data CPU 2:0 events,0 KiB data CPU 3:0 events,0 KiB data CPU 4:0 events,0 KiB data CPU 5:0 events,0 KiB data Total: 1 events (dropped 0),1 KiB data It seems to me that blktrace-use-number-of-configured-cpus-instead-of- online-cpus.patch was the cause of this bug. > Common code specific ! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1692907/+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 1691146] Re: linux: 4.10.0-22.24 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-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 => 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 backports: 1691149,1691152 derivatives: 1691153 - kernel-stable-phase-changed:Monday, 22. May 2017 17:31 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Tuesday, 23. May 2017 14:31 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 backports: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Tuesday, 23. May 2017 14:31 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 in Ubuntu. https://bugs.launchpad.net/bugs/1691146 Title: linux: 4.10.0-22.24 -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: 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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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 1679823] Re: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS
Works inside a virtual machine Linux vt-xenial-server 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:14:44 UTC 2017 i686 i686 i686 GNU/Linux ifconfig lan1 … UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1679823 Title: bond0: Invalid MTU 9000 requested, hw max 1500 with kernel 4.8 / 4.10 in XENIAL LTS Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Status in linux source package in Yakkety: Fix Committed Status in linux-hwe source package in Yakkety: Fix Committed Status in linux-hwe-edge source package in Yakkety: Fix Committed Status in linux source package in Zesty: In Progress Status in linux-hwe source package in Zesty: Confirmed Status in linux-hwe-edge source package in Zesty: Confirmed Bug description: Since I upgraded the kernel from linux-image-4.8.0-46-generic to linux-image-extra-4.10.0-14-generic I'm facing an issue when I want to change the MTU. It seems to be known bug already fixed: https://bugzilla.kernel.org/show_bug.cgi?id=194763 # ip l sh eno49 2: eno49: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh eno50 3: eno50: mtu 9000 qdisc mq master bond0 state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l sh bond0 6: bond0: mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000 link/ether 5c:b9:01:8a:61:e9 brd ff:ff:ff:ff:ff:ff # ip l set mtu 9000 bond0 RTNETLINK answers: Invalid argument root@controller002[SRV][YUL]:~# tail -1 /var/log/syslog Apr 4 19:36:28 controller002 kernel: [ 8869.077853] bond0: Invalid MTU 9000 requested, hw max 1500 # modinfo ixgbe filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/ethernet/intel/ixgbe/ixgbe.ko version:4.4.0-k license:GPL description:Intel(R) 10 Gigabit PCI Express Network Driver # modinfo bonding filename: /lib/modules/4.10.0-14-generic/kernel/drivers/net/bonding/bonding.ko author: Thomas Davis, tada...@lbl.gov and many others description:Ethernet Channel Bonding Driver, v3.7.1 version:3.7.1 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1679823/+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 1615774] Re: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested
Thank you for the tip, Kai-Heng Feng, I will observere what happens, when I remove "pcie_aspm=force". I added it long time ago, Apr 2014. Reason was, that my notebook then, a Dell M2400, sometimes didn't survive resume after standby (1 of 10 times maybe). It just crashed, black screen, X11 dead. The option didn't really help that days, but it survived my config somehow ;-) However, even today with Dell E7450 I sometimes have weird situations, where system is gone that way without any "visible" cause. Last time in April with 4.10.0-8.slh.1-aptosid-amd64 (I am now on 4.11.0-0.slh.1 -aptosid-amd64), in the middle of using it, doing "nothing special". I must say, that I am using the notebook in a very "dynamic" way, that may be unusual to others: (*) I use it constantly using standby/resume, when I don't need it (*) Rebooting only on dist-upgrades, kernel-upgrades or some backups (*) Constantly plug/unplugging HW to notebook (USB-Devices, Dockingstation, ext. Monitors) I had issues, where it didn't seem to be good, to have system in a docking station, then send it to standby, remove it from dock, and resume system. I guess, that shouldn't make any difference but I try to avoid that, after some crashes . Since my last post, I didn't experience the vanishing WLAN again. Situation didn't get better overall with USB3-Devices (I miss eSata-ports). I cannot use double-bay-USB3-Adapters. Rsyncing two discs leads to Disconnects sooner or later under heavy load. Or accessing a USB2-CD/DVD and having in parallel I/O to a USB3-connected HDD, I repeatedly had the situation of USB3-HDD disconnecting. When I reconnect, and havingsame workload again, no problem for hours. And seeing USB3 having influence on your WLAN is weird :-) But I am just guessing. I will remove unnecessary kernel-parameter first and then observe. Thank you for helping! -- 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/1615774 Title: iwlwifi queue stuck, Microcode SW error detected, "ieee80211 phy0: Hardware restart was requested Status in linux package in Ubuntu: Incomplete Bug description: Recently (maybe since updating to linux-image-4.4.0-34-generic:amd64 (4.4.0-34.53), i've not used this notebook to much lately), my wifi connection is unstable, often hangs and therefore spread a lot of bad karma to all networking applications. My log shows entries of the following pattern Aug 22 20:12:56 nb-voer kernel: [ 1792.518944] iwlwifi :02:00.0: Queue 2 stuck for 1 ms. Aug 22 20:12:56 nb-voer kernel: [ 1792.518962] iwlwifi :02:00.0: Current SW read_ptr 86 write_ptr 124 Aug 22 20:12:56 nb-voer kernel: [ 1792.518999] iwl data: : 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Aug 22 20:12:56 nb-voer kernel: [ 1792.519024] iwlwifi :02:00.0: FH TRBs(0) = 0x Aug 22 20:12:56 nb-voer kernel: [ 1792.519037] iwlwifi :02:00.0: FH TRBs(1) = 0x80102065 Aug 22 20:12:56 nb-voer kernel: [ 1792.519050] iwlwifi :02:00.0: FH TRBs(2) = 0x Aug 22 20:12:56 nb-voer kernel: [ 1792.519062] iwlwifi :02:00.0: FH TRBs(3) = 0x8031 Aug 22 20:12:56 nb-voer kernel: [ 1792.519075] iwlwifi :02:00.0: FH TRBs(4) = 0x Aug 22 20:12:56 nb-voer kernel: [ 1792.519088] iwlwifi :02:00.0: FH TRBs(5) = 0x Aug 22 20:12:56 nb-voer kernel: [ 1792.519100] iwlwifi :02:00.0: FH TRBs(6) = 0x Aug 22 20:12:56 nb-voer kernel: [ 1792.519113] iwlwifi :02:00.0: FH TRBs(7) = 0x00709052 Aug 22 20:12:56 nb-voer kernel: [ 1792.519163] iwlwifi :02:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x [2,2] Aug 22 20:12:56 nb-voer kernel: [ 1792.519213] iwlwifi :02:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519265] iwlwifi :02:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x [86,124] Aug 22 20:12:56 nb-voer kernel: [ 1792.519326] iwlwifi :02:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519376] iwlwifi :02:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519426] iwlwifi :02:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519476] iwlwifi :02:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519526] iwlwifi :02:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519576] iwlwifi :02:00.0: Q 8 is active and mapped to fifo 3 ra_tid 0x [0,0] Aug 22 20:12:56 nb-voer kernel: [ 1792.519626] iwlwifi :02:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x [83,83] Aug 22 20:12:56 nb-voer kernel: [ 1792.519676] iwlwifi :02:00.0: Q 10 is inacti
[Kernel-packages] [Bug 1691146] rizzo (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/rizzo__4.10.0-22.24__2017-05-23_15-00-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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 1691146] amaura (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/amaura__4.10.0-22.24__2017-05-23_14-52-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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 1691146] fozzie (amd64) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/fozzie__4.10.0-22.24__2017-05-23_14-56-00/results-index.html ** 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/1691146 Title: linux: 4.10.0-22.24 -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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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 1630245] Re: after starting ubuntu 16.10 -- no keyboard, no mouse
I had a very similar problem when I upgraded my virtual machine to Ubuntu 16.10. My mouse and keyboard worked fine until I upgraded to 16.10. The virtual machine would boot just fine, but I had no cursor and no ability to click or type anything. My mouse was being captured by the VM, but not working at all. Well I did realize I had the ability to hold shift at boot to bring up the GRUB menu, so the virtual box was working fine! I figured the issue must be with Xorg. I was able to bring up a root shell and uninstall Xorg. Apt was having issues updating packages since it could not resolve name servers. This somehow caused Xorg to not come up at boot, which is when I also confirmed that bash was also working fine. TL;DR: Uninstalling and reinstalling Xorg has fixed my issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630245 Title: after starting ubuntu 16.10 -- no keyboard, no mouse Status in linux package in Ubuntu: Incomplete Status in linux source package in Yakkety: Incomplete Bug description: After starting Ubuntu 16.10 keyboard and mouse are dead. Since it works with an older kernel but not with the latest one, I'd assume the newer kernel does not initialize the devices the right way. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: systemd 231-9git1 ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16 Uname: Linux 4.4.0-9136-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 Date: Tue Oct 4 15:27:52 2016 InstallationDate: Installed on 2012-12-12 (1391 days ago) InstallationMedia: Ubuntu-Server 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120817.3) Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-9136-generic root=/dev/mapper/test--tps--ubuntu--muc-root ro vga=789 consoleblank=0 SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2013-02-11 (1330 days ago) dmi.bios.date: 07/02/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/02/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630245/+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 1691146] fozzie (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/fozzie__4.10.0-22.24__2017-05-23_15-23-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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 1691146] rizzo (i386) - tests ran: 1, failed: 0
tests ran: 1, failed: 0; http://kernel.ubuntu.com/testing/4.10.0-22.24-generic/rizzo__4.10.0-22.24__2017-05-23_15-31-00/results-index.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/1691146 Title: linux: 4.10.0-22.24 -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: Confirmed 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 Zesty: New 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: 1691149,1691152 derivatives: 1691153 -- swm properties -- boot-testing-requested: 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/1691146/+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
