[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
But "blacklist=nouveau modprobe.blacklist=nouveau" can boot, right? 13a86519202c5d119d83640d6f781f3181205d2c drm/nouveau/i2c/gf119-: add support for address-only transactions: http://people.canonical.com/~khfeng/lp1723619-2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On the latest daily artful image (/current as of 2017-01-14), the following occurs on a system with nVidia graphics (on my system, a GTX970) when connected to a 4k display over a displayport: https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. On the faulty system I could test with, it seems to *only* happen over displayport/on a 4k screen (I don't own a non-4k displayport screen to test the 4k out). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718703] Re: Kernel support for Corsair Strafe monochrome keyboard
dmesg1, dmesg2, which are the same as LP: #1678477: [7.388222] usb 3-14: can't read configurations, error -110 dmesg3: [ 40.156098] usbhid 3-14:1.1: can't add hid device: -110 [ 40.156314] usbhid: probe of 3-14:1.1 failed with error -110 So the original issue is solved, but now you hit another bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1718703 Title: Kernel support for Corsair Strafe monochrome keyboard Status in linux package in Ubuntu: Confirmed Bug description: Related to bug: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1678477 Support for Corsair Strafe RGB was added, but the Corsair Strafe monochrome keyboard has a different device ID and isn't covered by the RGB fix. Quote from other user: "I'm using a slightly different variant of this keyboard - Corsair Strafe (without RGB; product ID is 1b15). I had more or less the same problem (error -110). I tried your solution (USB_QUIRK_DELAY_INIT) and it seems to work every time. I did a quick test - previously keyboard worked 5 out of 10 reboots, and after applying this change it worked 10 out of 10 reboots (I also get this new message during boot, like others did before - "couldn't find an input interrupt endpoint"). As this keyboard has a different product ID (but the same vendor ID), it will probably require additional entry in the drivers/usb/core/quirks.c Please let me know if you need any additional info or tests from me." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1718703/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module
Thanks. It looks like there's also an out-of-tree driver available, if people want to go that direction. (For example, it's available from Dell at https://downloads.dell.com/FOLDER04588242M/1/UnifiedDriver_7.700.52.00_SLES12.tar.gz , found on the drivers and downloads page for the R640 or R740 after selecting SLES or RHEL.) I haven't tried building it on Ubuntu yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Won't Fix Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. There is a series of kernel patches required to support these: http://www.mail-archive.com/linux- ker...@vger.kernel.org/msg1307314.html There is also a relevant follow-up series: https://www.spinics.net/lists/linux-scsi/msg104667.html especially patches 1 and 12. The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Xenial onwards. The upstream commit is going in for 4.11, so this will need to be backported to v4.4 and v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723644] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1723644 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723644 Title: NetworkManager hang Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Recently I had issues with NetworkManager. When I try to restart or close NetworkManager, the process hangs. First it sends a SIGTERM to the NetworkManager process, and after a while it sends SIGKILL, yet nothing happens. After the attempt to restart/close NetworkManager, the OS behaves badly: - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/ SIGKILLing it causes the kill command to hang (no matter how many times I try it), it also hangs the terminal - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill command, can't close the terminal) - the OS won't reboot/suspend/shutdown (it does only after holding the restart button) Suspending/rebooting normally/shutdowning normally the laptop hangs the OS (because of NetworkManager). What I've tried: - reinstalling NetworkManager (uninstalling it using --purge, installing it clean) - deleting ~/.config - deleting ~/.cache - installing a version from NetworkManager from Debian (version: 1.8.4.2), reinstalling NetworkManager from Ubuntu back affects ubuntu affects ubuntu/network-manager affects ubuntu/systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723644] Re: NetworkManager hang
So it's more likely to be a driver issue. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723644 Title: NetworkManager hang Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Recently I had issues with NetworkManager. When I try to restart or close NetworkManager, the process hangs. First it sends a SIGTERM to the NetworkManager process, and after a while it sends SIGKILL, yet nothing happens. After the attempt to restart/close NetworkManager, the OS behaves badly: - journalctl doesn't work, doesn't output anything, SIGTERMing/SIGABRTing/ SIGKILLing it causes the kill command to hang (no matter how many times I try it), it also hangs the terminal - 'sudo dmesg' hangs (killing it with SIGKILL/SIGTERM/SIGABRT hangs the kill command, can't close the terminal) - the OS won't reboot/suspend/shutdown (it does only after holding the restart button) Suspending/rebooting normally/shutdowning normally the laptop hangs the OS (because of NetworkManager). What I've tried: - reinstalling NetworkManager (uninstalling it using --purge, installing it clean) - deleting ~/.config - deleting ~/.cache - installing a version from NetworkManager from Debian (version: 1.8.4.2), reinstalling NetworkManager from Ubuntu back affects ubuntu affects ubuntu/network-manager affects ubuntu/systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module
Hi, It turns out that support for this driver would require a very large backport with several series of patches, involving significant refactoring, code movement and other code change. This makes it very hard for us to be sure that our backport is correct, and that it's not going to fail unexpectedly on this new model or on any of the many older models supported by this driver. Therefore, we have decided that the complexity and risk of regression is unacceptably high, and we will not be providing a backport to the 4.4 kernel series. This means that you will need to use the HWE kernel for this chassis. The Artful kernel, which is out next week, has full support. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Won't Fix Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. There is a series of kernel patches required to support these: http://www.mail-archive.com/linux- ker...@vger.kernel.org/msg1307314.html There is also a relevant follow-up series: https://www.spinics.net/lists/linux-scsi/msg104667.html especially patches 1 and 12. The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Xenial onwards. The upstream commit is going in for 4.11, so this will need to be backported to v4.4 and v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683587] Re: LSI Harpoon support in megaraid_sas module
Are the patches for 4.4 (Xenial) available somewhere? We'd like patches so we can build the kernel ourselves. We can immediately do basic testing against H730/830 (Invader, previously supported) and H840 (Harpoon, new, probably same as H740 except with external connectors instead of internal). With a little more time and effort we can do some testing on H720 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/1683587 Title: LSI Harpoon support in megaraid_sas module Status in linux package in Ubuntu: Confirmed Bug description: The Dell PERC H740 series RAID controllers, codename "Harpoon", are not supported in standard Ubuntu kernels. There is a series of kernel patches required to support these: http://www.mail-archive.com/linux- ker...@vger.kernel.org/msg1307314.html There is also a relevant follow-up series: https://www.spinics.net/lists/linux-scsi/msg104667.html especially patches 1 and 12. The relevant PCI IDs from the PCI database (http://pciids.sourceforge.net/v2.2/pci.ids) are: 0016 MegaRAID Tri-Mode SAS3508 1028 1fc9 PERC H840 Adapter 1028 1fcb PERC H740P Adapter 1028 1fcd PERC H740P Mini 1028 1fcf PERC H740P Mini They should be supported from Xenial onwards. The upstream commit is going in for 4.11, so this will need to be backported to v4.4 and v4.10. I am working on SRU patches for this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1683587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724079] Re: bluetooth applet hangs - 17.10 artful
Please look in /var/crash for a relevant crash file and when found upload it using this command: ubuntu-bug /PATH/TO/WHATEVER.crash ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- 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/1724079 Title: bluetooth applet hangs - 17.10 artful Status in bluez package in Ubuntu: Incomplete Bug description: ubuntu 17.10 bluez 5.46-0ubuntu3 after failing to search for bluetooth mouse, bluetooth applet crashes. restarting bluetooth.service yields "adapter not found" message upon trying to turn on bluetooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1724079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
That's just the same BS Asus support always try to push on people. I can tell you have updated every driver, to no avail. And even if it did work, it wouldn't make a difference in Windows. It is most certainly a firmware bug. That said, there still hasn't been any explanation as to why this thread was marked "fixed." Except for the iffy firmware patch I posted earlier, as far as I know nothing else has fixed this issue. It would be nice if Anton made some other comment besides just marking the thread fixed. -- You 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: Fix Released 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 I: Bus=0003 Vendor=04d9 Product=a070
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
Wouldn't make a difference in Linux I meant. -- You 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: Fix Released 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 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:04D9:A070.0001/input/input5 U: Uniq= H: Handlers=sysrq kbd event5 leds B: PROP=0 B: EV=120013 B: KEY=e080ffdf01cf fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input1 S:
[Kernel-packages] [Bug 1724120] [NEW] Ubuntu 16.10/16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured
Public bug reported: Issue: Call traces occurs when memory-hotplug script is run with 16Gb hugepages configured. Environment: ppc64le PowerVM Lpar root@ltctuleta-lp1:~# uname -r 4.4.0-34-generic root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge AnonHugePages: 0 kB HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@ltctuleta-lp1:~# free -h totalusedfree shared buff/cache available Mem:85G 32G 52G 16M193M 52G Swap: 43G 0B 43G Steps to reproduce: 1 - Download kernel source and enter to the directory- tools/testing/selftests/memory-hotplug/ 2 - Run mem-on-off-test.sh script in it. System gives call traces like: offline_memory_expect_success 639: unexpected fail online-offline 668 [ 57.552964] Unable to handle kernel paging request for data at address 0x0028 [ 57.552977] Faulting instruction address: 0xc029bc04 [ 57.552987] Oops: Kernel access of bad area, sig: 11 [#1] [ 57.552992] SMP NR_CPUS=2048 NUMA pSeries [ 57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel rtc_generic mdio libcrc32c [ 57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 4.4.0-34-generic #53-Ubuntu [ 57.553059] task: c0072773c8e0 ti: c0072778 task.ti: c0072778 [ 57.553067] NIP: c029bc04 LR: c029bbdc CTR: c01107f0 [ 57.553076] REGS: c00727783770 TRAP: 0300 Not tainted (4.4.0-34-generic) [ 57.553083] MSR: 80019033CR: 24242882 XER: 0002 [ 57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 SOFTE: 1 GPR00: c029bbdc c007277839f0 c15b5d00 GPR04: 0029d000 0800 fa01 GPR08: fa700020 0008 c185e270 c00e7e50 GPR12: 2200 ce6ea200 0029d000 2200 GPR16: 1000 c15e2200 0a70 GPR20: 0001 0100 0200 c15f16d0 GPR24: c1876510 0001 c1872a00 GPR28: 0029d000 f000 fa70 0029c000 [ 57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220 [ 57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 [ 57.553226] Call Trace: [ 57.553231] [c007277839f0] [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 (unreliable) [ 57.553244] [c00727783a80] [c02dcbc8] __offline_pages.constprop.6+0x3f8/0x900 [ 57.553254] [c00727783bd0] [c06fbb38] memory_subsys_offline+0xa8/0x110 [ 57.553265] [c00727783c00] [c06d6424] device_offline+0x104/0x140 [ 57.553274] [c00727783c40] [c06fba80] store_mem_state+0x180/0x190 [ 57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0 [ 57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0 [ 57.553302] [c00727783d00] [c0397028] kernfs_fop_write+0x188/0x200 [ 57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0 [ 57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230 [ 57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110 [ 57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4 [ 57.553346] Instruction dump: [ 57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 fabe0020 [ 57.553366] fade0028 79294620 79291764 7d234a14 3908 f9030028 81091458 [ 57.553383] ---[ end trace 617f7bdd75bcfc10 ]--- [ 57.557133] Segmentation fault The following commit IDs were built into a 4.10.0-37-generic #41 test kernel and verified to fix the problem: a525108cf1cc14651602d678da38fa627a76a724 e1073d1e7920946ac4776a619cc40668b9e1401b 40692eb5eea209c2dd55857f44b4e1d7206e91d6 e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d 79cc38ded1e1ac86e69c90f604efadd50b0b3762 4ae279c2c96ab38a78b954d218790a8f6db714e5 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-145249 severity-high targetmilestone-inin16043 ** Tags added: architecture-ppc64le bugnameltc-145249 severity-high targetmilestone-inin16043 ** Changed in: ubuntu Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) ** 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.
[Kernel-packages] [Bug 1724120] [NEW] Ubuntu 16.10/16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured
You have been subscribed to a public bug: Issue: Call traces occurs when memory-hotplug script is run with 16Gb hugepages configured. Environment: ppc64le PowerVM Lpar root@ltctuleta-lp1:~# uname -r 4.4.0-34-generic root@ltctuleta-lp1:~# cat /proc/meminfo | grep -i huge AnonHugePages: 0 kB HugePages_Total: 2 HugePages_Free:2 HugePages_Rsvd:0 HugePages_Surp:0 Hugepagesize: 16777216 kB root@ltctuleta-lp1:~# free -h totalusedfree shared buff/cache available Mem:85G 32G 52G 16M193M 52G Swap: 43G 0B 43G Steps to reproduce: 1 - Download kernel source and enter to the directory- tools/testing/selftests/memory-hotplug/ 2 - Run mem-on-off-test.sh script in it. System gives call traces like: offline_memory_expect_success 639: unexpected fail online-offline 668 [ 57.552964] Unable to handle kernel paging request for data at address 0x0028 [ 57.552977] Faulting instruction address: 0xc029bc04 [ 57.552987] Oops: Kernel access of bad area, sig: 11 [#1] [ 57.552992] SMP NR_CPUS=2048 NUMA pSeries [ 57.553002] Modules linked in: btrfs xor raid6_pq pseries_rng sunrpc autofs4 ses enclosure nouveau bnx2x i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm vxlan ip6_udp_tunnel ipr udp_tunnel rtc_generic mdio libcrc32c [ 57.553050] CPU: 44 PID: 6518 Comm: mem-on-off-test Not tainted 4.4.0-34-generic #53-Ubuntu [ 57.553059] task: c0072773c8e0 ti: c0072778 task.ti: c0072778 [ 57.553067] NIP: c029bc04 LR: c029bbdc CTR: c01107f0 [ 57.553076] REGS: c00727783770 TRAP: 0300 Not tainted (4.4.0-34-generic) [ 57.553083] MSR: 80019033CR: 24242882 XER: 0002 [ 57.553104] CFAR: c0008468 DAR: 0028 DSISR: 4000 SOFTE: 1 GPR00: c029bbdc c007277839f0 c15b5d00 GPR04: 0029d000 0800 fa01 GPR08: fa700020 0008 c185e270 c00e7e50 GPR12: 2200 ce6ea200 0029d000 2200 GPR16: 1000 c15e2200 0a70 GPR20: 0001 0100 0200 c15f16d0 GPR24: c1876510 0001 c1872a00 GPR28: 0029d000 f000 fa70 0029c000 [ 57.553211] NIP [c029bc04] dissolve_free_huge_pages+0x154/0x220 [ 57.553219] LR [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 [ 57.553226] Call Trace: [ 57.553231] [c007277839f0] [c029bbdc] dissolve_free_huge_pages+0x12c/0x220 (unreliable) [ 57.553244] [c00727783a80] [c02dcbc8] __offline_pages.constprop.6+0x3f8/0x900 [ 57.553254] [c00727783bd0] [c06fbb38] memory_subsys_offline+0xa8/0x110 [ 57.553265] [c00727783c00] [c06d6424] device_offline+0x104/0x140 [ 57.553274] [c00727783c40] [c06fba80] store_mem_state+0x180/0x190 [ 57.553283] [c00727783c80] [c06d1e58] dev_attr_store+0x68/0xa0 [ 57.553293] [c00727783cc0] [c0398110] sysfs_kf_write+0x80/0xb0 [ 57.553302] [c00727783d00] [c0397028] kernfs_fop_write+0x188/0x200 [ 57.553312] [c00727783d50] [c02e190c] __vfs_write+0x6c/0xe0 [ 57.553321] [c00727783d90] [c02e2640] vfs_write+0xc0/0x230 [ 57.553329] [c00727783de0] [c02e367c] SyS_write+0x6c/0x110 [ 57.553339] [c00727783e30] [c0009204] system_call+0x38/0xb4 [ 57.553346] Instruction dump: [ 57.553351] 7e831836 4bfff991 e91e0028 e8fe0020 7d32e82a f9070008 f8e8 fabe0020 [ 57.553366] fade0028 79294620 79291764 7d234a14 3908 f9030028 81091458 [ 57.553383] ---[ end trace 617f7bdd75bcfc10 ]--- [ 57.557133] Segmentation fault The following commit IDs were built into a 4.10.0-37-generic #41 test kernel and verified to fix the problem: a525108cf1cc14651602d678da38fa627a76a724 e1073d1e7920946ac4776a619cc40668b9e1401b 40692eb5eea209c2dd55857f44b4e1d7206e91d6 e24a1307ba1f99fc62a0bd61d5e87fcfb6d5503d 79cc38ded1e1ac86e69c90f604efadd50b0b3762 4ae279c2c96ab38a78b954d218790a8f6db714e5 ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) Status: New ** Tags: architecture-ppc64le bugnameltc-145249 severity-high targetmilestone-inin16043 -- Ubuntu 16.10/16.04.3 - call traces occurs when memory-hotplug test is run with 16Gb hugepages configured https://bugs.launchpad.net/bugs/1724120 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] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724117] [NEW] thunderx2 ahci errata workaround needs additional delays
Public bug reported: [Impact] Early ThunderX silicon may hang when initializing the SATA controller. [Test Case] This was found in a reboot loop. The latest ThunderX2 firmware (3.1) enables hardware error interrupts and when the reset fix fails, we get a hang with the print: [ 14.839308] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB) [ 14.846796] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 14.852036] sd 1:0:0:0: [sdb] Write Protect is off [ 14.856843] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.866022] ata2.00: Enabling discard_zeroes_data *** NBU BAR Error 0x1e25c *** AddrLo 0x1d80180 AddrHi 0x0 [Regression Risk] The fix is only compiled in on arm64, and only activated at runtime on this specific revision of silicon, so regression risk will be limited to a single platform that is only being distributed for development purposes. ** Affects: linux (Ubuntu) Importance: Undecided Assignee: dann frazier (dannf) Status: 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/1724117 Title: thunderx2 ahci errata workaround needs additional delays Status in linux package in Ubuntu: In Progress Bug description: [Impact] Early ThunderX silicon may hang when initializing the SATA controller. [Test Case] This was found in a reboot loop. The latest ThunderX2 firmware (3.1) enables hardware error interrupts and when the reset fix fails, we get a hang with the print: [ 14.839308] sd 1:0:0:0: [sdb] 468862128 512-byte logical blocks: (240 GB/224 GiB) [ 14.846796] sd 1:0:0:0: [sdb] 4096-byte physical blocks [ 14.852036] sd 1:0:0:0: [sdb] Write Protect is off [ 14.856843] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 14.866022] ata2.00: Enabling discard_zeroes_data *** NBU BAR Error 0x1e25c *** AddrLo 0x1d80180 AddrHi 0x0 [Regression Risk] The fix is only compiled in on arm64, and only activated at runtime on this specific revision of silicon, so regression risk will be limited to a single platform that is only being distributed for development purposes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723680] Re: GPU Hang in Xorg rcs0 drm/i915
Did this issue start happening after an update/upgrade? It started after upgrading to 17.10 artful aardvark. Was there a prior kernel version where you were not having this particular problem? It worked/works with 4.10.0-35 (still in grub boot list) Would it be possible for you to test the latest upstream kernel? Installed and booted v4.14-rc5. Issue was got worse. Completely wedged on what should be lightdm login. Just non blinking cursor in top left of screen, no ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723680 Title: GPU Hang in Xorg rcs0 drm/i915 Status in linux package in Ubuntu: Confirmed Bug description: Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful When using linux kernel linux-image-4.13.0-12-generic to linux- image-4.13.0-16-generic Xorg fails to start with kernel error messages below. Kernel boots and displays messages allows for GUI to enter disk encryption key then tries to start Xorg login. Shows blank screen, sometimes part of login dialog. Then hangs and goes blank usually showing the low graphics mode error screen from Xorg and no functionality after a while. Can ctrl+alt+f1 to console. Using linux-image-4.10.0-35-generic everything works as expected. System worked without issue with Ubuntu 17.04 Kernel error messages: [ 43.836641] [drm] GPU HANG: ecode 8:0:0x00df, in Xorg [1027], reason: Hang on rcs0, action: reset [ 43.836645] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 43.836646] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 43.836647] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 43.836648] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 43.836649] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 43.836718] drm/i915: Resetting chip after gpu hang [ 55.812149] drm/i915: Resetting chip after gpu hang [ 63.840645] drm/i915: Resetting chip after gpu hang [ 71.836614] drm/i915: Resetting chip after gpu hang [ 79.836882] drm/i915: Resetting chip after gpu hang [ 88.828508] drm/i915: Resetting chip after gpu hang have tried kernel parameter intel_iommu=off, intel_iommu=igfx_off, i915.enable_rc6=0 with no better results. lshw, dmesg and card0/error file attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723777] Re: Apple bluetooth USB driver is 100% busy despite BT switched off
Reproes with the v4.14 kernel. Power usage on idle is 4.14:~8W 4.13:~10W 4.10:~7W There appears to have been a significant regression in power use from 4.10 to 4.13 that has been partially addressed in 4.14. I got curious, and I get the same 100% busy report if I boot with the legacy 4.10.37 kernel now (whereas I did not before), so this might be an issue with powertop as upgraded with 17.10 and the bt driver might be a red herring. Is there a more reliable way to measure power usage? ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723777 Title: Apple bluetooth USB driver is 100% busy despite BT switched off Status in linux package in Ubuntu: Confirmed Bug description: Just upgraded from 17.04 to 17.10 on a 2011 macbook air. Battery drain is markedly more severe. Looking at powertop, the main difference is that the Apple USB Bluetooth driver is drawing ~2.5W and is showing as 100% busy. Bluetooth is switched off. I have tried rfkill, blacklisting btusb, modifying the /etc/bluetooth/main.conf to not autoenable and to set InitiallyPowered to false. None of these work. powertop output: 2.58 W100.0% Device USB device: Bluetooth USB Host Controller (Apple Inc.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 11:45:16 2017 InstallationDate: Installed on 2014-11-09 (1070 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: bluetooth MachineType: Apple Inc. MacBookAir4,2 ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=58091989-ee9b-4c99-afa8-fffa56a1f3af ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago) dmi.bios.date: 06/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B12.1506081728 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B12.1506081728:bd06/08/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.family: MacBook Air dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722335] Re: linux: 3.13.0-134.183 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722335 Title: linux: 3.13.0-134.183 -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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722336 derivatives: -- 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/1722335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
Now I cannot do it. I will do it tomorrow around this time, having access to the hardware involved. Thanks On Mon, 16 Oct 2017 at 21:41 Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > It looks like the bisect failed. All of the kernels I posted were > reported as good and resolved the bug. One or more of them should have > been bad and exhibited the bug. > > > I copied all of the test kernels back to > http://kernel.ubuntu.com/~jsalisbury/lp1723174. The test kernels for a > specific SHA1 are in a sub directory with that SHA1 as the directory name. > > Would it be possible for folks affected by this bug to test some of > these kernels and see which one first exhibits the bug? Based on that, > I can restart the bisect. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1723174 > > Title: > Intel graphics problems on kernel 4.10.0-37-generic > > Status in linux package in Ubuntu: > In Progress > Status in linux source package in Zesty: > In Progress > > Bug description: > After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works > extremely slow. > The reason is that i915 driver is UNCLAIMED now. > > Error from Xorg logs is: > [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version > 1.4: Permission denied > > Environment: > Ubuntu 17.04 > Kernel 4.10.0-37 > Intel HD Graphics 520 > INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions > -- Emanuele on the earth for a while looking for enlightenment listening to the inner teacher about.me/emanuelecisbani keybase.io/cisba -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724079] [NEW] bluetooth applet hangs - 17.10 artful
Public bug reported: ubuntu 17.10 bluez 5.46-0ubuntu3 after failing to search for bluetooth mouse, bluetooth applet crashes. restarting bluetooth.service yields "adapter not found" message upon trying to turn on bluetooth. ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: artful bluetooth bluez -- 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/1724079 Title: bluetooth applet hangs - 17.10 artful Status in bluez package in Ubuntu: New Bug description: ubuntu 17.10 bluez 5.46-0ubuntu3 after failing to search for bluetooth mouse, bluetooth applet crashes. restarting bluetooth.service yields "adapter not found" message upon trying to turn on bluetooth. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1724079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
I did the same with: $ uname -rv 4.13.7-041307-generic #201710141430 SMP Sat Oct 14 14:31:12 UTC 2017 and also this kernel works for me and touchpad works after resume. What is also nice, Wi-Fi works after resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723619] Re: Ubuntu Desktop ISO fails to boot with nouveau on a displayport
The kernel at #14 fails to boot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723619 Title: Ubuntu Desktop ISO fails to boot with nouveau on a displayport Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: On the latest daily artful image (/current as of 2017-01-14), the following occurs on a system with nVidia graphics (on my system, a GTX970) when connected to a 4k display over a displayport: https://photos.app.goo.gl/gLUva3Vgvtv0lAmj2 Steps to reproduce: - Download latest daily image, check checksums, burn to USB - Boot from USB. - Choose "Install Ubuntu" or "try ubuntu" at the menu. This happens on the livecd, but also upon ugrading the system from a previous daily with a different kernel: my "old" daily booted and installed fine with kernel 4.12.0-12, then failed with same error once dist-upgraded. On the faulty system I could test with, it seems to *only* happen over displayport/on a 4k screen (I don't own a non-4k displayport screen to test the 4k out). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1723619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1478754] Re: [Lenovo Thinkpad X1 Carbon 3rd Gen] Wireless disconnects using Intel 7265 [8086:095b] (rev 59)
This was presumed fixed in the upstream bug report [1] and hasn't been a problem for a couple of years now. Closing this report. [1] https://bugzilla.kernel.org/show_bug.cgi?id=102161 ** Bug watch added: Linux Kernel Bug Tracker #102161 https://bugzilla.kernel.org/show_bug.cgi?id=102161 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1478754 Title: [Lenovo Thinkpad X1 Carbon 3rd Gen] Wireless disconnects using Intel 7265 [8086:095b] (rev 59) Status in linux package in Ubuntu: Invalid Bug description: Wireless disconnects from networks randomly - sometimes connections OK for days, other times for only a few minutes. Sometimes a wireless power off/on or system standby/resume re-establishes connection, but usually a reboot is required. Wireless hardware and symptoms similar to bug 1437913, but different laptop model. Log messages vary depending on the type of network being used. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-23-generic 3.19.0-23.24 ProcVersionSignature: Ubuntu 3.19.0-23.24-generic 3.19.8-ckt2 Uname: Linux 3.19.0-23-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: cimes 1898 F pulseaudio /dev/snd/controlC0: cimes 1898 F pulseaudio /dev/snd/controlC1: cimes 1898 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 27 21:17:20 2015 HibernationDevice: RESUME=UUID=3b6a30b4-016d-4ebd-ae99-2e6b978faadd InstallationDate: Installed on 2015-06-15 (42 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO 20BSCTO1WW ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-23-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-23-generic N/A linux-backports-modules-3.19.0-23-generic N/A linux-firmware 1.143.2 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-06-19 (38 days ago) dmi.bios.date: 03/12/2015 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET28W (1.06 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET28W(1.06):bd03/12/2015:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1478754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1722677] Re: Touch Screen NOT working
Sorry for the delay. I will try the new kernel, thanks! On Wed, Oct 11, 2017 at 3:01 PM, Joseph Salisbury < joseph.salisb...@canonical.com> wrote: > Would it be possible for you to test the latest upstream kernel? Refer > to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.14 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc4 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1722677 > > Title: > Touch Screen NOT working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. > Touchscreen does not work after installing OS from live USB. It did not > work on USB either. There is zero touchscreen functionality. > > Workaroud: Must put computer to sleep, and then wake from sleep for > touchscreen to work. > > Please Note: In this edition of 17.10, tilt sensors work perfectly > without having to put the computer to sleep (an old bug). Also note, > wifi works perfectly after resuming from sleep (another old bug fixed > :) > > ProblemType: Bug > DistroRelease: Ubuntu 17.10 > Package: linux-image-4.13.0-15-generic 4.13.0-15.16 > ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 > Uname: Linux 4.13.0-15-generic x86_64 > ApportVersion: 2.20.7-0ubuntu2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: troll 1255 F pulseaudio >/dev/snd/controlC0: troll 1255 F pulseaudio > CurrentDesktop: ubuntu:GNOME > Date: Tue Oct 10 18:54:29 2017 > InstallationDate: Installed on 2017-09-30 (10 days ago) > InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 > (20170926) > MachineType: Dell Inc. Venue 11 Pro 7139 > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcFB: 0 inteldrmfb > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-15-generic.efi.signed > root=UUID=cdb5516d-c1f9-4c0b-8869-35a9db498fa1 ro quiet splash > vt.handoff=7 > RelatedPackageVersions: >linux-restricted-modules-4.13.0-15-generic N/A >linux-backports-modules-4.13.0-15-generic N/A >linux-firmware 1.169 > SourcePackage: linux > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/15/2015 > dmi.bios.vendor: Dell Inc. > dmi.bios.version: A16 > dmi.board.name: 0RFDKW > dmi.board.vendor: Dell Inc. > dmi.board.version: A01 > dmi.chassis.type: 8 > dmi.chassis.vendor: Dell Inc. > dmi.modalias: dmi:bvnDellInc.:bvrA16:bd06/15/2015:svnDellInc.: > pnVenue11Pro7139:pvr01:rvnDellInc.:rn0RFDKW:rvrA01:cvnDellInc.:ct8:cvr: > dmi.product.name: Venue 11 Pro 7139 > dmi.product.version: 01 > dmi.sys.vendor: Dell Inc. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/ > 1722677/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722677 Title: Touch Screen NOT working Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 17.10 Beta 2. Dell Venue 11 pro 7139. Touchscreen does not work after installing OS from live USB. It did not work on USB either. There is zero touchscreen functionality. Workaroud: Must put computer to sleep, and then wake from sleep for touchscreen to work. Please Note: In this edition of 17.10, tilt sensors work perfectly without having to put the computer to sleep (an old bug). Also note, wifi works perfectly after resuming from sleep (another old bug fixed :) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-15-generic 4.13.0-15.16 ProcVersionSignature: Ubuntu 4.13.0-15.16-generic 4.13.4 Uname: Linux 4.13.0-15-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: troll 1255 F pulseaudio /dev/snd/controlC0: troll 1255 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 10 18:54:29 2017 InstallationDate: Installed on 2017-09-30 (10 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: Dell Inc. Venue 11 Pro 7139 ProcEnviron: TERM=xterm-256color
Re: [Kernel-packages] [Bug 1723772] Re: Hibernation
Hello Joseph, thanks for your email. I'm trying to install the Kernel 4.14 from this link: http://sourcedigit.com/22814-install-linux-kernel-4-14-rc5/ but it doesn't work. After the two first commands all other show the message "not found". I'll try to answer your questions. This problem started after an upgrade from 17.04 to 17.10. With ubuntu 17.04 (Gnome) I tipped the key "space" and could immediatly put the password an work further. Now I'm asked to click over my name (even though I'm the only user an have only one account) then the password and everything is out. I'm not sure which kernel I was using. Maybe 4.10.0-37-generic? I'm still use this one on my laptop. I need to apologize that I'm not an user so advanced. But I'm working now and trying to install the version 4.14. Well; I'm still on computer for the next two hours and I can answer if you have questions. Thank you too. Am Montag, den 16.10.2017, 17:30 + schrieb Joseph Salisbury: > Did this issue start happening after an update/upgrade? Was there a > prior kernel version where you were not having this particular problem? > > We would like to see if this bug is already fixed upstream, so please > test the latest upstream kernel. Refer to > https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest > v4.14 kernel[0]. > > If this bug is fixed in the mainline kernel, please add the following > tag 'kernel-fixed-upstream'. > > If the mainline kernel does not fix this bug, please add the tag: > 'kernel-bug-exists-upstream'. > > Once testing of the upstream kernel is complete, please mark this bug as > "Confirmed". > > > Thanks in advance. > > [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 > > ** Changed in: linux (Ubuntu) >Importance: Undecided => Medium > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723772 Title: Hibernation Status in linux package in Ubuntu: Incomplete Bug description: When the monitor in the modus hibernation gets, it works until then ok, even if I'm listenig to music, the music plays further. When I try to come back to use the computer the music stops and when I insert my password all the programs are closed, as if I had started the OS. Every windows are closed and you need to open eveything again. Just to inform: I use a Monitor Samsung 4K 28" through DisplayPort. On a desktop, not a laptop. If you need some more information that I may forgot, I try to answer as soon as possible. Thank you very much, Thiago Benites PS: I use the german version of Artful Aardvark --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 1032 F...m pulseaudio /dev/snd/controlC0: thiago 1032 F pulseaudio /dev/snd/controlC1: thiago 1032 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-02 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 32272R4 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT67AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT67AUS:bd04/27/2013:svnLENOVO:pn32272R4:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrWin8STDDPKTPG:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 32272R4 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 6664 F...m pulseaudio /dev/snd/controlC0: thiago 6664 F pulseaudio /dev/snd/controlC1: thiago 6664 F
[Kernel-packages] [Bug 1724071] [NEW] Update firmware for 4.13 linux-hwe-edge kernel
Public bug reported: Add and update firmware files as necessary to support a 4.12 based kernel in the xenial linux-hwe-edge package. ** Affects: linux-firmware (Ubuntu) Importance: Medium Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1724071 Title: Update firmware for 4.13 linux-hwe-edge kernel Status in linux-firmware package in Ubuntu: In Progress Bug description: Add and update firmware files as necessary to support a 4.12 based kernel in the xenial linux-hwe-edge package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1724071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720580] Re: RTL8723bs bug: ERROR sd_recv_rxfifo: alloc recvbuf FAIL!
I've applied the above mentioned patch, and rebuilt the rtl8723bs module, but the same problem persists. Also tested kernel 4.14, and, as expected, the same bug is there too. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720580 Title: RTL8723bs bug: ERROR sd_recv_rxfifo: alloc recvbuf FAIL! Status in linux package in Ubuntu: Confirmed Bug description: Found a bunch of "RTL8723BS: ERROR sd_recv_rxfifo: alloc recvbuf FAIL!" messages in syslog after a complete freeze. Searching for this error only found one reference https://lkml.org/lkml/2017/6/12/504. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: boot/vmlinuz-4.13.0-12-generic] ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mele 1303 F pulseaudio CurrentDesktop: MATE Date: Sat Sep 30 23:45:09 2017 HibernationDevice: RESUME=UUID=ab188fcc-c7b5-433e-8dc8-bf403e9888ec InstallationDate: Installed on 2017-09-29 (1 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha amd64 (20170926) MachineType: MiPi PC Mini PC ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-12-generic.efi.signed root=UUID=f415201e-4ac6-4443-83b8-f40d3dc03403 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-12-generic N/A linux-backports-modules-4.13.0-12-generic N/A linux-firmware 1.168 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: r8723bs UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Mini PC dmi.board.vendor: Mini PC dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 8 dmi.chassis.vendor: Mini PC dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.6.5:bd10/29/2015:svnMiPiPC:pnMiniPC:pvr2.80:rvnMiniPC:rnMiniPC:rvrTobefilledbyO.E.M.:cvnMiniPC:ct8:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Mini PC dmi.product.version: 2.80 dmi.sys.vendor: MiPi PC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1720580/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Could you also give the latest upstream stable 3.13 kernel a try? It is available here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13.7/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715146] Re: Not Suspending When Lid is Closed Causing Heat Issue
Disabling Thunderbolt support in the BIOS (F2 during boot) worked for me. Suspend works. Don't know when/if I'll need the Thunderbolt. This works for now. Thanks! Can I provide any additional info to help you debug/fix this properly? Cheers, Walter Before disabling Thunderbolt: [ 4694.667622] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 4694.679878] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 4696.418854] PM: Syncing filesystems ... done. [ 4696.426577] PM: Preparing system for sleep (mem) [ 4696.426825] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 4696.428577] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 4696.429797] PM: Suspending system (mem) [ 4696.429831] Suspending console(s) (use no_console_suspend to debug) [ 4696.645611] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout [ 4696.645628] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110 [ 4696.645632] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 4696.645636] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 4696.645642] PM: Device :39:00.0 failed to suspend async: error -110 [ 4696.645836] PM: Some devices failed to suspend, or early wake event detected [ 4696.653802] PM: resume of devices complete after 7.960 msecs [ 4696.654412] PM: Finishing wakeup. [ 4696.654413] Restarting tasks ... done. [ 4696.713358] PM: Syncing filesystems ... done. [ 4696.724043] PM: Preparing system for sleep (freeze) [ 4696.724263] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 4696.726226] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 4696.727480] PM: Suspending system (freeze) [ 4696.727481] Suspending console(s) (use no_console_suspend to debug) [ 4696.727681] xhci_hcd :39:00.0: WARN: xHC CMD_RUN timeout [ 4696.727685] suspend_common(): xhci_pci_suspend+0x0/0xd0 returns -110 [ 4696.727687] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -110 [ 4696.727688] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -110 [ 4696.727690] PM: Device :39:00.0 failed to suspend async: error -110 [ 4696.727901] PM: Some devices failed to suspend, or early wake event detected [ 4696.735295] PM: resume of devices complete after 7.392 msecs [ 4696.735495] PM: Finishing wakeup. After disabling Thunderbolt: [ 467.806774] wlp58s0: deauthenticating from xx:xx:xx:xx:xx:xx by local choice (Reason: 3=DEAUTH_LEAVING) [ 467.819709] IPv6: ADDRCONF(NETDEV_UP): wlp58s0: link is not ready [ 469.526719] PM: Syncing filesystems ... done. [ 469.536851] PM: Preparing system for sleep (mem) [ 469.537149] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 469.538896] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. [ 469.539665] PM: Suspending system (mem) [ 469.539701] Suspending console(s) (use no_console_suspend to debug) [ 469.759779] ACPI : EC: event blocked [ 470.973736] PM: suspend of devices complete after 1217.757 msecs [ 470.995596] PM: late suspend of devices complete after 21.855 msecs [ 470.996271] ACPI : EC: interrupt blocked [ 470.999072] xhci_hcd :00:14.0: System wakeup enabled by ACPI [ 471.035732] PM: noirq suspend of devices complete after 40.130 msecs [ 471.036567] ACPI: Preparing to enter system sleep state S3 [ 471.043286] ACPI : EC: EC stopped [ 471.043288] PM: Saving platform NVS memory [ 471.043385] Disabling non-boot CPUs ... [ 471.046076] smpboot: CPU 1 is now offline [ 471.073211] Broke affinity for irq 123 [ 471.073217] Broke affinity for irq 124 [ 471.073229] Broke affinity for irq 126 [ 471.073284] Broke affinity for irq 286 [ 471.074352] smpboot: CPU 2 is now offline [ 471.096769] Broke affinity for irq 1 [ 471.096776] Broke affinity for irq 8 [ 471.096781] Broke affinity for irq 9 [ 471.096785] Broke affinity for irq 12 [ 471.096789] Broke affinity for irq 14 [ 471.096793] Broke affinity for irq 16 [ 471.096798] Broke affinity for irq 17 [ 471.096806] Broke affinity for irq 51 [ 471.096815] Broke affinity for irq 122 [ 471.096820] Broke affinity for irq 123 [ 471.096823] Broke affinity for irq 124 [ 471.096827] Broke affinity for irq 125 [ 471.096832] Broke affinity for irq 126 [ 471.096871] Broke affinity for irq 281 [ 471.096875] Broke affinity for irq 286 [ 471.097940] smpboot: CPU 3 is now offline [ 471.111695] ACPI: Low-level resume complete [ 471.111808] ACPI : EC: EC started [ 471.111809] PM: Restoring platform NVS memory [ 471.112606] Suspended for 16.485 seconds [ 471.113987] Enabling non-boot CPUs ... [ 471.123998] x86: Booting SMP configuration: [ 471.123998] smpboot: Booting Node 0 Processor 1 APIC 0x2 [ 471.124625] cache: parent cpu1 should not be sleeping [ 471.124746] microcode: sig=0x806e9, pf=0x40, revision=0x4e [ 471.125660] CPU1 is up [ 471.136138] smpboot: Booting Node 0 Processor 2 APIC 0x1 [ 471.137181] cache: parent cpu2 should not be sleeping [
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
Let me know do you need anything else. Will be possible to backport fixes from 4.14 to final release of Ubuntu 17.10, so touchpad works after resume on default Artful Aardvark install? ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
I did following: dpkg -i \ linux-headers-4.14.0-041400rc5_4.14.0-041400rc5.201710152230_all.deb \ linux-headers-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb \ linux-image-4.14.0-041400rc5-generic_4.14.0-041400rc5.201710152230_amd64.deb and rebooted the system to new kernel. Yes I can confirm that kernel 4.14.0-041400rc5-generic fixes the problem for me. With this new kernel however Wi-Fi doesn't work, but that's another issue. Wi-Fi works with 4.13.0-16-generic and previous kernels from Ubuntu 17.10 ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Confirmed Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722335] Re: linux: 3.13.0-134.183 -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: 1722336 derivatives: - kernel-stable-phase-changed:Tuesday, 10. October 2017 20:34 UTC - kernel-stable-phase:Uploaded - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase-changed:Monday, 16. October 2017 19:32 UTC + kernel-stable-phase:Promoted to proposed ** 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: 1722336 derivatives: -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase-changed:Monday, 16. October 2017 19:32 UTC - kernel-stable-phase:Promoted to proposed + 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/1722335 Title: linux: 3.13.0-134.183 -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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722336 derivatives: -- 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/1722335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724044] Re: autopkgtest regression due to only building single FLAVOUR
** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Artful) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Bb-series) Assignee: (unassigned) => Dan Streetman (ddstreet) ** Changed in: linux (Ubuntu Artful) Importance: Medium => Low ** Changed in: linux (Ubuntu Xenial) Importance: Medium => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724044 Title: autopkgtest regression due to only building single FLAVOUR Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Status in linux source package in bb-series: Triaged Bug description: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
It looks like the bisect failed. All of the kernels I posted were reported as good and resolved the bug. One or more of them should have been bad and exhibited the bug. I copied all of the test kernels back to http://kernel.ubuntu.com/~jsalisbury/lp1723174. The test kernels for a specific SHA1 are in a sub directory with that SHA1 as the directory name. Would it be possible for folks affected by this bug to test some of these kernels and see which one first exhibits the bug? Based on that, I can restart the bisect. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724044] Re: autopkgtest regression due to only building single FLAVOUR
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: Incomplete ** Also affects: linux (Ubuntu Bb-series) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Zesty) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: Incomplete => Triaged ** Changed in: linux (Ubuntu Bb-series) Status: New => Triaged ** Changed in: linux (Ubuntu Zesty) Status: New => Triaged ** Changed in: linux (Ubuntu Xenial) Status: New => Triaged ** Changed in: linux (Ubuntu Trusty) Status: New => Triaged ** Changed in: linux (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Zesty) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bb-series) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724044 Title: autopkgtest regression due to only building single FLAVOUR Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: Triaged Status in linux source package in Zesty: Triaged Status in linux source package in Artful: Triaged Status in linux source package in bb-series: Triaged Bug description: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724044] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1724044 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: trusty -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724044 Title: autopkgtest regression due to only building single FLAVOUR Status in linux package in Ubuntu: Incomplete Bug description: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724044] Re: autopkgtest regression due to only building single FLAVOUR
note the commit mentioned in the description is for trusty, but there are similar commits for x/y/z/a that make autopkgtest fail for those releases as well in the same way. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724044 Title: autopkgtest regression due to only building single FLAVOUR Status in linux package in Ubuntu: New Bug description: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724044] [NEW] autopkgtest regression due to only building single FLAVOUR
Public bug reported: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724044 Title: autopkgtest regression due to only building single FLAVOUR Status in linux package in Ubuntu: New Bug description: commit 7a4e330a7f82869d161462b6f4b47f7d8ff963f2 (for trusty kernel) changed autopkgtest to only build the first 'flavour'. However, this causes failure on armhf because the 'lpae' flavour is still expected, e.g.: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-trusty/trusty/armhf/l/linux/20171012_203950_bf028@/log.gz Debug: do-binary-udebs dh_testdir dh_testroot # unpack the kernels into a temporary directory mkdir -p debian/d-i-armhf imagelist=$(cat /tmp/autopkgtest.XJHwMz/build.6rB/linux-3.13.0/debian/build/kernel-versions | grep ^armhf | gawk '{print $4}') && \ for i in $imagelist; do \ dpkg -x $(ls ../linux-image-$i\_3.13.0-133.182_armhf.deb) \ debian/d-i-armhf; \ if [ -f ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb ] ; then \ dpkg -x ../linux-image-extra-$i\_3.13.0-133.182_armhf.deb \ debian/d-i-armhf; \ fi; \ /sbin/depmod -b debian/d-i-armhf $i; \ done ls: cannot access ../linux-image-3.13.0-133-generic-lpae_3.13.0-133.182_armhf.deb: No such file or directory dpkg-deb: error: --extract needs a target directory. Either this should be reverted to build all flavours, or the build/autopkgtest needs to updated also to not expect the lpae flavour (or other than base flavour). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1683184] Re: GPU problems on HP 15-ba009ng
I can confirm that Kernel 4.13 in ubuntu 17.10 beta 2 fixes this problem. No work around is needed to boot into the system or live media. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1683184 Title: GPU problems on HP 15-ba009ng Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: Problem description: The notebook does not work when not booted using nomodeset: It is not possible to login - after logging in the login screen shows up (sometimes the computer also shuts down, or shows information similiar to the shutdown screen (not using quiet splash boot options, so it is white text on black background)), until the login screen shows up again, only the background image is shown. When using an USB stick, plymouth hangs after some time. When using a text console to login instead of a graphical session, one can login, but sees how the console gets spammed with the following lines repeating itself frequently: [ XXX.XX] AMD-Vi: Event logged [ (usually once) [ XXX.XX] AMD-Vi: Completion-Wait loop timed out (usually twice) When using nomodeset, things work fine, but I only get software rendering (I do not intend using the notebook as a loud heating). During startup I found the following, potentially related messages: (...) [0.718421] ACPI Error: Method parse/execution failes [\_SB.WLBU._STA] (Node 94cad68b6b68), AE_NOT_FOUND (20160930/psparse-543) [6.291431] amd_gpio AMD0030:00: Failed to get gpio IRQ. (plymouth started showing some boot screen) And, during a different startup (please note this is transcribed from an older photo, Ubuntu version can be an early version of zesty, but also might be yakkety): (...) [ 12.950688] amdgpu :05:00.0:fence driver on ring 10 use gpu addr 0x000100b0, cpu addr 0x8a4fcb63d0b0 [ 12.954029] can't get the mac of 5 [ 12.960416] [drm] ring test on 0 succeeded in 16 usecs (other ring tests, until:) [ 12.966726] [drm] ring test on 10 succeeded in 6 usecs [ 12.967789] [drm] ib test on ring 0 succeeded (other ib test, until:) [ 12.985277] [drm] ib test on ring 10 succeeded [ 12.985277] [drm] Initialized amdgpu 3.9.0 20150101 for :05:00.0 on minor 1 Begin: Loading essential drivers ... done. (...) Ubuntu version: Ubuntu 17.04 (16.04 had less problems, with 16.10 installation failed) Hardware: Notebook: HP 15-ba009ng CPU: AMD A10-9600P GPU: AMD Radeon R7 M440 4 GB DDR3-RAM (according to the web page of the vendor) xorg version: 1:7.7+16ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: xorg 1:7.7+16ubuntu3 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 .tmp.unity_support_test.1: ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7 Date: Sun Apr 16 22:24:26 2017 DistUpgraded: 2017-03-11 13:02:33,428 DEBUG apt btrfs snapshots supported: True DistroCodename: zesty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev ca) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Carrizo [103c:81fa] Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] [103c:81fa] InstallationDate: Installed on 2016-12-25 (112 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: HP HP Notebook ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic.efi.signed root=UUID=af212aa7-7cfe-4e46-a312-da2a25fb0df1 ro rootflags=subvol=@ nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to zesty on 2017-03-11 (36 days ago) dmi.bios.date: 09/01/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.17 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 81FA dmi.board.vendor: HP dmi.board.version: 67.34 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.17:bd09/01/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81FA:rvr67.34:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Kernel-packages] [Bug 1722302] Packages outside of proper component
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
The following packages ended up in the wrong component in the -proposed pocket: linux-aws 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-cloud-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-headers-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002 4.4.0-1002.2 - is in universe instead of main linux-aws-tools-4.4.0-1002-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-cloud-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-headers-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-image-4.4.0-1002-aws-dbgsym 4.4.0-1002.2 - is in universe instead of main linux-tools-4.4.0-1002-aws 4.4.0-1002.2 - is in universe instead of main linux-meta-aws 4.4.0.1002.2 - is in universe instead of main linux-aws 4.4.0.1002.2 - is in universe instead of main linux-headers-aws 4.4.0.1002.2 - is in universe instead of main linux-image-aws 4.4.0.1002.2 - is in universe instead of main linux-tools-aws 4.4.0.1002.2 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again ** 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 => Incomplete ** 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 ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Incomplete => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 promote-to-proposed series: Incomplete 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: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
linux-image-4.10.0-37-generic Commit b1943b80d393d40a75c7fd0679f51d6f998d28d5 fixed the problem. Wifi not working again 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/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723223] Re: linux-lts and linux-hwe autopkgtests fail due to version mismatch
** Description changed: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 - exit 1 + echo "ERROR: running version does not match source package" 1>&2 + exit 1 fi - - However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. + However, when testing a -lts or -hwe kernel build, the running kernel + will not match because the running kernel is the stock version while the + building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that - invoke linux autopkgtests - for example, initramfs-tools. This requires - unnecessary work to investigate the autopkgtest errors every time, only - to find it's a autopkgtest error. + invoke linux autopkgtests - for example, initramfs-tools, systemd, ... + This requires unnecessary work to investigate the autopkgtest errors + every time, only to find it's a autopkgtest error. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723223 Title: linux-lts and linux-hwe autopkgtests fail due to version mismatch Status in linux package in Ubuntu: Invalid Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: In Progress Bug description: the autopkgtests for the kernel include 'ubuntu-regression-suite' which contains this test: sver=`dpkg-parsechangelog -SVersion` read x rver x &2 exit 1 fi However, when testing a -lts or -hwe kernel build, the running kernel will not match because the running kernel is the stock version while the building/testing kernel is the newer -lts/-hwe version. This failure results in autopkgtest errors for all other packages that invoke linux autopkgtests - for example, initramfs-tools, systemd, ... This requires unnecessary work to investigate the autopkgtest errors every time, only to find it's a autopkgtest error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
This bug was fixed in the package dkms - 2.2.0.3-2ubuntu11.5 --- dkms (2.2.0.3-2ubuntu11.5) xenial; urgency=medium * 0014-remove-initrd-backup.patch: When removing a kernel also remove related .old-dkms file from /boot after its been created not before. (LP: #1515513) -- Brian MurrayThu, 05 Oct 2017 13:14:20 -0700 ** Changed in: dkms (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: New Status in dkms source package in Zesty: Fix Released Status in initramfs-tools source package in Zesty: New Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Re: /boot/initrd.img-*.old-dkms files left behind
This bug was fixed in the package dkms - 2.3-3ubuntu1.2 --- dkms (2.3-3ubuntu1.2) zesty; urgency=medium * 0014-remove-initrd-backup.patch: When removing a kernel also remove related .old-dkms file from /boot after its been created not before. (LP: #1515513) -- Brian MurrayThu, 05 Oct 2017 11:45:16 -0700 ** Changed in: dkms (Ubuntu Zesty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: New Status in dkms source package in Zesty: Fix Released Status in initramfs-tools source package in Zesty: New Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1515513] Update Released
The verification of the Stable Release Update for dkms has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1515513 Title: /boot/initrd.img-*.old-dkms files left behind Status in dkms package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Confirmed Status in dkms source package in Xenial: Fix Released Status in initramfs-tools source package in Xenial: New Status in dkms source package in Zesty: Fix Released Status in initramfs-tools source package in Zesty: New Status in dkms package in Debian: New Bug description: [Impact] If a dkms package is installed which has REMAKE_INITRD or the same setting has be manually configured by a user then when a kernel is removed its possible for an ".old-dkms" file to be left in /boot with no associated kernel. [Test Case] On a system with two old kernels and one new kernel available in -updates: 1) install r8168-dkms 2) install the dkms module for the old kernel e.g. 'sudo dkms install -m r8168 -v 8.041.00 -k 4.4.0-31-generic' 3) upgrade your kernel e.g. "sudo apt install linux-image-generic' 4) sudo apt autoremove 5) observe something like "initrd.img-4.4.0-31-generic.old-dkms" in /boot without a corresponding "initrd.img-4.4.0-31-generic" With the version of dkms in -proposed, the .old-dkms file will be removed when the kernel is auto removed. [Regression Potential] Somebody out there might expect the .old-dkms file to be kept, but that seems like an odd expectation. One notices *.old-dkms files being left behind still sitting on the disk after purging the related kernel. This can cause /boot to become full, and when it gets really bad, even sudo apt-get autoremove won't fix the problem - only deleting the old-dkms files manually solves the problem. Note: Filling up the /boot partition causes updates to fail. ProblemType: BugDistroRelease: Ubuntu 15.04 Package: dkms 2.2.0.3-2ubuntu3.3 ProcVersionSignature: Ubuntu 3.19.0-28.30-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.7 Architecture: amd64 CurrentDesktop: KDE Date: Thu Nov 12 08:17:10 2015 InstallationDate: Installed on 2015-05-05 (190 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: allSourcePackage: dkms UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1515513/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1705748] Re: Samsung SSD 960 EVO 500GB refused to change power state
The fault is mine. Didn't take out-of-tree proprietary modules into account. Please try artful kernel here: http://people.canonical.com/~khfeng/lp1705748-artful/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1705748 Title: Samsung SSD 960 EVO 500GB refused to change power state Status in linux package in Ubuntu: Triaged Bug description: Originally thought my issue was same as this: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 but requested to report as separate bug System becomes unusable at seemingly random times but especially after resume from suspend due to disk 'disappearing' becoming inaccessible, with hundreds of I/O errors logged. After viewing the above bug report yesterday as a quick temporary fix I added kernel param, updated grub, etc with: GRUB_CMDLINE_LINUX_DEFAULT="nvme_core.default_ps_max_latency_us=0" System appears to have been stable for the last day, but is presumably using more power than it should. System, drive details below: M2 nvme drive: Samsung SSD 960 EVO 500GB Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 M/B Asus Prime B350m-A Ryzen 1600 cpu Jul 20 16:32:59 phs08 kernel: [ 190.893571] INVALID_DEVICE_REQUEST device=00:00.0 address=0xfffdf800 flags=0x0a00] Jul 20 16:33:05 phs08 kernel: [ 197.010928] nvme :01:00.0: controller is down; will reset: CSTS=0x, PCI_STATUS=0x Jul 20 16:33:05 phs08 kernel: [ 197.046980] pci_raw_set_power_state: 4 callbacks suppressed Jul 20 16:33:05 phs08 kernel: [ 197.046985] nvme :01:00.0: Refused to change power state, currently in D3 Jul 20 16:33:05 phs08 kernel: [ 197.047163] nvme nvme0: Removing after probe failure status: -19 Jul 20 16:33:05 phs08 kernel: [ 197.047182] nvme0n1: detected capacity change from 500107862016 to 0 Jul 20 16:33:05 phs08 kernel: [ 197.047793] blk_update_request: I/O error, dev nvme0n1, sector 0 nvme list /dev/nvme0n1 S3EUNX0J305518L Samsung SSD 960 EVO 500GB 1.2 1 125.20 GB / 500.11 GB 512 B + 0 B 2B7QCXE7 sudo nvme id-ctrl /dev/nvme0 NVME Identify Controller: vid : 0x144d ssvid : 0x144d sn : S3EUNX0J305518L mn : Samsung SSD 960 EVO 500GB fr : 2B7QCXE7 rab : 2 ieee : 002538 cmic : 0 mdts : 9 cntlid : 2 ver : 10200 rtd3r : 7a120 rtd3e : 4c4b40 oaes : 0 oacs : 0x7 acl : 7 aerl : 3 frmw : 0x16 lpa : 0x3 elpe : 63 npss : 4 avscc : 0x1 apsta : 0x1 wctemp : 350 cctemp : 352 mtfa : 0 hmpre : 0 hmmin : 0 tnvmcap : 500107862016 unvmcap : 0 rpmbs : 0 sqes : 0x66 cqes : 0x44 nn : 1 oncs : 0x1f fuses : 0 fna : 0x5 vwc : 0x1 awun : 255 awupf : 0 nvscc : 1 acwu : 0 sgls : 0 ps 0 : mp:6.04W operational enlat:0 exlat:0 rrt:0 rrl:0 rwt:0 rwl:0 idle_power:- active_power:- ps 1 : mp:5.09W operational enlat:0 exlat:0 rrt:1 rrl:1 rwt:1 rwl:1 idle_power:- active_power:- ps 2 : mp:4.08W operational enlat:0 exlat:0 rrt:2 rrl:2 rwt:2 rwl:2 idle_power:- active_power:- ps 3 : mp:0.0400W non-operational enlat:210 exlat:1500 rrt:3 rrl:3 rwt:3 rwl:3 idle_power:- active_power:- ps 4 : mp:0.0050W non-operational enlat:2200 exlat:6000 rrt:4 rrl:4 rwt:4 rwl:4 idle_power:- active_power:- --- ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: drgrumpy 2192 F pulseaudio /dev/snd/pcmC1D0p: drgrumpy 2192 F...m pulseaudio /dev/snd/controlC1: drgrumpy 2192 F pulseaudio DistroRelease: Linux 18.2 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=a6896cdd-6bac-4e7f-9e13-55460859c3ec InstallationDate: Installed on 2017-07-06 (15 days ago) InstallationMedia: Linux Mint 18.2 "Sonya" - Release amd64 20170628 IwConfig: lono wireless extensions. enp37s0 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic root=UUID=f7ae652b-cbf6-48b8-bc6a-d3963957ab57 ro nvme_core.default_ps_max_latency_us=0 ProcVersionSignature: Ubuntu 4.10.0-26.30~16.04.1-generic 4.10.17 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.10.0-26-generic N/A linux-backports-modules-4.10.0-26-generic N/A linux-firmware 1.157.11 RfKill: Tags: sonya Uname: Linux 4.10.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload:
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
Please try Linux kernel here: http://people.canonical.com/~khfeng/lp1723736/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
I built the next test kernel, up to the following commit: b1943b80d393d40a75c7fd0679f51d6f998d28d5 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1723174 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes
It looks like you may have already tested 4.12 final per comment #6. If so, we just need to figure out which 4.13 release candidate introduced the fix. So if v4.13-rc1 is still bad, we would next test -rc2, -rc3, etc until we find the good version. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721856] Re: Suspend ends after seconds and laptop resumes
To perform a bisect, we need to identify linear versions. Can you test the following two kernels: v4.12 final: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.12/ v4.13-rc1: http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.13-rc1/ ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Zesty) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Zesty) Status: Triaged => 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/1721856 Title: Suspend ends after seconds and laptop resumes Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: The suspend/standby ends after seconds and the laptop resumes like it'd wake up from suspend. I didn't use suspend for a long time (months or years) and can't even estimate when it worked for the last time. This issue is fixed in 4.14-rc3 mainline kernel - although some parts of the installation don't work, like ZFS and nvidia-340 which might cause the problem as well. I'm willing to do git bisect work if you confirm me that this makes sense. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-35-generic 4.10.0-35.39 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: BEN.PID ZUGR. BEFEHL /dev/snd/controlC0: richter 18896 F pulseaudio CurrentDesktop: XFCE Date: Fri Oct 6 20:21:35 2017 HibernationDevice: RESUME=UUID=1bb0bb3e-8148-4957-9673-9701bd571c0a InstallationDate: Installed on 2015-12-12 (664 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: LENOVO 20221 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic root=UUID=791b47e7-915d-4d5a-bce0-d7e9b660a2ab ro rootflags=subvol=ubuntu-main-root RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-05-01 (158 days ago) dmi.bios.date: 07/12/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 71CN51WW(V1.21) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: 3193WIN8 STD MLT dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Z500 Touch dmi.modalias: dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch: dmi.product.name: 20221 dmi.product.version: Lenovo IdeaPad Z500 Touch dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721856/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723583] Re: BUG: unable to handle kernel NULL pointer dereference at 00000004
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723583 Title: BUG: unable to handle kernel NULL pointer dereference at 0004 Status in linux package in Ubuntu: Incomplete Bug description: Just booted up computer. ProblemType: KernelOops DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic i686 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.7-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: charlie2351 F pulseaudio Date: Sat Oct 14 09:11:41 2017 DuplicateSignature: BUG: unable to handle kernel NULL pointer dereference at location EIP: bio_uncopy_user+0xc3/0x140 SS:ESP: 0068:f43c5d0c Failure: oops InstallationDate: Installed on 2017-07-28 (77 days ago) InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Alpha i386 (20170725.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: NOVATECH LTD PERSONAL COMPUTER ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=650586f6-4f8f-4d72-853f-15154b747716 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: BUG: unable to handle kernel NULL pointer dereference at 0004 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H81M-DS2V dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: xxx-xxx dmi.chassis.type: 3 dmi.chassis.vendor: NOVATECH LTD dmi.chassis.version: V1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd06/19/2014:svnNOVATECHLTD:pnPERSONALCOMPUTER:pvrV1.0:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-DS2V:rvrTobefilledbyO.E.M.:cvnNOVATECHLTD:ct3:cvrV1.0: dmi.product.family: AMI PLATFORM dmi.product.name: PERSONAL COMPUTER dmi.product.version: V1.0 dmi.sys.vendor: NOVATECH LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723612] Re: new laptop: Lenovo Y520-15IKBM no wireless networks found
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723612 Title: new laptop: Lenovo Y520-15IKBM no wireless networks found Status in linux package in Ubuntu: Triaged Bug description: platform/x86: ideapad-laptop: Add Y720-15IKBM to no_hw_rfkill Lenovo Legion Y720-15IKBM is yet another Lenovo model that does not have an hw rfkill switch, resulting in wifi always reported as hard blocked. Please add the model to the list of models without rfkill switch, in module ideapad-laptop ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: loek 2044 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 16:14:40 2017 HibernationDevice: RESUME=UUID=4864f7b1-0f01-42de-8c0b-fe93495c315f InstallationDate: Installed on 2017-10-09 (4 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:2414 Syntek Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80YY ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-37-generic.efi.signed root=UUID=349aa14b-4edc-478e-9b00-da8d368233f8 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-37-generic N/A linux-backports-modules-4.10.0-37-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 5XCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y520-15IKBM dmi.modalias: dmi:bvnLENOVO:bvr5XCN13WW:bd09/07/2017:svnLENOVO:pn80YY:pvrLenovoY520-15IKBM:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoY520-15IKBM: dmi.product.name: 80YY dmi.product.version: Lenovo Y520-15IKBM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723613] Re: xserver fail after upgrade from image-4.10.0-37-generic
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key needs-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723613 Title: xserver fail after upgrade from image-4.10.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: blank screen after boot, rebooting with previous kernel work fine ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuele 2283 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 12:58:08 2017 HibernationDevice: RESUME=UUID=cd4e1983-2ff1-4199-b9a1-ba1cb0175aaf InstallationDate: Installed on 2016-07-09 (461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ZOTAC XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=b483e7af-edbd-49ca-a3bd-542c88843248 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-06-11 (124 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B273P018 dmi.board.asset.tag: N/A dmi.board.name: XX dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 2 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB273P018:bd04/06/2016:svnZOTAC:pnXX:pvrXX:rvnZOTAC:rnXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring: dmi.product.name: XX dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723613] Re: xserver fail after upgrade from image-4.10.0-37-generic
If the bug still exists in mainline, we can perform a kernel bisect to identify the commit that introduced this regression. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723613 Title: xserver fail after upgrade from image-4.10.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: blank screen after boot, rebooting with previous kernel work fine ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-35.39-generic 4.10.17 Uname: Linux 4.10.0-35-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: emanuele 2283 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 12:58:08 2017 HibernationDevice: RESUME=UUID=cd4e1983-2ff1-4199-b9a1-ba1cb0175aaf InstallationDate: Installed on 2016-07-09 (461 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: ZOTAC XX ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic root=UUID=b483e7af-edbd-49ca-a3bd-542c88843248 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-35-generic N/A linux-backports-modules-4.10.0-35-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: Upgraded to zesty on 2017-06-11 (124 days ago) dmi.bios.date: 04/06/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: B273P018 dmi.board.asset.tag: N/A dmi.board.name: XX dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 2 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrB273P018:bd04/06/2016:svnZOTAC:pnXX:pvrXX:rvnZOTAC:rnXX:rvrXX:cvnDefaultstring:ct2:cvrDefaultstring: dmi.product.name: XX dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723613/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723607] Re: TouchPad don't work
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723607 Title: TouchPad don't work Status in linux package in Ubuntu: Incomplete Bug description: I've got a MSI gl62 6qf and my touchpad isn't recognize by (I think) kernel even when I list /proc/bus/input/devices : { 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/input0 U: Uniq= H: Handlers=sysrq kbd event0 leds B: PROP=0 B: EV=120013 B: KEY=60070290 8380207af040d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=0738 Product=1722 Version=0111 N: Name="Mad Catz Mad Catz R.A.T. Pro S" P: Phys=usb-:00:14.0-3/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:0738:1722.0001/input/input1 U: Uniq=Example# H: Handlers=mouse0 event1 B: PROP=0 B: EV=17 B: KEY=1fff 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0003 Vendor=0738 Product=1722 Version=0111 N: Name="Mad Catz Mad Catz R.A.T. Pro S" P: Phys=usb-:00:14.0-3/input2 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.2/0003:0738:1722.0003/input/input2 U: Uniq=Example# H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff9f207ac14057ff febeffdfffef fffe B: MSC=10 B: LED=1f I: Bus=0003 Vendor=0738 Product=1722 Version=0111 N: Name="Mad Catz Mad Catz R.A.T. Pro S" P: Phys=usb-:00:14.0-3/input3 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.3/0003:0738:1722.0004/input/input3 U: Uniq=Example# H: Handlers=kbd event3 B: PROP=0 B: EV=1f B: KEY=3007f 0 0 48317aff32d bf56 1 130f938b17c000 677bfad9415fed 9ed6804400 1002 B: REL=40 B: ABS=1 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input4 U: Uniq= H: Handlers=event4 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input5 U: Uniq= H: Handlers=event5 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input6 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 } I just see my USB mouse ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-37-generic 4.10.0-37.41 ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17 Uname: Linux 4.10.0-37-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oki28z 1747 F pulseaudio CurrentDesktop: Unity:Unity7 Date: Sat Oct 14 15:52:52 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-06-05 (130 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0738:1722 Mad Catz, Inc. Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International
[Kernel-packages] [Bug 1723736] Re: Touchpad not detected - Lenovo ideapad 320-15IKB
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723736 Title: Touchpad not detected - Lenovo ideapad 320-15IKB Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 17.04 Release: 17.04 Basically the same bug as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1708852 I'm using a Lenovo ideapad 320-15IKB, though. I also tried the latest mainline kernel (4.13.7) which didn't help. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: boot/vmlinuz-4.10.0-19-generic] ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: meradanis 1747 F pulseaudio CurrentDesktop: GNOME Date: Sun Oct 15 14:23:54 2017 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=912e6e24-9770-4e44-914b-9d181193c23d InstallationDate: Installed on 2017-10-14 (0 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: LENOVO 81BG ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-19-generic root=UUID=a7c89b92-6e62-49e5-a4b0-052b751a2d6e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.10.0-19-generic N/A linux-backports-modules-4.10.0-19-generic N/A linux-firmware 1.164.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2017 dmi.bios.vendor: LENOVO dmi.bios.version: 6JCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 320-15IKB dmi.modalias: dmi:bvnLENOVO:bvr6JCN14WW:bd09/28/2017:svnLENOVO:pn81BG:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB: dmi.product.name: 81BG dmi.product.version: Lenovo ideapad 320-15IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723680] Re: GPU Hang in Xorg rcs0 drm/i915
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Tags added: kernel-da-key ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723680 Title: GPU Hang in Xorg rcs0 drm/i915 Status in linux package in Ubuntu: Incomplete Bug description: Distributor ID: Ubuntu Description: Ubuntu Artful Aardvark (development branch) Release: 17.10 Codename: artful When using linux kernel linux-image-4.13.0-12-generic to linux- image-4.13.0-16-generic Xorg fails to start with kernel error messages below. Kernel boots and displays messages allows for GUI to enter disk encryption key then tries to start Xorg login. Shows blank screen, sometimes part of login dialog. Then hangs and goes blank usually showing the low graphics mode error screen from Xorg and no functionality after a while. Can ctrl+alt+f1 to console. Using linux-image-4.10.0-35-generic everything works as expected. System worked without issue with Ubuntu 17.04 Kernel error messages: [ 43.836641] [drm] GPU HANG: ecode 8:0:0x00df, in Xorg [1027], reason: Hang on rcs0, action: reset [ 43.836645] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 43.836646] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 43.836647] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 43.836648] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 43.836649] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 43.836718] drm/i915: Resetting chip after gpu hang [ 55.812149] drm/i915: Resetting chip after gpu hang [ 63.840645] drm/i915: Resetting chip after gpu hang [ 71.836614] drm/i915: Resetting chip after gpu hang [ 79.836882] drm/i915: Resetting chip after gpu hang [ 88.828508] drm/i915: Resetting chip after gpu hang have tried kernel parameter intel_iommu=off, intel_iommu=igfx_off, i915.enable_rc6=0 with no better results. lshw, dmesg and card0/error file attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723680/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723777] Re: Apple bluetooth USB driver is 100% busy despite BT switched off
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723777 Title: Apple bluetooth USB driver is 100% busy despite BT switched off Status in linux package in Ubuntu: Incomplete Bug description: Just upgraded from 17.04 to 17.10 on a 2011 macbook air. Battery drain is markedly more severe. Looking at powertop, the main difference is that the Apple USB Bluetooth driver is drawing ~2.5W and is showing as 100% busy. Bluetooth is switched off. I have tried rfkill, blacklisting btusb, modifying the /etc/bluetooth/main.conf to not autoenable and to set InitiallyPowered to false. None of these work. powertop output: 2.58 W100.0% Device USB device: Bluetooth USB Host Controller (Apple Inc.) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 11:45:16 2017 InstallationDate: Installed on 2014-11-09 (1070 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) InterestingModules: bluetooth MachineType: Apple Inc. MacBookAir4,2 ProcEnviron: LANG=en_US.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=58091989-ee9b-4c99-afa8-fffa56a1f3af ro quiet splash crashkernel=384M-:128M vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to artful on 2017-10-15 (0 days ago) dmi.bios.date: 06/08/2015 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBA41.88Z.0077.B12.1506081728 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-742912EFDBEE19B3 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookAir4,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-742912EFDBEE19B3 dmi.modalias: dmi:bvnAppleInc.:bvrMBA41.88Z.0077.B12.1506081728:bd06/08/2015:svnAppleInc.:pnMacBookAir4,2:pvr1.0:rvnAppleInc.:rnMac-742912EFDBEE19B3:rvrMacBookAir4,2:cvnAppleInc.:ct10:cvrMac-742912EFDBEE19B3: dmi.product.family: MacBook Air dmi.product.name: MacBookAir4,2 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. hciconfig: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721880] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1721880 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1721880 Title: can't disable wi-fi and system hangs on shutdown Status in linux package in Ubuntu: Incomplete Bug description: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723772] Re: Hibernation
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? We would like to see if this bug is already fixed upstream, so please test the latest upstream kernel. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723772 Title: Hibernation Status in linux package in Ubuntu: Incomplete Bug description: When the monitor in the modus hibernation gets, it works until then ok, even if I'm listenig to music, the music plays further. When I try to come back to use the computer the music stops and when I insert my password all the programs are closed, as if I had started the OS. Every windows are closed and you need to open eveything again. Just to inform: I use a Monitor Samsung 4K 28" through DisplayPort. On a desktop, not a laptop. If you need some more information that I may forgot, I try to answer as soon as possible. Thank you very much, Thiago Benites PS: I use the german version of Artful Aardvark --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 1032 F...m pulseaudio /dev/snd/controlC0: thiago 1032 F pulseaudio /dev/snd/controlC1: thiago 1032 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-02 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 32272R4 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 9SKT67AUS dmi.board.name: MAHOBAY dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnLENOVO:bvr9SKT67AUS:bd04/27/2013:svnLENOVO:pn32272R4:pvrThinkCentreM92p:rvnLENOVO:rnMAHOBAY:rvrWin8STDDPKTPG:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: 32272R4 dmi.product.version: ThinkCentre M92p dmi.sys.vendor: LENOVO --- ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: thiago 6664 F...m pulseaudio /dev/snd/controlC0: thiago 6664 F pulseaudio /dev/snd/controlC1: thiago 6664 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-10-02 (13 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: LENOVO 32272R4 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-16-generic.efi.signed root=UUID=49009627-59f0-42b5-a403-7fd1a9dfc065 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 RfKill: Tags: artful wayland-session Uname: Linux 4.13.0-16-generic x86_64 UpgradeStatus: No
[Kernel-packages] [Bug 1723799] Re: touchpad not working after resume on kernel 4.13
To see if this bug is fixed upstream, please test the latest upstream kernel. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14-rc5 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723799 Title: touchpad not working after resume on kernel 4.13 Status in linux package in Ubuntu: Incomplete Bug description: I'm running Ubuntu 17.10 [Ubuntu Artful Aardvark (development branch) installed from beta 2 ISO with latest apt update && apt dist-upgrade] with kernel: $ uname -rv 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 and after putting system to sleep via closing laptop lid and then resuming it by opening laptop lid makes touchpad not working. Kernel message buffer contains following error message after resume: PM: Device i2c-SYNA3105:00 failed to resume async: error -11 and I can find other people reporting similar issue on other distros: https://bugzilla.redhat.com/show_bug.cgi?id=1431375 https://bugzilla.kernel.org/show_bug.cgi?id=195949 https://bugzilla.redhat.com/show_bug.cgi?id=1442699 like in those other bug reports I can workaround the problem by: rmmod i2c-hid modprobe i2c-hid in systemd-suspend.service(8) post scripts. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-extra-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mkucharski 1367 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Oct 15 22:49:38 2017 HibernationDevice: RESUME=UUID=aa9acb18-b692-4020-9811-d58e5c8b8857 InstallationDate: Installed on 2017-10-06 (9 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05c8:03a1 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Timi TM1607 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2017 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: XMAKB200P0100 dmi.board.asset.tag: Any dmi.board.name: TM1607 dmi.board.vendor: Timi dmi.board.version: MP dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Timi dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrXMAKB200P0100:bd05/07/2017:svnTimi:pnTM1607:pvr:rvnTimi:rnTM1607:rvrMP:cvnTimi:ct10:cvrChassisVersion: dmi.product.family: Timibook dmi.product.name: TM1607 dmi.sys.vendor: Timi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 362075] Re: session logout after suspend
This problem persists on Ubuntu 16.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/362075 Title: session logout after suspend Status in NULL Project: Invalid Status in linux package in Ubuntu: Expired Bug description: In Kubuntu 9.04 Jaunty, my laptop lid down is set to suspend via guidance-power-manager. After I lid up, I am at the login screen, instead of the unlock screen dialog. WORKAROUND: Disable the "Lock screen on resume" option in the power management settings. To manage notifications about this bug go to: https://bugs.launchpad.net/null-and-void/+bug/362075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1719853] Re: Plantronics P610 does not support sample rate reading
The upstream kernel 4.14-rc5 contains a patch for this ALSA: usb-audio: Add sample rate quirk for Plantronics P610 https://patchwork.kernel.org/patch/9987737/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1719853 Title: Plantronics P610 does not support sample rate reading Status in linux package in Ubuntu: Incomplete Bug description: As per https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1622763/comments/29 and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1709282 , I believe the USB ID 0x047F 0xC02F needs to be added to quirks.c in order for me to use my Plantronics P610. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1719853/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1721880] Re: can't disable wi-fi and system hangs on shutdown
Yea, all ath10k devices are affected. Linux kernel based on 4.13.6 should land in Artful soon. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: network-manager (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/1721880 Title: can't disable wi-fi and system hangs on shutdown Status in linux package in Ubuntu: New Bug description: If I try to turn off wi-fi the system freezes for few seconds and after that internet is not working and I can't open settings anymore, even if the wi-fi tray icon still shows a connection. When I shutdown the system it says that "A stop job for network-manager and wpa supplicant is running" and I have to wait for 10-11 minutes. Suspension doesn't work neither. Everything was working just fine on 17.10 daily builds. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 6 23:18:01 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-22 (14 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170917) IpRoute: default via 192.168.1.254 dev wlp3s0 proto static metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.105 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlp3s0 wifi connected/org/freedesktop/NetworkManager/Devices/3 Alice_BO2f15ab74-48df-437b-b0a1-83bf31708fea /org/freedesktop/NetworkManager/ActiveConnection/1 enp2s0 ethernet unavailable /org/freedesktop/NetworkManager/Devices/2 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.4connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721880/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722302] Re: linux-aws: 4.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722302 Title: linux-aws: 4.4.0-1002.2 -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 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: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722335] Re: linux: 3.13.0-134.183 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722335 Title: linux: 3.13.0-134.183 -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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722336 derivatives: kernel-stable-phase-changed:Tuesday, 10. October 2017 20:34 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/1722335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1715073] Comment bridged from LTC Bugzilla
--- Comment From cls...@us.ibm.com 2017-10-16 12:32 EDT--- (In reply to comment #30) > Hi Carol, > > Could you please do one last check and let us know if we can close this bug? > > Thanks > Victor Verified with 4.10.0-37-generic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1715073 Title: SRIOV: warning if unload VFs Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Zesty: Fix Released Status in linux source package in Artful: Fix Released Bug description: == Comment: #0 - Carol L. Soto- 2017-02-23 16:11:47 == ---Problem Description--- When doing SRIOV if I unload VFs will see a warning: Feb 23 16:05:56 powerio-le11 kernel: [ 201.343397] mlx5_3:wait_for_async_commands:674:(pid 6272): done with all pending requests Feb 23 16:05:56 powerio-le11 kernel: [ 201.603999] iommu: Removing device 0004:01:00.2 from group 7 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604078] pci 0004:01: 0.2: [PE# 00] Removing DMA window #0 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604084] pci 0004:01: 0.2: [PE# 00] Disabling 64-bit DMA bypass Feb 23 16:05:56 powerio-le11 kernel: [ 201.604350] mlx5_core 0004:01:00.0: VF BAR0: [mem 0x2400-0x2401 64bit pref] shifted to [mem 0x2400-0x2401 64bit pref] (Disabling 1 VFs shifted by 0) Feb 23 16:05:56 powerio-le11 kernel: [ 201.604363] mlx5_core 0004:01:00.0: can't update enabled VF BAR0 [mem 0x2400-0x2401 64bit pref] Feb 23 16:05:56 powerio-le11 kernel: [ 201.604379] [ cut here ] Feb 23 16:05:56 powerio-le11 kernel: [ 201.604386] WARNING: CPU: 14 PID: 6272 at /build/linux-twbIHf/linux-4.10.0/drivers/pci/iov.c:584 pci_iov_update_resource+0x178/0x1d0 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604388] Modules linked in: mlx5_ib xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp kvm_hv kvm_pr kvm ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter bridge stp llc binfmt_misc ipmi_powernv ipmi_devintf uio_pdrv_genirq ipmi_msghandler uio vmx_crypto powernv_rng powernv_op_panel leds_powernv ibmpowernv ib_iser rdma_cm iw_cm ib_cm ib_core configfs iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi knem(OE) ip_tables x_tables autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_en ses enclosure scsi_transport_sas crc32c_vpmsum mlx5_core mlx4_core Feb 23 16:05:56 powerio-le11 kernel: [ 201.604451] tg3 ipr devlink Feb 23 16:05:56 powerio-le11 kernel: [ 201.604456] CPU: 14 PID: 6272 Comm: bash Tainted: G OE 4.10.0-8-generic #10-Ubuntu Feb 23 16:05:56 powerio-le11 kernel: [ 201.604457] task: c00f40a6d600 task.stack: c00f40ac8000 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604459] NIP: c06721b8 LR: c06721b4 CTR: Feb 23 16:05:56 powerio-le11 kernel: [ 201.604461] REGS: c00f40acb590 TRAP: 0700 Tainted: G OE(4.10.0-8-generic) Feb 23 16:05:56 powerio-le11 kernel: [ 201.604462] MSR: 9282b033 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604470] CR: 42424422 XER: 2000 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] CFAR: c0b49db4 SOFTE: 1 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR00: c06721b4 c00f40acb810 c143c900 0063 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR04: 0001 0539 c01fff70 00021a50 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR08: 0007 0007 0001 656d5b2030524142 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR12: 4400 cfb87e00 10180df8 10189e60 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR16: 10189ed8 c00fdd0a2400 c01fff97d180 c0d46268 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR20: c0d4e410 c0d41df8 c01fff97d190 c0d4d8d8 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR24: c0d4d8e0 c00fe8f460a0 0001 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604471] GPR28: c00fe8f80f80 c00fe8f46580 c00fe8f46000 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604498] NIP [c06721b8] pci_iov_update_resource+0x178/0x1d0 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604501] LR [c06721b4] pci_iov_update_resource+0x174/0x1d0 Feb 23 16:05:56 powerio-le11 kernel: [ 201.604501] Call
[Kernel-packages] [Bug 1722336] Re: linux-lts-trusty: 3.13.0-134.183~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1722336 Title: linux-lts-trusty: 3.13.0-134.183~precise1 -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: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722335 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
I can confirm that linux-image-4.10.0-37-generic Commit 8b1a7b0607a840e73e9b6fd15cc01d800742fe43 fixed the problem. Wifi not working 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/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
@Dimitri, yes I'll submit an SRU request. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: Incomplete Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1567597] Re: implement 'complain mode' in seccomp for developer mode with snaps
Hi - I tested the libseccomp SRU in Zesty using the following libseccomp package version: - libseccomp2 2.3.1-2.1ubuntu2~17.04.1 I tested it with the following kernels: - linux-image-4.10.0-37-generic 4.10.0-37.41 + does not contain seccomp logging patches - linux-image-4.10.0-38-generic 4.10.0-38.42 + contains seccomp logging patches + installed from zesty-proposed The libseccomp SRU testing was successful and followed what's documented in the [libseccomp Test Case] section of this bug description. ** Tags removed: verification-needed-zesty ** Tags added: verification-done-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/1567597 Title: implement 'complain mode' in seccomp for developer mode with snaps Status in Snappy: In Progress Status in libseccomp package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in libseccomp source package in Xenial: In Progress Status in linux source package in Xenial: Fix Committed Status in libseccomp source package in Zesty: Fix Committed Status in linux source package in Zesty: Fix Committed Bug description: A requirement for snappy is that a snap may be placed in developer mode which will put the security sandbox in complain mode such that violations against policy are logged, but permitted. In this manner learning tools can be written to parse the logs, etc and make developing on snappy easier. Unfortunately with seccomp only SCMP_ACT_KILL logs to dmesg and while we can set complain mode to permit all calls, they are not logged at this time. I've discussed this with upstream and we are working together on the approach. This may require a kernel patch and an update to libseccomp, to filing this bug for now as a placeholder and we'll add other tasks as necessary. UPDATE: ubuntu-core-launcher now supports the '@complain' directive that is a synonym for '@unrestricted' so people can at least turn on developer mode and not be blocked by seccomp. Proper complain mode for seccomp needs to still be implemented (this bug). [Impact] Snapd needs a way to log seccomp actions without blocking any syscalls in order to have a more useful complain mode. Such functionality has been acked upstream and patches are on their way into the Linux 4.14 kernel (backported to 4.12.0-13.14 in artful). The corresponding libseccomp changes are still undergoing review (https://github.com/seccomp/libseccomp/pull/92). The pull request adds a number of new symbols and probably isn't appropriate to backport until upstream has acked the pull request. However, only a small part of that larger pull request is needed by snapd and that change can be safely backported since the only added symbol, the SCMP_ACT_LOG macro, must match the SECCOMP_RET_LOG macro that has already been approved and merged in the upstream Linux kernel. [libseccomp Test Case] A large number of tests are ran as part of the libseccomp build. However, the "live" tests which test libseccomp with actual kernel enforcement are not ran at that time. They can be manually exercised to help catch any regressions. Note that on Artful, there's an existing test failure (20-live-basic_die%%002-1): $ sudo apt build-dep -y libseccomp $ sudo apt install -y cython $ apt source libseccomp $ cd libseccomp-* $ autoreconf -ivf && ./configure --enable-python && make check-build $ (cd tests && ./regression -T live) All tests should pass on zesty (12 tests) and xenial (10 tests). On artful, you'll see one pre-existing failure: ... Test 20-live-basic_die%%002-1 result: FAILURE 20-live-basic_die TRAP rc=159 ... Regression Test Summary tests run: 12 tests skipped: 0 tests passed: 11 tests failed: 1 tests errored: 0 Now we can build and run a small test program to test the SCMP_ACT_LOG action in the way that snapd wants to use it for developer mode: $ sudo apt install -y libseccomp-dev $ gcc -o lp1567597-test lp1567597-test.c -lseccomp $ ./lp1567597-test With a kernel that contains the logging patches and an updated libseccomp, the exit code should be 0 and you should have an entry in the system log that looks like this: audit: type=1326 audit(1505859630.994:69): auid=1000 uid=1000 gid=1000 ses=2 pid=18451 comm="lp1567597-test" exe="/home/tyhicks/lp1567597-test" sig=0 arch=c03e syscall=2 compat=0 ip=0x7f547352c5c0 code=0x7ffc If you have an updated libseccomp with an old kernel, you'll see that seccomp_init() fails due to the added compatibility check inside of libseccomp determines that the kernel doesn't have proper support for the new log action: $ ./lp1567597-test ERROR: seccomp_init: Invalid argument [Linux
[Kernel-packages] [Bug 1653456] Re: ASUS G752VS: Touchpad and Fn keys not working (Ubuntu 16.04.1/16.10/17.04)
No. I don't feel comfortable installing that patch. Firstly, because it is quite suspicious. Secondly, I will completely wipe out Windows from my machine in coming days, so even if the patch eventually works correctly - I think that without Windows the effect will most probably disappear. By the way, Google says that "touchpad works only after waking from suspend/hibernate" was not-so-rare problem in the recent past. -- You 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: Fix Released 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 I: Bus=0003 Vendor=04d9 Product=a070 Version=0110 N: Name="G-SPY USB Gaming Mouse" P: Phys=usb-:00:14.0-2/input0
[Kernel-packages] [Bug 1646277] Re: Xenial server 16.04.x will have a black screen after PXE installation
** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1722336] Re: linux-lts-trusty: 3.13.0-134.183~precise1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-trusty in Ubuntu. https://bugs.launchpad.net/bugs/1722336 Title: linux-lts-trusty: 3.13.0-134.183~precise1 -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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722335 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1722336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1723174] Re: Intel graphics problems on kernel 4.10.0-37-generic
I built the next test kernel, up to the following commit: 8b1a7b0607a840e73e9b6fd15cc01d800742fe43 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1723174 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1723174 Title: Intel graphics problems on kernel 4.10.0-37-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Zesty: In Progress Bug description: After kernel upgrade from 4.10.0-35 to 4.10.0-37 Ubuntu 17.04 works extremely slow. The reason is that i915 driver is UNCLAIMED now. Error from Xorg logs is: [ 56749.198] (EE) /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied Environment: Ubuntu 17.04 Kernel 4.10.0-37 Intel HD Graphics 520 INTEL GRAPHICS UPDATE TOOL FOR LINUX* OS V2.0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722306] Re: linux-aws: 4.4.0-1039.48 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1722306 Title: linux-aws: 4.4.0-1039.48 -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 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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1722299 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/1722306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 696435] Re: wait-for-root fails to detect nbd root
@jsalisbury that kernel is very nice, could you please cherrypick that patch and include it in the next available/convenient src:linux SRU? I have added the SRU template to the bug report. ** Description changed: + [Impact] + Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. + + [Fix] + Generate change uevent when size of /dev/nbd0 changes + + [Testcase] + * Start udevadm monitor + * modprobe nbd + * use ndb-client to connect something to /dev/nbd0 + * observe that there are change udev events generated on /dev/nbd0 itself + + [Regression Potential] + There is no change to existing uevents, or their ordering. + There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions + + [Original Bug Report] + When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: - nbd-client 1:2.9.16-6ubuntu1 - initramfs-tools 0.98.1ubuntu9 + nbd-client 1:2.9.16-6ubuntu1 + initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: - while [ -z "${FSTYPE}" ]; do - FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) + while [ -z "${FSTYPE}" ]; do + FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) - # Run failure hooks, hoping one of them can fix up the system - # and we can restart the wait loop. If they all fail, abort - # and move on to the panic handler and shell. - if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then - break - fi - done + # Run failure hooks, hoping one of them can fix up the system + # and we can restart the wait loop. If they all fail, abort + # and move on to the panic handler and shell. + if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then + break + fi + done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked and while it was still waiting. But I tried adding a "sleep 5" as the last line of local-top/nbd, so that the nbd message was displayed a lot before wait-for-root was called, and it didn't make a difference. So I don't think a race condition is involved in this problem. Temporarily I'm passing rootdelay=1 in the kernel command line to work around the 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/696435 Title: wait-for-root fails to detect nbd root Status in linux package in Ubuntu: Fix Released Status in nbd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Status in linux source package in Xenial: In Progress Status in systemd source package in Xenial: Incomplete Bug description: [Impact] Kernel does not generate any events when ndb-client connects /dev/nbd0 devices, therefore it is impossible to monitor/react to the state of /dev/nbd0. [Fix] Generate change uevent when size of /dev/nbd0 changes [Testcase] * Start udevadm monitor * modprobe nbd * use ndb-client to connect something to /dev/nbd0 * observe that there are change udev events generated on /dev/nbd0 itself [Regression Potential] There is no change to existing uevents, or their ordering. There is now an addition change event which will cause systemd to mark ndb devices as ready and trigger appropriate actions [Original Bug Report] When using an nbd root, wait-for-root blocks for 30 seconds before booting continues successfully. Using Ubuntu Natty, related packages versions: nbd-client 1:2.9.16-6ubuntu1 initramfs-tools 0.98.1ubuntu9 The wait-for-root call from /usr/share/initramfs-tools/scripts/local: while [ -z "${FSTYPE}" ]; do FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30}) # Run failure hooks, hoping one of them can fix up the system # and we can restart the wait loop. If they all fail, abort # and move on to the panic handler and shell. if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then break fi done I replaced wait-for-root with a sh script that did `set >&2`, here are the relevant environment variables at the time wait-for-root was called: ROOT='/dev/nbd0' ROOTDELAY='' ROOTFLAGS='' ROOTFSTYPE='' nbdroot='192.168.0.1,2011' It's probably worth noting that "nbd0: unknown partition table" was displayed asynchronously 1-2 seconds after wait-for-root was invoked
[Kernel-packages] [Bug 1722335] Re: linux: 3.13.0-134.183 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722335 Title: linux: 3.13.0-134.183 -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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722336 derivatives: kernel-stable-phase-changed:Tuesday, 10. October 2017 20:34 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/1722335/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1722299] Re: linux: 4.4.0-98.121 -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 ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** 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: 1722301,1722302 derivatives: 1722303,1722304,1722306,1722308,1722310 - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Tuesday, 10. October 2017 14:36 UTC - -- swm properties -- boot-testing-requested: true phase: Uploaded + kernel-stable-phase:Promoted to proposed + kernel-stable-phase-changed:Monday, 16. October 2017 15:32 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722301,1722302 derivatives: 1722303,1722304,1722306,1722308,1722310 -- swm properties -- boot-testing-requested: true - phase: Uploaded - kernel-stable-phase:Promoted to proposed - kernel-stable-phase-changed:Monday, 16. October 2017 15:32 UTC + phase: Promoted to proposed + proposed-announcement-sent: true + proposed-testing-requested: true -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1722299 Title: linux: 4.4.0-98.121 -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 snap-certification-testing series: New Status in Kernel SRU Workflow snap-publish series: New Status in Kernel SRU Workflow snap-qa-testing series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable series: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: 1722301,1722302 derivatives: 1722303,1722304,1722306,1722308,1722310 -- 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/1722299/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp