[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Please also run this in both the VM and on the host, and send us both outputs: lsusb -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
OK then, in the VM please open a Terminal (Ctrl+Alt+T) and run: rfkill > rfkill.txt and then attach the file 'rfkill.txt' here. Alternatively run: rfkill and just take a screenshot. ** Changed in: bluez (Ubuntu) Status: Invalid => 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837609] Re: xenial/linux: 4.4.0-158.186 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- + boot-testing-requested: true packages: main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Proposed - phase-changed: Monday, 29. July 2019 19:07 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 30. July 2019 03:21 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:depwait + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837609 Title: xenial/linux: 4.4.0-158.186 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- boot-testing-requested: true packages: main: linux meta: linux-meta signed: linux-signed phase: Ready for Promote to Proposed phase-changed: Tuesday, 30. July 2019 03:21 UTC reason: promote-to-proposed: Pending -- ready for review trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
** Attachment added: "newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279955/+files/newlog_kernel5.0.0-21-generic_repeateduntilitworks.txt -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Well, I see the problem also on real hardware, but it's harder to reproduce. In any case, I don't want to install a non-standard kernel there, so it is mixed up with the other problems with the 5.0 kernel. However, the VM *does* indeed have bluetooth. Virtualbox allows VMs to access any USB device on the host (when enabled). My BT controller is a usb device. For testing I disable BT on the host and later enable the VM to access the BT usb device; it works fine, ie. connects and disconnects as expected (and, yes, even plays music!). All from the VM. However the GUI problem is most apparent in the VM, running 5.2 kernel. I don't think using a VM is relevant, except that hardware timing will be different due to i/o instructions being trapped and re-executed on the host. If timing causes a problem, then it probably points to a race condition or similar bug. Anyway, as I mentioned the same symptom appears less frequently on bare hardware with the 5.0 kernel. I will attached output from journalctl -f for just one "snapback", and for a complete sequence eventually succeeding. Again, tjese were made with the older kernel. ** Attachment added: "newlog_kernel5.0.0-21-generic_onlyfirstsnapback.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279954/+files/newlog_kernel5.0.0-21-generic_onlyfirstsnapback.txt -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837632] Re: xenial/linux-azure: 4.15.0-1052.57 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837630 (trusty/linux-azure) derivatives: bug 1837629 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Security - phase-changed: Monday, 29. July 2019 07:11 UTC + phase: Ready for Security + phase-changed: Tuesday, 30. July 2019 03:10 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: trusty/linux-azure: bug 1837630 xenial/linux-azure-edge: bug 1834946 xenial/linux-azure/azure-kernel: bug 1837629 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1837632 Title: xenial/linux-azure: 4.15.0-1052.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837630 (trusty/linux-azure) derivatives: bug 1837629 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Security phase-changed: Tuesday, 30. July 2019 03:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: trusty/linux-azure: bug 1837630 xenial/linux-azure-edge: bug 1834946 xenial/linux-azure/azure-kernel: bug 1837629 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837474] Re: xenial/linux-snapdragon: 4.4.0-1121.127 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837473 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837476 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Security - phase-changed: Monday, 29. July 2019 07:11 UTC + phase: Ready for Security + phase-changed: Tuesday, 30. July 2019 03:11 UTC proposed-announcement-sent: true proposed-testing-requested: true + reason: + promote-to-security: Pending -- ready to copy trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1837473 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1837474 Title: xenial/linux-snapdragon: 4.4.0-1121.127 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Fix Released Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837473 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837476 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Security phase-changed: Tuesday, 30. July 2019 03:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1837473 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788336] Re: Failed to install nfs-kernel-server package on KVM kernels
** Changed in: ubuntu-kernel-tests Assignee: Po-Hsu Lin (cypressyew) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1788336 Title: Failed to install nfs-kernel-server package on KVM kernels Status in ubuntu-kernel-tests: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Bug description: When trying to install the nfs-kernel-server package on a KVM node running with X/X-KVM kernel, it will fail with service dependency issue. This is affecting the ubuntu_vfat_stress and ubuntu_ramfs_stress test. $ sudo apt-get install nfs-kernel-server Reading package lists... Done Building dependency tree Reading state information... Done nfs-kernel-server is already the newest version (1:1.2.8-9ubuntu12.1). 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Setting up nfs-kernel-server (1:1.2.8-9ubuntu12.1) ... A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. nfs-server.service couldn't start. locale: Cannot set LC_ALL to default locale: No such file or directory locale: Cannot set LC_ALL to default locale: No such file or directory A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. invoke-rc.d: initscript nfs-kernel-server, action "start" failed. ● nfs-server.service - NFS server and services Loaded: loaded (/lib/systemd/system/nfs-server.service; enabled; vendor preset: enabled) Active: inactive (dead) Aug 22 03:27:46 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:46 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:27:49 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:49 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:27:50 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:27:50 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:29:41 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:29:41 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. Aug 22 03:29:42 zeppo systemd[1]: Dependency failed for NFS server and services. Aug 22 03:29:42 zeppo systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'. dpkg: error processing package nfs-kernel-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nfs-kernel-server E: Sub-process /usr/bin/dpkg returned an error code (1) Log from journalctl -xe: http://paste.ubuntu.com/p/CxrWqGc2YT/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1031-kvm 4.4.0-1031.37 ProcVersionSignature: User Name 4.4.0-1031.37-kvm 4.4.134 Uname: Linux 4.4.0-1031-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Aug 22 03:28:11 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1788336/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724359] Re: no network after boot
** Changed in: linux-kvm (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1724359 Title: no network after boot Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: Fix Released Bug description: I have no network on an Openstack instance after trying to boot a minimized image with linux-kvm: [0.00] Linux version 4.4.0-1007-kvm (buildd@lgw01-13) (gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #12-Ubuntu SMP Tue Sep 12 18:30:13 UTC 2017 (Ubuntu 4.4.0-1007.12-kvm 4.4.83) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-1007-kvm root=PARTUUID=3a3cac6a-0f87-4d28-9995-64fbe0aacfb6 ro console=tty1 console=ttyS0 [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers' [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] x86/fpu: Using 'eager' FPU context switches. [0.00] e820: BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0009fbff] usable [0.00] BIOS-e820: [mem 0x0009fc00-0x0009] reserved [0.00] BIOS-e820: [mem 0x000f-0x000f] reserved [0.00] BIOS-e820: [mem 0x0010-0xbffdbfff] usable [0.00] BIOS-e820: [mem 0xbffdc000-0xbfff] reserved [0.00] BIOS-e820: [mem 0xfeffc000-0xfeff] reserved [0.00] BIOS-e820: [mem 0xfffc-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0001f57f] usable [0.00] NX (Execute Disable) protection: active [0.00] Hypervisor detected: KVM [0.00] e820: last_pfn = 0x1f5800 max_arch_pfn = 0x4 [0.00] x86/PAT: Configuration [0-7]: WB WT UC- UC WB WT UC- UC [0.00] e820: last_pfn = 0xbffdc max_arch_pfn = 0x4 [0.00] found SMP MP-table at [mem 0x000f6a50-0x000f6a5f] mapped at [880f6a50] [0.00] Using GB pages for direct mapping [0.00] ACPI: Early table checksum verification disabled [0.00] ACPI: RSDP 0x000F67F0 14 (v00 BOCHS ) [0.00] ACPI: RSDT 0xBFFE16BA 30 (v01 BOCHS BXPCRSDT 0001 BXPC 0001) [0.00] ACPI: FACP 0xBFFE0BDA 74 (v01 BOCHS BXPCFACP 0001 BXPC 0001) [0.00] ACPI: DSDT 0xBFFE0040 000B9A (v01 BOCHS BXPCDSDT 0001 BXPC 0001) [0.00] ACPI: FACS 0xBFFE 40 [0.00] ACPI: SSDT 0xBFFE0C4E 0009EC (v01 BOCHS BXPCSSDT 0001 BXPC 0001) [0.00] ACPI: APIC 0xBFFE163A 80 (v01 BOCHS BXPCAPIC 0001 BXPC 0001) [0.00] kvm-clock: Using msrs 4b564d01 and 4b564d00 [0.00] kvm-clock: cpu 0, msr 1:f57fc001, primary cpu clock [0.00] kvm-clock: using sched offset of 13480604670 cycles [0.00] clocksource: kvm-clock: mask: 0x max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns [0.00] Zone ranges: [0.00] DMA32[mem 0x1000-0x] [0.00] Normal [mem 0x0001-0x0001f57f] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x1000-0x0009efff] [0.00] node 0: [mem 0x0010-0xbffdbfff] [0.00] node 0: [mem 0x0001-0x0001f57f] [0.00] Initmem setup node 0 [mem 0x1000-0x0001f57f] [0.00] ACPI: LAPIC_NMI (acpi_id[0xff] dfl dfl lint[0x1]) [0.00] IOAPIC[0]: apic_id 0, version 17, address 0xfec0, GSI 0-23 [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 5 global_irq 5 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 10 global_irq 10 high level) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 11 global_irq 11 high level) [0.00] Using ACPI (MADT) for SMP configuration information [0.00] smpboot: Allowing 2 CPUs, 0 hotplug CPUs [0.00] e820: [mem 0xc000-0xfeffbfff] available for PCI devices [0.00] Booting paravirtualized kernel on KVM [0.00] clocksource: refined-jiffies: mask: 0x max_cycles: 0x, max_idle_ns:
[Kernel-packages] [Bug 1381016] Re: [Dell Alienware X51 R2] Unable to run hybrid-suspend on this system
** 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/1381016 Title: [Dell Alienware X51 R2] Unable to run hybrid-suspend on this system Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201303-13031 Dell Alienware X51 R2 This system can run S3 / S4 normally, but hybrid-sleep does not work on it. Steps: 1. Install 14.04.1 + nvidia-331 2. Try to run hybrid-sleep with fwts: sudo fwts --s3-hybrid --s3-sleep-delay=30 --s3-device-check --s3-device-check-delay=45 -P s3 Expected result: * System can go through hybrid-sleep normally. Actual result: * The display will be turned off, but the system is not suspended, if you move the mouse, ths display will be back, it acts just like nothing happened. The following message can be found in dmesg log: [ 75.308317] HybridSleep ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: ubuntu 1486 F pulseaudio /dev/snd/controlC0: ubuntu 1486 F pulseaudio /dev/snd/controlC1: ubuntu 1486 F pulseaudio CurrentDesktop: Unity Date: Tue Oct 14 06:29:40 2014 HibernationDevice: RESUME=UUID=6180570b-fc77-4230-8d27-df4f4b3d10f4 InstallationDate: Installed on 2014-10-13 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Alienware Alienware X51 R2 ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic.efi.signed root=UUID=08934195-682b-4b74-84b6-e80c7c86ae8b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/18/2013 dmi.bios.vendor: Alienware dmi.bios.version: A04 dmi.board.vendor: Alienware dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: 00 dmi.modalias: dmi:bvnAlienware:bvrA04:bd11/18/2013:svnAlienware:pnAlienwareX51R2:pvr00:rvnAlienware:rn:rvr:cvnAlienware:ct3:cvr00: dmi.product.name: Alienware X51 R2 dmi.product.version: 00 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1381016/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1407604] Re: [Dell Inspiron 7548] Brightness control does not work on 14.04.1
** 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/1407604 Title: [Dell Inspiron 7548] Brightness control does not work on 14.04.1 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201408-15450 Inspiron 7548 Brightness control does not work on this system with 14.04.1 The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: root@201408-15450:~$ ls /sys/class/backlight acpi_video0 intel_backlight root@201408-15450:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: charging /proc/acpi/battery/BAT0/state:present rate:474 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3811 mAh /proc/acpi/battery/BAT0/state:present voltage: 13006 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3900 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3900 mAh /proc/acpi/battery/BAT0/info:battery technology: non-rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11400 mV /proc/acpi/battery/BAT0/info:design capacity warning: 390 mAh /proc/acpi/battery/BAT0/info:design capacity low: 0 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 100 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 0 mAh /proc/acpi/battery/BAT0/info:model number:Dell /proc/acpi/battery/BAT0/info:serial number: 480 /proc/acpi/battery/BAT0/info:battery type:LION /proc/acpi/battery/BAT0/info:OEM info:SIMPLO /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/ADP1/state:state: on-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::07:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled root@201408-15450:~$ dmesg | grep 'ACPI: Video' [2.843516] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) root@201408-15450:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1512 F pulseaudio /dev/snd/controlC0: ubuntu 1512 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Jan 5 04:10:59 2015 HibernationDevice: RESUME=UUID=87828d2c-0d30-454b-90f1-ed89c2790e76 InstallationDate: Installed on 2015-01-05 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 7548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic.efi.signed root=UUID=4cf32401-def5-4cf9-a237-f0bfb729a6cc ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd11/19/2014:svnDellInc.:pnInspiron7548:pvrA00:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 7548 dmi.product.version: A00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1407604/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1454843] Re: 10ec:b723 Realtek RTL8723BE wireless card drops connection
** Changed in: linux (Ubuntu) Status: Triaged => 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/1454843 Title: 10ec:b723 Realtek RTL8723BE wireless card drops connection Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I am using Lenovo M30-70. I tried many workarounds from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1320070 but no change, the connection is lost after a while. Finally I tried the rtlwifi_new driver from https://bugzilla.kernel.org/show_bug.cgi?id=83641#c1. I first thought it works stable but after a while it also loses the connection (see my comment there). After reconnect it works for a while again. I uninstalled the rtlwifi_new driver for this bug report. (Bluetooth does not work at all, it doesn't find any devices) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-17-generic 3.19.0-17.17 ProcVersionSignature: Ubuntu 3.19.0-17.17-generic 3.19.6 Uname: Linux 3.19.0-17-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sledzik2179 F pulseaudio CurrentDesktop: Unity Date: Wed May 13 22:51:38 2015 HibernationDevice: RESUME=UUID=d61164da-04eb-444a-a976-6a1f91fc4ffb InstallationDate: Installed on 2015-03-11 (63 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: LENOVO ZIUS6 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-17-generic.efi.signed root=UUID=40721d88-7203-4dfa-ac65-1a2b204fea34 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-17-generic N/A linux-backports-modules-3.19.0-17-generic N/A linux-firmware 1.143 SourcePackage: linux UpgradeStatus: Upgraded to vivid on 2015-04-06 (36 days ago) dmi.bios.date: 10/15/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 8BCN45WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: INVALID dmi.board.vendor: LENOVO dmi.board.version: INVALID dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvr8BCN45WW(V3.08):bd10/15/2014:svnLENOVO:pnZIUS6:pvrINVALID:rvnLENOVO:rnINVALID:rvrINVALID:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: ZIUS6 dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1454843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1352816] Re: Sleep hotkey will trigger suspend twice on Dell laptop with 12.04.5
** Changed in: linux-lts-trusty (Ubuntu) Status: New => Won't Fix -- 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/1352816 Title: Sleep hotkey will trigger suspend twice on Dell laptop with 12.04.5 Status in HWE Next: Won't Fix Status in linux-lts-trusty package in Ubuntu: Won't Fix Bug description: This issue could be found on serval Dell Latitude laptops with 12.04.5 dailylive image (Aug.5) The Sleep hotkey would trigger suspend twice Steps: 1. Install the dailylive image for 12.04.5, boot to desktop 2. Try to suspend it with the sleep hotkey Expect result: * System suspended, after pressing the power button, it wakes from suspend, and everything works fine Actual result: * Suspend will be triggered twice: System suspended with power LED blinking -> press the power button System resumed from suspend, but few seconds later, it's suspended again. Also, call trace could be found in dmesg output from these systems: [11820.250541] [ cut here ] [11820.250548] WARNING: CPU: 0 PID: 40 at /build/buildd/linux-lts-trusty-3.13.0/drivers/base/firmware_class.c:1089 _request_firmware+0x1c4/0x1e0() [11820.250574] Modules linked in: ctr ccm nls_iso8859_1 rfcomm bnep snd_hda_codec_hdmi snd_hda_codec_idt arc4 joydev iwldvm mac80211 btusb bluetooth snd_hda_intel snd_hda_codec i915 iwlwifi snd_hwdep snd_pcm cfg80211 snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq mei_me drm_kms_helper mei drm snd_timer psmouse dell_wmi sparse_keymap snd_seq_device i2c_algo_bit snd serio_raw dell_laptop wmi ppdev parport_pc soundcore video mac_hid lpc_ich dcdbas snd_page_alloc lp parport usb_storage mmc_block ahci libahci tg3 ptp pps_core sdhci_pci sdhci [11820.250577] CPU: 0 PID: 40 Comm: kworker/u9:0 Tainted: GW 3.13.0-32-generic #57~precise1-Ubuntu [11820.250578] Hardware name: Dell Inc. Latitude E5430 non-vPro/0N0PKJ, BIOS A13 01/13/2014 [11820.250590] Workqueue: hci0 hci_power_on [bluetooth] [11820.250593] 0441 880078e67c18 81752c9e 81c4b718 [11820.250594] 880078e67c58 8106af7c [11820.250596] 88006eda9088 880078e67d10 880078e67d1c 3a98 [11820.250596] Call Trace: [11820.250602] [] dump_stack+0x46/0x58 [11820.250605] [] warn_slowpath_common+0x8c/0xc0 [11820.250607] [] warn_slowpath_null+0x1a/0x20 [11820.250609] [] _request_firmware+0x1c4/0x1e0 [11820.250610] [] request_firmware+0x3f/0x60 [11820.250613] [] btusb_setup_patchram+0x72/0x1d0 [btusb] [11820.250620] [] hci_dev_do_open+0x235/0x310 [bluetooth] [11820.250627] [] hci_power_on+0x3e/0x160 [bluetooth] [11820.250630] [] process_one_work+0x17f/0x4c0 [11820.250631] [] worker_thread+0x11b/0x3d0 [11820.250633] [] ? manage_workers.isra.21+0x190/0x190 [11820.250636] [] kthread+0xc9/0xe0 [11820.250637] [] ? flush_kthread_worker+0xb0/0xb0 [11820.250640] [] ret_from_fork+0x7c/0xb0 [11820.250642] [] ? flush_kthread_worker+0xb0/0xb0 [11820.250643] ---[ end trace 8bd327679ac10916 ]--- However, this issue also affects 201208-11587 Lenovo B470e laptop, but there is no such call trace could be found in dmesg output. Suspend with lid close or using the "Suspend" option in system menu works fine. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Tue Aug 5 05:36:39 2014 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140803) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1352816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1411514] Re: [Dell Precision M4800] Brightness can't be controlled on 14.04.1
** 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/1411514 Title: [Dell Precision M4800] Brightness can't be controlled on 14.04.1 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201305-13527 Dell Precision M4800 The screen brightness The brightness control does not work at all on 14.04.1 Steps: 1. Install 14.04.1 + update 2. Test the brightness control with hotkeys 3. Test the brightness control by using the "Brightness and Lock" applet. Expected results: * Brightness control should work in step 2 and 3 Actual result: * Brightness level would change with the hotkey, but the backlight level won't, nothing happened when you scroll the scrollbar in the "Brightness and Lock" applet. Debugging information: ubuntu@201305-13527:~$ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc 0x1d ^Ccaught signal 2, cleaning up... ubuntu@201305-13527:~$ ubuntu@201305-13527:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 225 press keycode 225 release keycode 224 press keycode 224 release keycode 29 press ^Ccaught signal 2, cleaning up... ubuntu@201305-13527:~$ ubuntu@201305-13527:~$ ls /sys/class/backlight/ acpi_video0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-44-generic 3.13.0-44.73 ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12 Uname: Linux 3.13.0-44-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1635 F pulseaudio ubuntu 2242 F pulseaudio /dev/snd/controlC0: ubuntu 1635 F pulseaudio ubuntu 2242 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Fri Jan 16 00:56:25 2015 HibernationDevice: RESUME=UUID=4e3c0183-4d3f-495e-8d6a-57e2b23e6412 InstallationDate: Installed on 2015-01-16 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Precision M4800 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=3edd6366-27b1-41af-88d4-ac1abe216d8f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-44-generic N/A linux-backports-modules-3.13.0-44-generic N/A linux-firmware 1.127.11 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/03/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0FVDR2 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/03/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0FVDR2:rvrX02:cvnDellInc.:ct9:cvr: dmi.product.name: Precision M4800 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1411514/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1708372] Re: The Precision Touchpad(PTP) button sends incorrect event code
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1708372 Title: The Precision Touchpad(PTP) button sends incorrect event code Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] The touchpad right button should send 273(BTN_RIGHT), and the left button should send 272(BTN_LEFT) But the touchpad right button sends 274(BTN_MIDDLE), and the left button sends 273 (BTN_RIGHT) [Fix] The fix is pretty simple to just decrease the event code by 1. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] The patch has strict if statement, so it won't affect other touchpad devices. And no more rework on this code snip after this commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1708372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764067] Re: Kernel 4.15 KVM not start
Hello, do you still seeing this with the latest 4.15 KVM kernel (4.15.0.1039.39)? Thanks. ** Changed in: launchpad-report-tool Status: In Progress => Invalid ** Changed in: launchpad-report-tool Assignee: Carlos Lopez Sanchez (car-lopsan) => (unassigned) ** Changed in: linux-kvm (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1764067 Title: Kernel 4.15 KVM not start Status in Launchpad Bug Report Tool: Invalid Status in linux-kvm package in Ubuntu: Incomplete Bug description: Ubuntu 18-04 and kernel 4.15 kvm not start . Binking cursor black window . To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-report-tool/+bug/1764067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1720977] Re: [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang
** Changed in: hwe-next Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1720977 Title: [Dell Docking IE][0bda:8153] Realtek USB Ethernet leads to system hang Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Zesty: Fix Released Bug description: [Impact] There is a USB Ethernet port, 0bda:8153, on Dell IE Docking. After plugged in the docking, system hard hangs. [Fix] This issue has been fix after v4.11-rc4, so after bisecting the kernel, we found the first bad commit, and realized this issue is from Realtek USB Ethernet driver with a non-initialized list. 98d068a r8152: fix the list rx_done may be used without initialization [Test Case] Verified on the Dell XPS and IE docking, and confirm this patch works. [Regression Potential] It's a one line patch and do the initialization of the list variable, there should be no any regression would be resulted from this. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1720977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1692836] Re: Dell XPS 9360 wifi 5G performance is poor
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1692836 Title: Dell XPS 9360 wifi 5G performance is poor Status in HWE Next: Fix Released Status in HWE Next xenial series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: TX throughput is not good in Ubuntu in IEEE 802.11ac mode. Measured Rx 60Mbit/s and Tx 12Mbit/s with Ubuntu Windows 10 (1607) performs much better with on transmit side Rx 73MBit/s and Tx 62MBit/s using the same hardware setup. Same result with WPA2 disabled in unencrypted mode. Steps to Reproduce: 1. connect to Wifi 2. copy a large file from XPS 13 to a share on a 2nd system To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1692836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1693393] Re: Power consumption issue on suspend-to-idle(s2idle)
** Changed in: hwe-next Status: In Progress => Fix Released ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Xenial) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1693393 Title: Power consumption issue on suspend-to-idle(s2idle) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: The power consumption is pretty high(8Watt) during suspend-to-idle mode under Xenial. 1. It consumes 8Watt under 4.4 kernel 2. It consumes 4Watt under 4.8 kernel 3. It consumes 2Watt under 4.11 kernel There are essential patches in 4.8 and 4.11 kernels, they are In 4.8 9d26d3a PCI: Put PCIe ports into D3 during suspend In 4.11 8d2c453 platform/x86: dell-laptop: Add Latitude 7480 and others to the DMI whitelist We need these 2 commits to have better s2idle support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1693393/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805088] Re: iwlwifi fails to work on 16 or more logical CPUs machines
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1805088 Title: iwlwifi fails to work on 16 or more logical CPUs machines Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] Got dmesg kernel BUG while loading iwlwifi driver on machines which has 16 or more logical CPUs kernel: RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] And it leads to wifi can't scan any APs, and leads to system hangs while suspending. [Fix] Below commit contained in v4.17 fix the issue. ab1068d6866e iwlwifi: pcie: compare with number of IRQs requested for, not number of CPUs [Regression Potential] Low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1805088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836983] Re: [Intel CyclonePeak] Pairing new BT mouse fails sometimes
** Changed in: linux-firmware (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux-firmware (Ubuntu Disco) Status: Fix Committed => Fix Released -- 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/1836983 Title: [Intel CyclonePeak] Pairing new BT mouse fails sometimes Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Disco: Fix Released Bug description: [Impact] After update the BT firmware, it requires to pair twice to pair a new device. There should be a "SMP: Pairing Request" send from hci0, but it doesn't be submitted in the first time. [Fix] The new firmware fix this issue. [Test] Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95) [Regression Potential] Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't affect the devices on the market currently. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1836983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775586] Re: after S3 bt icon shows disable
** Changed in: linux-meta-oem (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem in Ubuntu. https://bugs.launchpad.net/bugs/1775586 Title: after S3 bt icon shows disable Status in linux-meta-oem package in Ubuntu: Invalid Bug description: machine: WHN7-DVT2-C7 (201803-26164) Bus 001 Device 005: ID 8087:0025 Intel Corp. the steps to reproduce: 1. flash install whole system 2. install latest linux-oem and linux-firmware 3. reboot 4. press wireless key to disable wireless/bt 5. press wireless key to enable wireless/bt 6. trigger S3 by clicking right top icon 7. bluetooth get disabled after S3 resume. <= issue 8. bluetooth could be re-enabled by clicking UI. but if you install latest mainline kernel 4.17.0-rc7, this issue can not be reproduced. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-oem 4.13.0.1028.33 ProcVersionSignature: Ubuntu 4.13.0-1028.31-oem 4.13.16 Uname: Linux 4.13.0-1028-oem x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jun 7 19:11:10 2018 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2018-06-07 (0 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 SourcePackage: linux-meta-oem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem/+bug/1775586/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809219] Re: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809219 Title: Killer 802.11ac 2x2 (1550 or 1550i) [8086:2526][1a56:1550] is not supported Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: [Impact] Killer Wireless-1550 is not supported by Bionic kernel. [Fix] This card can be supported by adding its structs and IDs into table by below commit. 0a5257bc6d89 iwlwifi: add more card IDs for 9000 series [Test] Verified wifi works after applied the commit. [Regression Potential] Low. It adds its own structs and IDs to support killer cards. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1809219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834114] Re: AX88772A USB to Ethernet dongle doesn't work
** Changed in: linux (Ubuntu Eoan) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834114 Title: AX88772A USB to Ethernet dongle doesn't work Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] There are 2 asix drivers in the kernel, they are drivers/net/usb/asix and drivers/net/phy/asix. It leads to the compilation race condition that one overwrites the other asix.mod in .tmp_version directory. This affects the USB dongle if the "phy" one wins. T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 7 Spd=480 MxCh= 0 D: Ver= 2.00 Cls=ff(vend.) Sub=ff Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=0b95 ProdID=7720 Rev=00.01 S: Manufacturer=ASIX Elec. Corp. S: Product=AX88772A S: SerialNumber=000527 C: #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=250mA I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=ff Prot=00 Driver=asix [Fix] The same name asix has been introduced since v4.18-rc1 by this commit 31dd83b96641 net-next: phy: new Asix Electronics PHY driver the new commit fix this issue by renaming it a9520543b123 net: phy: rename Asix Electronics PHY driver [Test] Verified on my own ASIX USB Ethernet dongle. [Regression Potential] Low, it only rename the module name, no code change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809847] Re: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809847 Title: Ethernet[10ec:8136] doesn't work after S3 with kernel 4.15.0.43.64 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Bug description: [Impact] The Ethernet works after S3 with kernel 4.15.0-33.36, and fails with kernel 4.15.0.43.64. There is no interrupt while plug/unplug Ethernet cable after S3, so it looks like a regression after 4.15.0-33.36. [Fix] Check changelog and found there are 2 commits introduced from 4.15.0-35.38 might be suspicious * r8169 no internet after suspending (LP: #1779817) - r8169: don't use MSI-X on RTL8168g - r8169: don't use MSI-X on RTL8106e And check the upstream log and found the 2 MSI-X commits had been all reverted, since below commit claims it fixes the MSI-X interrupt issue which is already in Bionic kernel. 083874549fdf PCI: Reprogram bridge prefetch registers on resume So, I reverted the 2 MSI-X commits and found the Ethernet works again after S3. [Regression Potential] Low, the 2 disable MSI-X commits are workarounds, and now we have proper way to fix the issue, so it should be fine to revert them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1809847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1353307] Re: [Lenovo B470e] Unable to control brightness on 12.04.5
** Changed in: linux-lts-trusty (Ubuntu) Status: Confirmed => Won't Fix -- 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/1353307 Title: [Lenovo B470e] Unable to control brightness on 12.04.5 Status in HWE Next: Won't Fix Status in linux-lts-trusty package in Ubuntu: Won't Fix Bug description: CID: 201208-11587 Lenovo B470e This system was certified with 12.04.2 http://www.ubuntu.com/certification/hardware/201208-11587/ However, brightness control does not work on this system anymore. The brightness level indicator would change with hotkey events, but brightness itself does not. (This is an Intel UMA system) This issue could be found on many other Dell laptops as well ubuntu@201208-11587:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201208-11587:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: charged /proc/acpi/battery/BAT0/state:present rate:0 mW /proc/acpi/battery/BAT0/state:remaining capacity: 44460 mWh /proc/acpi/battery/BAT0/state:present voltage: 11373 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 48840 mWh /proc/acpi/battery/BAT0/info:last full capacity: 48560 mWh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 3395 mWh /proc/acpi/battery/BAT0/info:design capacity low: 1697 mWh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 1698 mWh /proc/acpi/battery/BAT0/info:capacity granularity 2: 45165 mWh /proc/acpi/battery/BAT0/info:model number:L09M6Y02 /proc/acpi/battery/BAT0/info:serial number: 601 /proc/acpi/battery/BAT0/info:battery type:LION /proc/acpi/battery/BAT0/info:OEM info:SMP /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:GLAN S4*disabled /proc/acpi/wakeup:EHC1 S3*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S3*enabled pci::00:1a.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:RP02 S4*disabled pci::00:1c.1 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*enabled pci::03:00.0 /proc/acpi/wakeup:RP05 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEG3 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:SLPB S3*enabled ubuntu@201208-11587:~$ dmesg | grep 'ACPI: Video' ubuntu@201208-11587:~$ ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.13.0-32-generic 3.13.0-32.57~precise1 [modified: boot/vmlinuz-3.13.0-32-generic] ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-32-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Wed Aug 6 03:01:29 2014 InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 (20140801) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-lts-trusty UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1353307/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1381851] Re: [Dell Latitude E5550] Brightness control does not work on this system
** Changed in: linux (Ubuntu) Status: Triaged => 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/1381851 Title: [Dell Latitude E5550] Brightness control does not work on this system Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201406-15271 Dell Latitude E5550 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201406-15271:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201406-15271:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: discharging /proc/acpi/battery/BAT0/state:present rate:772 mA /proc/acpi/battery/BAT0/state:remaining capacity: 3170 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 3540 mAh /proc/acpi/battery/BAT0/info:last full capacity: 3372 mAh /proc/acpi/battery/BAT0/info:battery technology: rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 354 mAh /proc/acpi/battery/BAT0/info:design capacity low: 107 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 35 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 35 mAh /proc/acpi/battery/BAT0/info:model number:DELL 9P4D246 /proc/acpi/battery/BAT0/info:serial number: 226 /proc/acpi/battery/BAT0/info:battery type:LiP /proc/acpi/battery/BAT0/info:OEM info:LGC-LGC3.4 /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/AC/state:state: off-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled pci::01:00.0 /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP05 S4*disabled pci::00:1c.4 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP06 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP07 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP08 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:GLAN S4*disabled pci::00:19.0 /proc/acpi/wakeup:EHC1 S0*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S0*disabled /proc/acpi/wakeup:XHC S0*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:LID0 S3*enabled /proc/acpi/wakeup:PBTN S3*enabled ubuntu@201406-15271:~$ dmesg | grep 'ACPI: Video' [ 12.986933] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201406-15271:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-37-generic 3.13.0-37.64 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1530 F pulseaudio /dev/snd/controlC1: ubuntu 1530 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 15 23:03:45 2014 HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d InstallationDate: Installed on 2014-10-09 (6 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Latitude E5550 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 1408592] Re: [Dell Vostro 5470] Unable to control brightness
** 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/1408592 Title: [Dell Vostro 5470] Unable to control brightness Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201307-14037 Vostro 5470 Brightness control does not work on this system The brightness level indicator would change with hotkey events, but the brightness itself does not. There is a simliar bug reported before, bug 1333638 for 201307-14038, another Vostro 5470, but the brightness control works on that system because it has a discrete video card. For this UMA system, it doesn't work. == WORKAROUND == Brightness would work with "acpi_osi=\"!Windows 2012\"" added to grub. Also verified on 201307-14038, this workaround won't affect its brightness control capability. Debugging information: ubuntu@201307-14037:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201307-14037:~$ grep -r . /proc/acpi /proc/acpi/battery/BAT0/alarm:alarm: unsupported /proc/acpi/battery/BAT0/state:present: yes /proc/acpi/battery/BAT0/state:capacity state: ok /proc/acpi/battery/BAT0/state:charging state: charged /proc/acpi/battery/BAT0/state:present rate:1 mA /proc/acpi/battery/BAT0/state:remaining capacity: 4412 mAh /proc/acpi/battery/BAT0/state:present voltage: 12493 mV /proc/acpi/battery/BAT0/info:present: yes /proc/acpi/battery/BAT0/info:design capacity: 4520 mAh /proc/acpi/battery/BAT0/info:last full capacity: 4412 mAh /proc/acpi/battery/BAT0/info:battery technology: non-rechargeable /proc/acpi/battery/BAT0/info:design voltage: 11100 mV /proc/acpi/battery/BAT0/info:design capacity warning: 441 mAh /proc/acpi/battery/BAT0/info:design capacity low: 0 mAh /proc/acpi/battery/BAT0/info:cycle count: 0 /proc/acpi/battery/BAT0/info:capacity granularity 1: 100 mAh /proc/acpi/battery/BAT0/info:capacity granularity 2: 0 mAh /proc/acpi/battery/BAT0/info:model number:Dell /proc/acpi/battery/BAT0/info:serial number: 716 /proc/acpi/battery/BAT0/info:battery type:LION /proc/acpi/battery/BAT0/info:OEM info:SIMPLO /proc/acpi/button/lid/LID0/state:state: open /proc/acpi/ac_adapter/ADP0/state:state: on-line /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:P0P1 S4*disabled /proc/acpi/wakeup:GLAN S4*disabled /proc/acpi/wakeup:EHC1 S4*enabled pci::00:1d.0 /proc/acpi/wakeup:EHC2 S4*disabled /proc/acpi/wakeup:XHC S4*enabled pci::00:14.0 /proc/acpi/wakeup:HDEF S4*disabled pci::00:1b.0 /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP02 S4*disabled pci::00:1c.1 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP03 S4*disabled pci::00:1c.2 /proc/acpi/wakeup:PXSX S4*enabled pci::07:00.0 /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*disabled pci::08:00.0 /proc/acpi/wakeup:PEG0 S4*disabled /proc/acpi/wakeup:PEGP S4*disabled /proc/acpi/wakeup:PEG1 S4*disabled /proc/acpi/wakeup:PEG2 S4*disabled /proc/acpi/wakeup:LID0 S3*enabled ubuntu@201307-14037:~$ dmesg | grep 'ACPI: Video' [ 12.591778] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201307-14037:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1458 F pulseaudio /dev/snd/controlC1: ubuntu 1458 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Thu Jan 8 04:06:09 2015 HibernationDevice: RESUME=UUID=2bba8b6d-4818-4d59-8187-613dffbe1088 InstallationDate: Installed on 2014-12-29 (9 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro 5470 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=b23b072b-a0ef-48de-bc97-3d66100bbc82 ro quiet splash "acpi_osi=!Windows 2012"
[Kernel-packages] [Bug 1609606] Re: Mic mute hotkey does not work on usb keyboard [03f0:2f4a]
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609606 Title: Mic mute hotkey does not work on usb keyboard [03f0:2f4a] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Press the MIC mute function key on the USB keyboard [03f0:2f4a] doesn't emit any keyevent nor acpi event. T: Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 23 Spd=1.5 MxCh= 0 D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=03f0 ProdID=2f4a Rev=00.10 S: Manufacturer=Chicony S: Product=HP Business Slim Keyboard C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=usbhid I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=usbhid To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1609606/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1405767] Re: [Dell Vostro 3010] USB3 controller [1022:7814] died after resume from S3
** Changed in: linux (Ubuntu) Status: Triaged => 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/1405767 Title: [Dell Vostro 3010] USB3 controller [1022:7814] died after resume from S3 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201401-14509 Dell Vostro 3010 The USB3 hub on this system died after resume from suspend. Error messages could be found in the dmesg output: $ dmesg | grep xhci [ 222.014935] xhci_hcd :00:10.0: System wakeup enabled by ACPI [ 222.062294] xhci_hcd :00:10.0: Refused to change power state, currently in D3 [ 222.122058] xhci_hcd :00:10.0: System wakeup disabled by ACPI [ 222.134306] xhci_hcd :00:10.0: Refused to change power state, currently in D3 [ 222.322547] xhci_hcd :00:10.0: Refused to change power state, currently in D3 [ 222.322562] xhci_hcd :00:10.0: WARN: xHC restore state timeout [ 222.322566] xhci_hcd :00:10.0: PCI post-resume error -110! [ 222.322568] xhci_hcd :00:10.0: HC died; cleaning up [ 222.322573] xhci_hcd :00:10.0: HC died; cleaning up [ 228.984071] xhci_hcd :00:10.0: Timeout while waiting for configure endpoint command [ 228.984094] xhci_hcd :00:10.0: Stopped the command ring failed, maybe the host is dead [ 228.984110] xhci_hcd :00:10.0: Host not halted after 16000 microseconds. [ 228.984117] xhci_hcd :00:10.0: Abort command ring failed [ 228.984125] xhci_hcd :00:10.0: HC died; cleaning up $ lspci -nn | grep 00\:10 00:10.0 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller [1022:7814] (rev ff) Reboot the system could bring it back. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-43-generic 3.13.0-43.72 ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11 Uname: Linux 3.13.0-43-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1635 F pulseaudio CurrentDesktop: Unity Date: Fri Dec 26 06:04:39 2014 HibernationDevice: RESUME=UUID=db110b28-de8a-49b3-9f4d-3947db24f8d9 InstallationDate: Installed on 2014-12-26 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro 20 Model 3010 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-43-generic root=UUID=59ed32bd-8858-473a-b407-1f41ce0412fb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-43-generic N/A linux-backports-modules-3.13.0-43-generic N/A linux-firmware 1.127.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA00:bd01/22/2014:svnDellInc.:pnVostro20Model3010:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: Vostro 20 Model 3010 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1405767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1393686] Re: [Dell Inspiron 3442] Wireless key does not work on 14.04.1
** 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/1393686 Title: [Dell Inspiron 3442] Wireless key does not work on 14.04.1 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201402-14675 Dell Inspiron 3442 The wireless key does not work on this system, which is simliar to bug 1339456, due to the BIOS doesn't handle Win8 OSI. WORKAROUND: it work with the acpi_osi=\"!Windows 2012\" parameter added to grub ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1511 F pulseaudio /dev/snd/controlC1: ubuntu 1511 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Tue Nov 18 01:57:44 2014 HibernationDevice: RESUME=UUID=6a176ac4-beb1-4a03-99e6-fd6b53e8b230 InstallationDate: Installed on 2014-11-18 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. Inspiron 3442 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=e3da6884-4737-4003-b0ae-efab9daa5157 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A00 dmi.board.name: 00G010 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA00:bd02/24/2014:svnDellInc.:pnInspiron3442:pvrNotSpecified:rvnDellInc.:rn00G010:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3442 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1393686/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1395618] Re: [Dell Vostro 20 3015] Unable to control brightness with 14.04.1
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1395618 Title: [Dell Vostro 20 3015] Unable to control brightness with 14.04.1 Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Confirmed Status in linux source package in Utopic: Fix Released Bug description: CID: 201402-14810 Dell Vostro 20 3015 Brightness control does not work on this AIO system The brightness level indicator would change with hotkey events, but the brightness itself does not. Debugging information: ubuntu@201402-14810:~$ ls /sys/class/backlight acpi_video0 intel_backlight ubuntu@201402-14810:~$ grep -r . /proc/acpi /proc/acpi/wakeup:Device S-state Status Sysfs node /proc/acpi/wakeup:XHC1 S4*enabled pci::00:14.0 /proc/acpi/wakeup:RP01 S4*disabled pci::00:1c.0 /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP02 S4*disabled /proc/acpi/wakeup:PXSX S4*disabled /proc/acpi/wakeup:RP03 S4*disabled pci::00:1c.2 /proc/acpi/wakeup:PXSX S4*disabled pci::02:00.0 /proc/acpi/wakeup:RP04 S4*disabled pci::00:1c.3 /proc/acpi/wakeup:PXSX S4*enabled pci::03:00.0 /proc/acpi/wakeup:PWRB S4*enabled ubuntu@201402-14810:~$ dmesg | grep 'ACPI: Video' [ 15.958744] ACPI: Video Device [PEGP] (multi-head: yes rom: yes post: no) [ 15.960535] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) ubuntu@201402-14810:~$ ubuntu@201402-14810:~$ sudo showkey -k kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... keycode 28 release keycode 225 press keycode 225 release keycode 225 press keycode 225 release keycode 224 press keycode 224 release keycode 224 press keycode 224 release ^Ccaught signal 2, cleaning up... ubuntu@201402-14810:~$ Keycode and scan code with brightness up / down key ubuntu@201402-14810:~$ sudo showkey -s kb mode was ?UNKNOWN? [ if you are trying this under X, it might not work since the X server is also reading /dev/console ] press any key (program terminates 10s after last keypress)... 0x9c 0xe0 0x54 0xe0 0xd4 0xe0 0x54 0xe0 0xd4 0xe0 0x4c 0xe0 0xcc 0xe0 0x4c 0xe0 0xcc 0x1d ^Ccaught signal 2, cleaning up... ubuntu@201402-14810:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-39-generic 3.13.0-39.66 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1597 F pulseaudio CRDA: country TW: (2402 - 2472 @ 40), (3, 27) (5270 - 5330 @ 40), (3, 17), DFS (5735 - 5815 @ 40), (3, 30) CurrentDesktop: Unity Date: Mon Nov 24 02:41:31 2014 HibernationDevice: RESUME=UUID=944a1d0f-5400-4d20-a9f3-8b43d4ae02a1 InstallationDate: Installed on 2014-11-19 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Vostro 20 3015 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=c241f0c7-88e6-435b-901f-35b094219306 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-39-generic N/A linux-backports-modules-3.13.0-39-generic N/A linux-firmware 1.127.8 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux StagingDrivers: rts5139 UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: X13 dmi.board.name: Type2 - Board Product Name1 dmi.board.vendor: Dell Inc. dmi.board.version: Type2 - Board Version dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: X13 dmi.modalias: dmi:bvnDellInc.:bvrX13:bd02/18/2014:svnDellInc.:pnVostro203015:pvr:rvnDellInc.:rnType2-BoardProductName1:rvrType2-BoardVersion:cvnDellInc.:ct13:cvrX13: dmi.product.name: Vostro 20 3015 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1395618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1616318] Re: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616318 Title: System hang when plug/pull USB 3.1 key via thunderbolt port over 5 times Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter to Dekstop. 3) Insert the USB 3.1 key in the thunderbolt port. 4) Remove the USB 3.1 key from the thunderbolt port. 5) Insert the USB 3.1 key in the thunderbolt port. Expected results: Can detect the USB 3.1 key and system will not hang. Actual results: System Hang To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1616318/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838142] Re: Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting
Please also try a newer kernel like: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.2.4/ and tell us if installing that solves the bug. ** 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/1838142 Title: Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting Status in linux package in Ubuntu: Incomplete Bug description: I was using my mouse and it was 100 functional, then when I took the usb wireless divice out, it stoppped working. I have a sculpt confort desktop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 10:56:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:382c] InstallationDate: Installed on 2019-02-03 (173 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=1d781a49-22b9-4932-8b1b-dfba2bf00d1f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN21WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN21WW(V2.02):bd10/24/2016:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UD dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1634380] Re: BT still shows off after resume by wireless hotkey
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1634380 Title: BT still shows off after resume by wireless hotkey Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Summary: BT still shows off after resume by wireless hotkey Steps: 1) Install ubuntu 16.04 2) Press the wireless hotkey 3) Check the WiFi/BT status 4) Press the wireless hotkey again 5) Check the WiFi/BT status Expected results: Can turn on/off the WiFi/BT by wireless hotkey Actual results: Can turn off the WiFi/BT by wireless hotkey, but the BT is still off after press the hotkey again. WiFi didn't has this issue. Can't turn on the BT in the system setting, need reboot the system. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1634380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835150] Re: Sometimes touchpad detected as mouse(i2c designware fails to get adapter number)
** Changed in: linux (Ubuntu Bionic) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835150 Title: Sometimes touchpad detected as mouse(i2c designware fails to get adapter number) Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Invalid Bug description: [Impact] I2C designware fails to get its adapter number, and this may lead to fail to access touchpad through I2C bus. [ 6.476367] WARNING: CPU: 9 PID: 567 at /build/linux-oem-osp1-bkWHJC/linux-oem-osp1-5.0.0/drivers/i2c/i2c-core-base.c:1322 i2c_add_numbered_adapter+0x81/0x90 [Fix] The 2 commits from v5.1-rc1 fix this issue. cd86d1403bb4 i2c: i2c-designware-platdrv: Always use a dynamic adapter number 77f3381a83c2 i2c: i2c-designware-platdrv: Cleanup setting of the adapter number [Test] Verified on Dell machine which had this issue. [Regression Potential] Low, the 2 commits make it always use dynamic adapter-numbers which does not make any difference in most cases and in the one case where it does make a difference the behavior change is desirable because the old behavior caused an oops. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835150/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838142] Re: mouse not working
Your Xorg log is showing that 'Microsoft Microsoft® 2.4GHz Transceiver v8.0' is being added and removed a lot. If that's not true and you are leaving the USB receiver plugged in, then this will be either a kernel bug or a hardware problem. Please try using a regular wired USB mouse and tell us if that has any similar issues. ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Summary changed: - mouse not working + Microsoft Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Summary changed: - Microsoft Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting + Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838142 Title: Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting Status in linux package in Ubuntu: Incomplete Bug description: I was using my mouse and it was 100 functional, then when I took the usb wireless divice out, it stoppped working. I have a sculpt confort desktop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 10:56:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:382c] InstallationDate: Installed on 2019-02-03 (173 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=1d781a49-22b9-4932-8b1b-dfba2bf00d1f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN21WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN21WW(V2.02):bd10/24/2016:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UD dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630857] Re: Dell Precision Trackpoint not working after suspend
** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630857 Title: Dell Precision Trackpoint not working after suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Steps: 1) Install Ubuntu 16.04 2) Enter Desktop. 3) Suspend system. 4) Using the trackpoint. 5) Click the left button with DualPoint stick. 6) Click the right button with DualPoint stick. 7) Click the middle button with DualPoint stick. 8) Double-click the left button with DualPoint stick. Expected results: Trackpoint and DualPoint stick can work after suspend. Actual results: Trackpoing and DualPoint stick not working after suspend. Manufacturer: Dell Inc. ProductName: Precision 7500 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1630857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1695216] Re: Can't disable USB port from BIOS
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1695216 Title: Can't disable USB port from BIOS Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: From BIOS, there is front USB port disable function. It is supposed the option in BIOS can disable USB port and due to AMD chip limitation, it need OS’s cowork. Otherwise the USB disable function will be invalid when resuming from S3 or reinsert USB device. === SRU Justification === [Impact] In BIOS, there is front USB port disable function. It is supposed the option in BIOS can disable USB port, but due to AMD chip's limitation, it needs OS’s cowork. Otherwise the USB disable function will be invalid when resuming from S3 or reinsert USB device. [Fix] After checking with Windows, we found there are 2 bits that are default on in Ubuntu is disabled in Windows. They are #define PORT_WKOC_E (1<<22) /* wake on overcurrent (enable) */ #define PORT_WKCONN_E (1<<20) /* wake on connect (enable) */ So, this patch introduce a quirk to not setup the wakeup bits only for AMD USB chips. [Test Case] Verified on the machine has this issue, and confirm this patch works. [Regression Potential] This patch only affects the listed USB ID, and we don't cert this kind of wakeup method, so should have no regression concerns. Wake up from USB device is still working, and the patch behavior is confirmed by the project lead, Tsai, Nicholas, from AMD in the discussion thread[1]. [Misc] This patch is accepted by the maintainer but still not shown up in any git tree yet. The discussion thread can be found here[1]. To fit the project schedule, we need this commit in our kernel as soon as possbile, and can't wait to next SRU release cycle. 1. https://www.spinics.net/lists/linux-usb/msg157789.html To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1695216/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838142] [NEW] Microsoft Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting
You have been subscribed to a public bug: I was using my mouse and it was 100 functional, then when I took the usb wireless divice out, it stoppped working. I have a sculpt confort desktop ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permiso denegado: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 10:56:09 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:382c] InstallationDate: Installed on 2019-02-03 (173 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=1d781a49-22b9-4932-8b1b-dfba2bf00d1f ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/24/2016 dmi.bios.vendor: LENOVO dmi.bios.version: 1TCN21WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lenovo ideapad 1 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15ISK dmi.modalias: dmi:bvnLENOVO:bvr1TCN21WW(V2.02):bd10/24/2016:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UD dmi.product.version: Lenovo ideapad 110-15ISK dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- Microsoft Microsoft® 2.4GHz Transceiver v8.0 repeatedly connecting and disconnecting https://bugs.launchpad.net/bugs/1838142 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1335026] Re: [Dell OptiPlex 3011] Sometimes system won't be able to run suspend stress test
** 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/1335026 Title: [Dell OptiPlex 3011] Sometimes system won't be able to run suspend stress test Status in HWE Next: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: CID: 201302-12682 Dell OptiPlex 3011 Sometimes this system cannot be suspended for multiple times with sudo fwts -P s3 --s3-multiple=5 --s3-device-check --s3-device-check-delay 45 (The first suspend cycle probably would success) Error could be found in the log file: S3 cycle 1 of 5 pm-suspend returned 128 after 20 seconds. FAILED [MEDIUM] ShortSuspend: Test 1, Unexpected: S3 slept for 20 seconds, less than the expected 30 seconds. FAILED [HIGH] PMActionPowerStateS3: Test 1, pm-action tried to put the machine in the requested power state but failed. When this happened, even suspend with the system menu would fail. I do have it successfully suspend for 5 times once. Steps: 1. Install 14.04, boot to desktop 2. Try to suspend this system for multiple times with the command above 3. Reboot and re-test it. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-24-generic 3.13.0-24.46 [modified: boot/vmlinuz-3.13.0-24-generic] ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1339 F pulseaudio CurrentDesktop: Unity Date: Tue Jun 24 02:25:16 2014 HibernationDevice: RESUME=UUID=1877e238-0ac4-41ae-8f13-91e1e3636b73 InstallationDate: Installed on 2014-06-19 (4 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. OptiPlex 3011 AIO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=d6534767-b55e-4ec0-b18e-cb1151963470 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-24-generic N/A linux-backports-modules-3.13.0-24-generic N/A linux-firmware 1.127 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: X19 dmi.board.vendor: Dell Inc. dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrX19:bd02/22/2013:svnDellInc.:pnOptiPlex3011AIO:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct13:cvr: dmi.product.name: OptiPlex 3011 AIO dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1335026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Thanks. The common factor still seems to be: Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: Unable to get Headset Voice gateway SDP record: Device or resource busy Jul 29 12:20:13 V-M-Ubuntu-Experimental bluetoothd[817]: connect error: Device or resource busy (16) which is the same error you had in bug 1838180. But obviously this is a different bug since it's happening with kernel 5.2. I think this bug is basically bluetoothd getting errors from the kernel and unable to comply with the user's requests. -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Hmm, you reported this bug from a virtual machine which doesn't seem to have any Bluetooth hardware, so actually I would expect the switch to not work. Please submit a new bug from a real machine if that's where you are seeing the problem. ** Changed in: bluez (Ubuntu) Status: Incomplete => Invalid -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ...
As far as I know, for the moment at least, this bug affects Xorg but might not affect Wayland Gnome sessions. Can anyone confirm that? ** Summary changed: - kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B + kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... ** Tags added: disco ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (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/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1806242] Re: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ...
>From memory, only Xorg's modesetting_drv uses atomic modesetting, but I don't think mutter/Gnome's Wayland backend does. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806242 Title: kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Incomplete Bug description: I have this error and arbitrary freezes on the system My System: Hardware: Processor: Intel Core i7-8750H @ 4.10GHz (12 Cores), Motherboard: Dell 0M2MWX, Chipset: Intel Device a36f, Memory: 16384MB, Disk: 1000GB Seagate ST1000LM035-1RK1 + 256GB TOSHIBA KSG60ZMV, Graphics: Intel Device 3e9b, Audio: Realtek ALC3246, Monitor: DELL P2016, Network: Qualcomm Atheros Killer E2400 Gigabit + Intel Device a370 Software: OS: Ubuntu 18.04, Kernel: 4.15.0-39-generic (x86_64), Desktop: Xfce 4.12, Display Driver: modesetting 1.19.6, OpenGL: 4.5 Mesa 18.0.5, File-System: ext4, Screen Resolution: 1920x1980 dmesg output: Dec 2 16:00:22 G5 kernel: [ 2027.018608] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=15726 end=15727) time 1024 us, min 894, max 899, scanline start 845, end 903 Dec 2 16:08:50 G5 kernel: [ 2534.448063] ACPI Error: [LCD_] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364) Dec 2 16:08:50 G5 kernel: [ 2534.448071] No Local Variables are initialized for Method [BRT6] Dec 2 16:08:50 G5 kernel: [ 2534.448072] Initialized Arguments for Method [BRT6]: (2 arguments defined for method invocation) Dec 2 16:08:50 G5 kernel: [ 2534.448073] Arg0: a83faa08 Integer 0001 Dec 2 16:08:50 G5 kernel: [ 2534.448076] Arg1: 35246c42 Integer Dec 2 16:08:50 G5 kernel: [ 2534.448079] ACPI Error: Method parse/execution failed \_SB.PCI0.PEG0.PEGP.BRT6, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448145] ACPI Error: Method parse/execution failed \EV5, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448206] ACPI Error: Method parse/execution failed \SMEE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448268] ACPI Error: Method parse/execution failed \SMIE, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448332] ACPI Error: Method parse/execution failed \NEVT, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:08:50 G5 kernel: [ 2534.448394] ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.ECDV._Q66, AE_NOT_FOUND (20170831/psparse-550) Dec 2 16:14:41 G5 kernel: [ 2885.660715] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:14:45 G5 kernel: [ 2889.787584] acpi INT3400:00: Unsupported event [0x86] Dec 2 16:20:32 G5 kernel: [ 3237.026638] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe B (start=88190 end=88191) time 1687 us, min 894, max 899, scanline start 864, end 14 Dec 2 16:22:20 G5 kernel: [ 3344.842212] wlp0s20f3: AP 90:ef:68:2c:31:9b changed bandwidth, new config is 2432 MHz, width 2 (2422/0 MHz) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: instantcrush 1622 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-28 (4 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. G5 5587 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=0017db25-edad-4311-bca6-171f2624432e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.2 Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/01/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0M2MWX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd11/01/2018:svnDellInc.:pnG55587:pvr:rvnDellInc.:rn0M2MWX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G5 5587 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806242/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1813423] Re: System freezing or flickering with i915 error "*ERROR* Atomic update failure on pipe A"
*** This bug is a duplicate of bug 1806242 *** https://bugs.launchpad.net/bugs/1806242 ** Summary changed: - Frequent system freezing with i915 error "*ERROR* Atomic update failure on pipe A" + System freezing or flickering with i915 error "*ERROR* Atomic update failure on pipe A" ** Summary changed: - System freezing or flickering with i915 error "*ERROR* Atomic update failure on pipe A" + System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ** Tags added: bionic ** This bug has been marked a duplicate of bug 1806242 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1813423 Title: System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: My system keeps freezing on a brand new install of Kubuntu 18.10, always with the kern.log error "[drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=4120234 end=4120235) time 486 us, min 763, max 767, scanline start 760, end 783" I think it's probably a duplicate of these bugs which were closed unresolved: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1660619 (closed as it was on an older version of Ubuntu) https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1671975 (closed because it was a duplicate of the first bug) It happens far more frequently if I have desktop effects turned on, and far less frequently when using a live USB key (at always happens eventually though. Usually once every few hours.) Please advise how I can help triage / test. My system is a new install now, so I'm perfectly willing to modify / reinstall to help testing (I've reinstalled 5 times to test things, but never managed to find a solution) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sat Jan 26 14:19:52 2019 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227a] InstallationDate: Installed on 2019-01-18 (8 days ago) InstallationMedia: Kubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: Hewlett-Packard HP Pavilion 14 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2c4bf3d1-1ff2-4345-95c0-c68d0e073df9 ro nogpumanager modprobe.blacklist=nouveau,nvidiafb,nvidia-modeset,nvidia-uvm,nvidia intel_iommu=igfx_off i915.semaphores=1 i915.enable_fbc=0 i915.modeset=1 i915.enable_rc=7 i915.enable_dc=2 i915.enable_ppgtt=3 i915.enable_guc_loading=1 i915.lvds_channel_mode=2 i915.lvds_use_ssc=1 quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.42 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227A dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.42:bd03/18/2015:svnHewlett-Packard:pnHPPavilion14NotebookPC:pvr096C110800405F1620180:rvnHewlett-Packard:rn227A:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 14 Notebook PC dmi.product.sku: J9L01UA#ABL dmi.product.version: 096C110800405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1658632] Re: [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe ...
** Summary changed: - [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe C + [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe ... ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Fix Released ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1658632 Title: [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe ... Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: Dell XPS 15, Ubuntu 16.04 (Ubuntu 4.4.0-59.80-generic 4.4.35), freshly updated. Running BTRFS and nouveau. The UI crashes, and put me back to the login screen after 30 seconds. This happens when I start softwares based on webkit (stremio, opera, chrome, etc). But generally only the first time. After login back and starting the program again, it works without crashing. The full dmesg error message is: [ 113.711453] [drm:intel_pipe_update_end [i915_bpo]] *ERROR* Atomic update failure on pipe C (start=5158 end=5159) time 130 us, min 1073, max 1079, scanline start 1071, end 1080 Repeated several times. I also get a: [ 762.958586] nouveau :01:00.0: priv: HUB0: 10ecc0 (1d40822c) And a: [13925.500344] brcmf_cfg80211_reg_notifier: not a ISO3166 code but don't know if it's relevant. --- ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 2730 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=4b156e2d-c1e9-435f-9a56-825b0c577742 InstallationDate: Installed on 2016-09-20 (206 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. XPS 15 9550 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-46-generic root=UUID=1e6d33f9-ac0e-48bb-b69e-e48ae79db74c ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-46.49~16.04.1-generic 4.8.17 RelatedPackageVersions: linux-restricted-modules-4.8.0-46-generic N/A linux-backports-modules-4.8.0-46-generic N/A linux-firmware1.157.8 Tags: xenial xenial Uname: Linux 4.8.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo www-data _MarkForUpload: True dmi.bios.date: 02/17/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.21 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.21:bd02/17/2017:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1658632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820997] Re: Ubuntu is freezing with two video monitors
*** This bug is a duplicate of bug 1806242 *** https://bugs.launchpad.net/bugs/1806242 ** This bug is no longer a duplicate of bug 1813423 System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ** This bug has been marked a duplicate of bug 1806242 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820997 Title: Ubuntu is freezing with two video monitors Status in linux package in Ubuntu: New Bug description: Hello, As you can see in the attached report, I have a Dell, Inspiron notebook with Nvidia 1050 etc ... I connected to this notebook (through the HDMI port) a monitor LG 23EA53 ... Initially the Nouveau driver never worked properly with this video card. It is a huge pain to do a Ubuntu installation on this notebook because it is very expensive after installation to get the notebook to start in a text mode session with internet... and then manually install the Nvidia driver ... But even with those difficulties (that simply prevent a lay user from having Ubuntu on their Dell notebook with Nvidia 1050) I was able to give outline solutions for this. I always try to use the development version of Ubuntu with the expectation of being able to help with the tests. So I'm currently using a "Disco" completely updated... At first (up to 3 months ago) I was working on a Ubuntu session on Xorg because the Wayland session did not allow me to use another video monitor connected to my notebook. However, from that time, there was a reversal, the Xorg session stopped working with the HDMI monitor and Xwayland started detecting and setting normally this monitor via HDMI. Well, that's where the problem is! The video monitor is detected, gnome-shell appears and runs normally on both monitors, but after a few moments of use, the GUI simply freezes! It always freezes on a point where the mouse cursor is in background processing mode. In this situation Linux gets completely frozen, not even the CapsLock, or Ctrl+Shift+F"n" keys work. The only way out is to completely turn off the notebook using the power button, then turn the notebook on again with the HDMI monitor disconnected to prevent further freezing. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xwayland 2:1.20.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] É um diretório: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.43 Tue Feb 19 01:12:11 CST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1) ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 20 08:43:48 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.43, 5.0.0-8-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:0798] NVIDIA Corporation GP107M [GeForce GTX 1050 Ti Mobile] [10de:1c8c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:0798] InstallationDate: Installed on 2019-01-30 (48 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190119) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0cf3:e007 Qualcomm Atheros Communications Bus 001 Device 002: ID 413c:301d Dell Computer Corp. Bus 001 Device 004: ID 1bcf:2c01 Sunplus Innovation Technology Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15 7000 Gaming ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=11a759f5-c884-4c9a-87f0-22554753d054 ro quiet splash vt.handoff=1 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0P84C9 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd08/15/2018:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15 7000 Gaming dmi.product.sku: 0798 dmi.sys.vendor: Dell Inc. nvidia-settings: ERROR: Unable to
[Kernel-packages] [Bug 1830358] Re: Screen flickering
*** This bug is a duplicate of bug 1806242 *** https://bugs.launchpad.net/bugs/1806242 Perfect, thanks. [78934.031960] [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A (start=11806 end=11807) time 173 us, min 1073, max 1079, scanline start 1069, end 1080 This looks like a pre-existing bug... ** This bug has been marked a duplicate of bug 1813423 System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ** This bug is no longer a duplicate of bug 1813423 System freezing or flickering with i915 error [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe A ** This bug has been marked a duplicate of bug 1806242 kernel: [drm:intel_pipe_update_end [i915]] *ERROR* Atomic update failure on pipe ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830358 Title: Screen flickering Status in linux package in Ubuntu: Incomplete Bug description: Using Intel Graphics HD 520 Constant flickering begins after some usage. Rebooting resolves the issue for a short while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 06:42:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2019-04-05 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764087] Re: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37)
** Changed in: lightdm (Ubuntu) Status: Confirmed => Invalid ** Changed in: xorg-server (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/1764087 Title: Wrongly boots into low graphics mode using kernel 4.13.0-38 (mostly works with 4.13.0-37) Status in X.Org X server: Won't Fix Status in lightdm package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Bug description: Description: Ubuntu 16.04.4 LTS Release: 16.04 Lenovo T410 with VGA compatible controller [0300]: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) Booting from latest kernel ThinkPad-T410 4.13.0-38-generic #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi connection insofar as it does not connect to my router. Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar 7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the time but occasionally has the same effects. I have had to submit this report after booting from 4.13.0.37 in order to submit bug. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-37-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Apr 15 10:40:31 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a] InstallationDate: Installed on 2016-09-24 (567 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: LENOVO 2519Y11 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/14/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 6IET85WW (1.45 ) dmi.board.name: 2519Y11 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T410 dmi.product.name: 2519Y11 dmi.product.version: ThinkPad T410 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Apr 15 08:52:27 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2016-09-24 (757 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Package: xorg-server PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-08-16 (66 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1764087/+subscriptions -- Mailing
[Kernel-packages] [Bug 1837609] Re: xenial/linux: 4.4.0-158.186 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:queued,meta:depwait,signed:queued + promote-to-proposed: Pending -- builds not complete in ppa meta:depwait trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837609 Title: xenial/linux: 4.4.0-158.186 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:depwait trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837609] Re: xenial/linux: 4.4.0-158.186 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa main:queued,meta:depwait,signed:queued trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837609 Title: xenial/linux: 4.4.0-158.186 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:queued,meta:depwait,signed:queued trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1704310] Re: [Bug] Crystal Ridge - null pointer de-reference in device unregister path
00289cd87676 6de5d06e657a 700cd033a82d 87a30e1f05d7 8aac0e233891
b70d31d054ee ca6bf264f6d8
v5.3-rc2
** Changed in: intel
Status: Triaged => Fix Committed
** Description changed:
Description:
If I run the following script in a loop, and then ctrl-c it, the kernel
hits a BUG in the device unregister path.
--[ns-reconf.sh]--
function pmem_btt_dax_switch() {
sector_size_list="512 520 528 4096 4104 4160 4224"
for sector_size in $sector_size_list; do
ndctl create-namespace -f -e namespace$
{1}.0 --mode=sector -l $sector_size
ndctl create-namespace -f -e namespace${1}
.0 --mode=raw
ndctl create-namespace -f -e namespace$
{1}
.0 --mode=dax
done
}
for i in 0 1 2 3; do
pmem_btt_dax_switch $i &
done
--[ns-reconf.sh]--
while true; do ./ns-reconfig.sh 0; ./ns-reconfig.sh 1; done
I've tried three times and hit the bug every time, so it seems readily
reproducible.
Offset 0x20 is the put function pointer in struct klist. This is where
the null pointer is triggered:
static void klist_put(struct klist_node *n, bool kill)
{
struct klist *k = knode_klist;
void (*put)(struct klist_node *) = k->put; <
This is the tip of Linus' tree, commit be941bf2e6a32.
Any ideas?
-Jeff
[ 117.728323] pmem0s: detected capacity change from 0 to 34093219840
[ 117.831496] BUG: unable to handle kernel NULL pointer dereference at
0020
[ 117.867193] IP: klist_put+0x1b/0x70
[ 117.884172] PGD 0
[ 117.884172] P4D 0
[ 117.894325]
[ 117.912779] Oops: 1 SMP
[ 117.926842] Modules linked in: 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 tun bridge
stp llc ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter
intel_rapl sb_edac x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm
vfat fat irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc
aesni_intel crypto_simd nd_pmem iTCO_wdt iTCO_vendor_support glue_helper
dax_pmem hpilo device_dax lpc_ich hpwdt cryptd nd_btt pcspkr ipmi_si sg ioatdma
i2c_i801 mfd_core shpchp ipmi_devintf dca wmi ipmi_msghandler nfit
acpi_power_meter nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables xfs
sr_mod sd_mod cdrom mgag200 i2c_algo_bit drm_kms_helper syscopyarea
[ 118.247253] sysfillrect sysimgblt bnx2x fb_sys_fops ahci tg3 mdio ttm
libahci ptp drm libata i2c_core pps_core hpsa libcrc32c crc32c_intel
scsi_transport_sas dm_mirror dm_region_hash dm_log dm_mod
[ 118.326324] CPU: 45 PID: 1060 Comm: kworker/u145:2 Not tainted 4.12.0-rc2+
#28
[ 118.358984] Hardware name: HP ProLiant DL380 Gen9/ProLiant DL380 Gen9, BIOS
P89 10/05/2016
[ 118.398735] Workqueue: events_unbound async_run_entry_fn
[ 118.426362] task: 880465ea8000 task.stack: c9000683c000
[ 118.452949] RIP: 0010:klist_put+0x1b/0x70
[ 118.470906] RSP: 0018:c9000683fd70 EFLAGS: 00010246
[ 118.494545] RAX: 880cfdbe8b40 RBX: RCX:
00018022001c
[ 118.526532] RDX: 00018022001d RSI: 0001 RDI:
[ 118.558720] RBP: c9000683fd90 R08: 88106463a8e8 R09:
00018022001c
[ 118.590772] R10: 6463a701 R11: 88106463a8e8 R12:
88106935cc00
[ 118.622923] R13: 880cfdbe8b68 R14: 0001 R15:
88046f438ce8
[ 118.655122] FS: () GS:88046fac()
knlGS:
[ 118.691517] CS: 0010 DS: ES: CR0: 80050033
[ 118.716914] CR2: 0020 CR3: 01c09000 CR4:
003406e0
[ 118.749349] DR0: DR1: DR2:
[ 118.781627] DR3: DR6: fffe0ff0 DR7:
0400
[ 118.814621] Call Trace:
[ 118.825740] klist_del+0xe/0x10
[ 118.839764] device_del+0x11a/0x330
[ 118.855526] device_unregister+0x1a/0x60
[ 118.873549] nd_async_device_unregister+0x22/0x30
[ 118.895091] async_run_entry_fn+0x39/0x170
[ 118.916718] process_one_work+0x149/0x360
[ 118.937472] worker_thread+0x4d/0x3c0
[ 118.953919] kthread+0x109/0x140
[ 118.968400] ? rescuer_thread+0x380/0x380
[ 118.986373] ? kthread_park+0x60/0x60
[ 119.002425] ret_from_fork+0x2c/0x40
[ 119.018421] Code: e9 1a ff ff ff 90 66 2e 0f 1f 84 00 00 00 00 00 55 48 89
e5 41 56 41 89 f6 41 55 49 89 fd 41 54 53 48 8b 1f 48 83 e3 fe 48 89 df <4c> 8b
63 20 e8 7c f8 00 00 45 84 f6 75 31 4c 89 ef e8 af fe ff
[ 119.103298] RIP: klist_put+0x1b/0x70 RSP: c9000683fd70
[ 119.128194] CR2: 0020
[ 119.143813] --[ end trace 4fadffd9ed599da8 ]--
[ 119.169828] Kernel panic - not syncing: Fatal exception
[ 119.193524] Kernel Offset: disabled
[ 119.213732] ---[ end Kernel panic - not syncing: Fatal exception
- Target Kernel:TBD
+ Target Kernel:5.3
Target Release: 19.10
--
You received this bug notification because
[Kernel-packages] [Bug 1835349] Re: Fix devm_memremap_pages shutdown handling
1570175abd16 2374b6822551 2e3f139e8ece 50f44ee7248a 795ee30648c7 e615a191216e v5.2 ** Description changed: Description: > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA > to taking a reference to the pgmap. > 2) Another process unbinds the underlying p2pdma driver and the devm > chain starts to unwind. > 3) devm_memremap_pages_release() is called and it kills the reference > and drop's it's last reference. Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and all outstanding references dropped before we can proceed to arch_remove_memory(), and I think this problem has been there since day one because the final exit was always after devm_memremap_pages() release which means arch_remove_memory() was always racing any final put_page(). I'll take a look, it seems the arch_remove_pages() call needs to be moved out-of-line to its own context and wait for the final exit of the percpu-ref. Target Release: 19.10 - Target Kernel: 5.3 + Target Kernel: 5.2 ** Changed in: intel Status: New => 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/1835349 Title: Fix devm_memremap_pages shutdown handling Status in intel: Fix Committed Status in linux package in Ubuntu: Incomplete Bug description: Description: > 1) Some p2pdma user calls pci_alloc_p2pmem() to get some memory to DMA > to taking a reference to the pgmap. > 2) Another process unbinds the underlying p2pdma driver and the devm > chain starts to unwind. > 3) devm_memremap_pages_release() is called and it kills the reference > and drop's it's last reference. Oh! Yes, nice find. We need to wait for the percpu-ref to be dead and all outstanding references dropped before we can proceed to arch_remove_memory(), and I think this problem has been there since day one because the final exit was always after devm_memremap_pages() release which means arch_remove_memory() was always racing any final put_page(). I'll take a look, it seems the arch_remove_pages() call needs to be moved out-of-line to its own context and wait for the final exit of the percpu-ref. Target Release: 19.10 Target Kernel: 5.2 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1835349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837588] Re: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837587 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws - phase: Ready for Packaging - phase-changed: Monday, 29. July 2019 19:09 UTC + phase: Packaging + phase-changed: Tuesday, 30. July 2019 00:25 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs -- 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/1837588 Title: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837587 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Tuesday, 30. July 2019 00:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837588] Re: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker
** Summary changed: - xenial/linux-aws: -proposed tracker + xenial/linux-aws: 4.4.0-1089.100 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Sultan Alsawaf (kerneltoast) -- 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/1837588 Title: xenial/linux-aws: 4.4.0-1089.100 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837587 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Packaging phase-changed: Tuesday, 30. July 2019 00:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830358] Re: Screen flickering
Finally was able to catch the problem when it happened. Log attached. ** Attachment added: "dmesgonflicker.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830358/+attachment/5279941/+files/dmesgonflicker.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830358 Title: Screen flickering Status in linux package in Ubuntu: Incomplete Bug description: Using Intel Graphics HD 520 Constant flickering begins after some usage. Rebooting resolves the issue for a short while. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 24 06:42:19 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704] InstallationDate: Installed on 2019-04-05 (49 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5682 Realtek Semiconductor Corp. Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9350 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-47-generic root=UUID=26ae1f0c-87cf-450a-82e8-a4034f51425d ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/14/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/14/2017:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1830358/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.
** Description changed: intel_pstate not working. CPU frequency fixed at 800MHz. I've tried to modify frequency using "cpufreq-set" and also by directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*" to no success. I tried different versions of kernel, it started working on 4.17.0 but stopped working soon. These are the versions I tested. 5.2.3 - Not Working 5.1.0 - Not Working 4.19.60 - Not Working 4.18.20 - Not Working 4.17.19 - Not Working 4.17.10 - Not Working 4.17.5 - Not Working - 4.17.3 - Working + 4.17.3 - Not Working 4.17.2 - Working 4.17.1 - Working 4.17.0 - Working 4.16.18 - Not Working 4.15.0 - Not Working Please let me know if anything else is needed. thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-55-generic 4.15.0-55.60 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: srijan 2219 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: srijan 2219 F pulseaudio CurrentDesktop: KDE Date: Sat Jul 27 11:34:10 2019 InstallationDate: Installed on 2018-11-25 (243 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. - Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver - Bus 001 Device 004: ID 8087:0aaa Intel Corp. - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. + Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH315-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 i915.disable_power_well=1 nmi_watchdog=0 RelatedPackageVersions: - linux-restricted-modules-4.15.0-55-generic N/A - linux-backports-modules-4.15.0-55-generic N/A - linux-firmware 1.173.10 + linux-restricted-modules-4.15.0-55-generic N/A + linux-backports-modules-4.15.0-55-generic N/A + linux-firmware 1.173.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: - + dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_CFS dmi.board.vendor: CFL dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-51 dmi.product.version: V1.24 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838141 Title: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling. Status in linux package in Ubuntu: Confirmed Bug description: intel_pstate not working. CPU frequency fixed at 800MHz. I've tried to modify frequency using "cpufreq-set" and also by directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*" to no success. I tried different versions of kernel, it started working on 4.17.0 but stopped working soon. These are the versions I tested. 5.2.3 - Not Working 5.1.0 - Not Working 4.19.60 - Not Working 4.18.20 - Not Working 4.17.19 - Not Working 4.17.10 - Not Working 4.17.5 - Not Working 4.17.3 - Not Working 4.17.2 - Working 4.17.1 - Working 4.17.0 - Working 4.16.18 - Not Working 4.15.0 - Not Working Please let me know if anything else is needed. thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-55-generic 4.15.0-55.60 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srijan 2219 F pulseaudio CurrentDesktop: KDE Date: Sat Jul 27 11:34:10 2019 InstallationDate: Installed on 2018-11-25 (243 days ago)
[Kernel-packages] [Bug 1838350] [NEW] package linux-firmware 1.157.22 failed to install/upgrade: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted
Public bug reported: This is not a new installation -- contrary to the automatically submitted report. Running Ubuntu 16.04.6 LTS. The problem occurred doing a routine update (sudo apt-get update; sudo apt-get upgrade). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.22 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Jul 29 17:05:17 2019 Dependencies: DuplicateSignature: package:linux-firmware:1.157.22 Unpacking linux-firmware (1.157.22) over (1.157.21) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.22_all.deb (--unpack): unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-03-20 (496 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: linux-firmware Title: package linux-firmware 1.157.22 failed to install/upgrade: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- 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/1838350 Title: package linux-firmware 1.157.22 failed to install/upgrade: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: This is not a new installation -- contrary to the automatically submitted report. Running Ubuntu 16.04.6 LTS. The problem occurred doing a routine update (sudo apt-get update; sudo apt-get upgrade). ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-firmware 1.157.22 ProcVersionSignature: Ubuntu 4.15.0-45.48~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-45-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.19 Architecture: amd64 Date: Mon Jul 29 17:05:17 2019 Dependencies: DuplicateSignature: package:linux-firmware:1.157.22 Unpacking linux-firmware (1.157.22) over (1.157.21) ... dpkg: error processing archive /var/cache/apt/archives/linux-firmware_1.157.22_all.deb (--unpack): unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2018-03-20 (496 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.4ubuntu1.5 apt 1.2.32 SourcePackage: linux-firmware Title: package linux-firmware 1.157.22 failed to install/upgrade: unable to open '/lib/firmware/s5p-mfc-v6-v2.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1838350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838349] [NEW] Bionic update: upstream stable patchset 2019-07-29
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-29 Ported from the following upstream stable releases: v4.14.113, v4.19.36, v4.14.114, v4.19.37 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2019-07-29 -upstream stable patchset 2019-07-29 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.113, v4.19.36, + v4.14.114, v4.19.37 + + from git://git.kernel.org/ ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838349 Title: Bionic update: upstream stable patchset 2019-07-29 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-29 Ported from the following upstream stable releases: v4.14.113, v4.19.36, v4.14.114, v4.19.37 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838349/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed + promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:failed trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
Good point, then there can be 2 explanations: 1) dedicated vs integrated GPU 2) intel vs amd/nvidia I will try to get some AMD APU to test it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837591] Re: xenial/linux-kvm: 4.4.0-1053.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-kvm meta: linux-meta-kvm - phase: Ready for Packaging - phase-changed: Monday, 29. July 2019 19:09 UTC + phase: Packaging + phase-changed: Monday, 29. July 2019 21:30 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837591 Title: xenial/linux-kvm: 4.4.0-1053.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Monday, 29. July 2019 21:30 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837591] Re: xenial/linux-kvm: 4.4.0-1053.60 -proposed tracker
** Summary changed: - xenial/linux-kvm: -proposed tracker + xenial/linux-kvm: 4.4.0-1053.60 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837591 Title: xenial/linux-kvm: 4.4.0-1053.60 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:09 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:failed trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
well by that logic, then somebody with an amd ryzen APU (such as 3200G or whichever with the integrated Vega graphics). Would also not be affected by this bug. But the other reason would be that intel's linux igp drivers are not affected. That is a different reason as to whether the gpu is being recognized as being discrete (or perhaps egpu) or not. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:queued trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837609] Re: xenial/linux: 4.4.0-158.186 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837609 Title: xenial/linux: 4.4.0-158.186 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building + promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:building trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:queued,main:building,meta:failed,signed:building trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- Mailing list: https://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 1838276] Re: zfs-module depedency selects random kernel package to install
On Mon, Jul 29, 2019 at 11:35 AM Richard Laager wrote: > What was the expected behavior from your perspective? > > The ZFS utilities are useless without a ZFS kernel module. It seems to > me that this is working fine, and installing the ZFS utilities in this > environment doesn’t make sense. > You're right that a module is needed (and we install it). I think the apparently random selection of a kernel package which provides the zfs-modules capability is what confused me. I think we can close this, if I include the kernel package we do install in the same apt install invocation then it all makes sense. apt install linux-generic zfsutils-linux Sorry for the noise. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1838276 > > Title: > zfs-module depedency selects random kernel package to install > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1838276/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1838276 Title: zfs-module depedency selects random kernel package to install Status in zfs-linux package in Ubuntu: New Bug description: In MAAS (ephemeral environment) or LXD where no kernel package is currently installed; installing the zfsutils-linux package will pull in a kernel package from the zfs-modules dependency. 1) # lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 2) n/a 3) zfsutils-linux installed without pulling in a random kernel 4) # apt install --dry-run zfsutils-linux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-1010-oem-osp1 linux-modules-5.0.0-1010-oem-osp1 os-prober zfs-zed Suggested packages: multiboot-doc grub-emu xorriso desktop-base fdutils linux-oem-osp1-tools linux-headers-5.0.0-1010-oem-osp1 nfs-kernel-server samba-common-bin zfs-initramfs | zfs-dracut The following NEW packages will be installed: grub-common grub-gfxpayload-lists grub-pc grub-pc-bin grub2-common libzfs2linux libzpool2linux linux-image-unsigned-5.0.0-1010-oem-osp1 linux-modules-5.0.0-1010-oem-osp1 os-prober zfs-zed zfsutils-linux 0 upgraded, 12 newly installed, 0 to remove and 1 not upgraded. Inst grub-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Inst grub2-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Inst grub-pc-bin (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Inst grub-pc (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) [] Inst grub-gfxpayload-lists (0.7 Ubuntu:19.10/eoan [amd64]) Inst linux-modules-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan [amd64]) Inst linux-image-unsigned-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan [amd64]) Inst os-prober (1.74ubuntu2 Ubuntu:19.10/eoan [amd64]) Inst libzfs2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Inst libzpool2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Inst zfsutils-linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Inst zfs-zed (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Conf grub-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf grub2-common (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf grub-pc-bin (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf grub-pc (2.04-1ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf grub-gfxpayload-lists (0.7 Ubuntu:19.10/eoan [amd64]) Conf linux-modules-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan [amd64]) Conf linux-image-unsigned-5.0.0-1010-oem-osp1 (5.0.0-1010.11 Ubuntu:19.10/eoan [amd64]) Conf os-prober (1.74ubuntu2 Ubuntu:19.10/eoan [amd64]) Conf libzfs2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Conf libzpool2linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Conf zfsutils-linux (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) Conf zfs-zed (0.8.1-1ubuntu7 Ubuntu:19.10/eoan [amd64]) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1838276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837788] Re: bcache kernel warning when attaching device
Patches sent to the kernel-team mailing list: [B][PATCH] bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached https://lists.ubuntu.com/archives/kernel-team/2019-July/102653.html [D][PATCH] bcache: only set BCACHE_DEV_WB_RUNNING when cached device attached https://lists.ubuntu.com/archives/kernel-team/2019-July/102654.html ** Description changed: + [Impact] + + * Users can get a Warning or even Oops the kernel if +bcache/writeback_percent is set before attaching a +caching device to the bcache device. + + * The fix is trivial, upstream, and consists of just +checking whether the caching device is attached in +order to set flags and schedule thread (which oops). + + [Test Case] + + * See attachment 'setup-bcache-wb_percent-before-attach.sh' +used in comment #5 and #6 to reproduce the problem(s). + + * for 'Warning': + +# make-bcache -B +# make-bcache -C +# echo 11 > /sys/block//bcache/writeback_percent +# sleep 1 +# echo > /sys/block//bcache/attach + + * for 'Oops': +(steps above, but don't run last command / 'attach'). + + [Regression Potential] + + * Low. The fix is trivial, contained, and exclusive to bcache sysfs + handler. + + * The modified path has been exercised with synthetic testing (script). + + [Original Bug Description] + See attached dmesg, each time this server is rebooted it emits a concerning bcache warning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-54-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jul 24 12:28:06 2019 InstallationDate: Installed on 2013-10-04 (2119 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Supermicro X9DAi ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=8577302d-1f37-40a6-afcd-385beb26059f ro nomodeset elevator=deadline nvme_core.default_ps_max_latency_us=0 nopti noibrs noibpb RelatedPackageVersions: - linux-restricted-modules-4.15.0-54-generic N/A - linux-backports-modules-4.15.0-54-generic N/A - linux-firmware 1.173.9 + linux-restricted-modules-4.15.0-54-generic N/A + linux-backports-modules-4.15.0-54-generic N/A + linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-09 (409 days ago) dmi.bios.date: 05/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DAi dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd05/09/2015:svnSupermicro:pnX9DAi:pvr0123456789:rvnSupermicro:rnX9DAi:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DAi dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Disco) 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/1837788 Title: bcache kernel warning when attaching device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
@Daniel Here you go (newlog_2019_07_29.txt). The log covers only the time while I tried to connect to the headset (took several tries before the switch switched; there are maybe a dozen mouse actions during that time). There are many message like this: org.gnome.Shell.desktop[1585]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (k eycode 12). ** Attachment added: "newlog_2019_07_29.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279854/+files/newlog_2019_07_29.txt -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
...and here is a smaller log covering only a single attempt to slide the connection switch to the right (the switch snapped back immediately by itself) ** Attachment added: "newlog_SingleTry_2019_07_29.txt" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+attachment/5279857/+files/newlog_SingleTry_2019_07_29.txt -- 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/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Incomplete Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Escalated to Field Critical as it now happens often enough to block our
ability to test proposed product releases. We are unable to test
openstack-next at the moment because our test runs fail behind this 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/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:01 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:10 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837600 Title: xenial/linux-fips: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:10 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837600/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837602] Re: trusty/linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:02 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:10 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- 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/1837602 Title: trusty/linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:10 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837602/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837591] Re: xenial/linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:01 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:09 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1837591 Title: xenial/linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:09 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837591/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837609] Re: xenial/linux: 4.4.0-158.186 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Thursday, 25. July 2019 20:50 UTC + phase: Holding before Promote to Proposed + phase-changed: Monday, 29. July 2019 19:07 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837609 Title: xenial/linux: 4.4.0-158.186 -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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1837602 (trusty/linux-aws), bug 1837607 (trusty/linux-lts-xenial) derivatives: bug 1837585 (pc-kernel), bug 1837588 (linux-aws), bug 1837591 (linux-kvm), bug 1837594 (linux-raspi2), bug 1837598 (linux-snapdragon), bug 1837600 (linux-fips) -- swm properties -- packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 19:07 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:building,signed:building trackers: trusty/linux-aws: bug 1837602 trusty/linux-lts-xenial: bug 1837607 xenial/linux-aws: bug 1837588 xenial/linux-fips: bug 1837600 xenial/linux-kvm: bug 1837591 xenial/linux-raspi2: bug 1837594 xenial/linux-snapdragon: bug 1837598 xenial/linux/pc-kernel: bug 1837585 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837609/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837598] Re: xenial/linux-snapdragon: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837596 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:01 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:10 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1837596 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1837598 Title: xenial/linux-snapdragon: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837596 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:10 UTC reason: prepare-package: Pending -- version not specified trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1837596 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837588] Re: xenial/linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837587 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:01 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:09 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs -- 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/1837588 Title: xenial/linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837587 (aws-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:09 UTC reason: prepare-package: Pending -- version not specified trackers: xenial/linux-aws/aws-kernel: bug 1837587 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837594] Re: xenial/linux-raspi2: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837592 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Packaging - phase-changed: Tuesday, 23. July 2019 15:01 UTC + phase: Ready for Packaging + phase-changed: Monday, 29. July 2019 19:10 UTC reason: - prepare-package: Stalled -- waiting for master bug + prepare-package: Pending -- version not specified trackers: xenial/linux-raspi2/pi2-kernel: bug 1837592 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1837594 Title: xenial/linux-raspi2: -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: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1837592 (pi2-kernel) -- swm properties -- kernel-stable-master-bug: 1837609 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Packaging phase-changed: Monday, 29. July 2019 19:10 UTC reason: prepare-package: Pending -- version not specified trackers: xenial/linux-raspi2/pi2-kernel: bug 1837592 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837751] Re: Kernel panic in xen-netfront on a VPS
I don't remember exactly when it started, but I can install some old kernels this week and see if I can pinpoint it exactly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837751 Title: Kernel panic in xen-netfront on a VPS Status in linux package in Ubuntu: Confirmed Bug description: This shows up occasionally when doing downloads of moderate size. apt- get update typically triggers it, as does updating plugins on the Wordpress installation running on the VPS. Note that this affects kernel versions at least as far back as 4.15.0-51, up to 4.15.0-55. 4.15.0-32, under which this bug report was taken does not display the problem. Kernel log output below: [ 342.864309] kernel BUG at /build/linux-aAn8fZ/linux-4.15.0/drivers/net/xen-netfront.c:909! [ 342.864329] invalid opcode: [#1] SMP NOPTI [ 342.864334] Modules linked in: iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_recent xt_conntrack nf_conntrack libcrc32c iptable_filter iptable_mangle intel_rapl sb_edac crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf sch_fq_codel ip_tables x_tables autofs4 [ 342.864373] CPU: 0 PID: 1730 Comm: http Tainted: GW 4.15.0-55-generic #60-Ubuntu [ 342.864385] RIP: e030:xennet_poll+0x8dc/0xbd0 [ 342.864389] RSP: e02b:8880faa03de0 EFLAGS: 00010246 [ 342.864395] RAX: 0042 RBX: 888004914028 RCX: 8880f948f000 [ 342.864403] RDX: 00ed RSI: 0042 RDI: 4000 [ 342.864409] RBP: 8880faa03ed8 R08: 8880f1f46ac0 R09: 0001802e [ 342.864414] R10: 8880faa03d80 R11: 8880f44e4b00 R12: baec [ 342.864419] R13: baed R14: 8880f284f000 R15: 8880f3660500 [ 342.864431] FS: 7f286c0482c0() GS:8880faa0() knlGS: [ 342.864450] CS: e033 DS: ES: CR0: 80050033 [ 342.864457] CR2: 7f265fb004d0 CR3: f45cc000 CR4: 2660 [ 342.864464] Call Trace: [ 342.864472] [ 342.864485] net_rx_action+0x140/0x3a0 [ 342.864513] __do_softirq+0xe4/0x2bb [ 342.864526] ? hypervisor_callback+0x25/0x40 [ 342.864542] irq_exit+0xb8/0xc0 [ 342.864556] xen_evtchn_do_upcall+0x30/0x40 [ 342.864578] xen_do_hypervisor_callback+0x29/0x40 [ 342.864584] [ 342.864592] RIP: e033:0x7f286bb4b25c [ 342.864598] RSP: e02b:7fff734357c8 EFLAGS: 0a03 [ 342.864606] RAX: 8d312d7f RBX: 39db402a RCX: 488fd63e [ 342.864614] RDX: 7a7f0825 RSI: 9a3e307c RDI: 807b756b [ 342.864623] RBP: 5d804986 R08: 7a7fcd33 R09: 0137510b [ 342.864631] R10: 5c03dbab R11: 6d0d84dc R12: 931464fb [ 342.864636] R13: aa89b1ac R14: 7cbb254f R15: 1e81958a [ 342.864643] Code: 83 f3 ff e9 33 fd ff ff 44 89 eb 44 89 ad 40 ff ff ff 44 8b 8d 50 ff ff ff 4d 89 e6 4c 8b ad 58 ff ff ff 83 c3 01 e9 78 fe ff ff <0f> 0b 48 89 d8 45 8d 6c 24 02 4c 89 f3 49 89 c6 e9 7b fc ff ff [ 342.864702] RIP: xennet_poll+0x8dc/0xbd0 RSP: 8880faa03de0 [ 342.864718] ---[ end trace 2a48579c5f763183 ]--- [ 342.864723] Kernel panic - not syncing: Fatal exception in interrupt [ 342.864750] Kernel Offset: disabled ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-32-generic 4.15.0-32.35 ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 Uname: Linux 4.15.0-32-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 24 10:40 seq crw-rw 1 root audio 116, 33 Jul 24 10:40 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Jul 24 10:59:40 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=/dev/xvda1 ro console=hvc0 quiet splash RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-08-15 (342 days ago) --- ProblemType: Bug AlsaDevices: total 0
[Kernel-packages] [Bug 1832795] Re: updates to aufs
Thanks for the report, I will work on getting this fix into our kernels. Is there a simple way to test the fix? ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832795 Title: updates to aufs Status in linux package in Ubuntu: Confirmed Bug description: I have found and reported a critical bug in aufs (as shipped with the latest Ubuntu kernels, both on Bionic and Xenial), which potentially affects anyone running Docker on Ubuntu using aufs graph driver. The fix has been developed, tested at least by me to fix the issue, and committed into upstream aufs git repos The nature of the bug is, in case of multiple parallels aufs mounts and unmounts, the kernel can screw up krefs, and once that happens, the only remedy is to reboot it (as commands like mount/umount or cat /proc/mounts are all stuck in syscalls). I would appreciate syncing aufs with the latest upstream release from git, as it was done a few times already, or at least taking the below fix (whatever suits maintainers better). The fixed versions are the ones marked with 20190610, and from what I see they are available for all kernel versions since 4.14 (for example, 4.15 tree is here: https://github.com/sfjro/aufs4-standalone/commits/aufs4.15). For 4.4, a backport might be needed, but it should be trivial. Original bug report: https://sourceforge.net/p/aufs/mailman/message/36680389/ Fix: https://github.com/sfjro/aufs4-linux/commit/b633d7b2635b9615fe294b85257d05008e3747a3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
i have same problem ubuntu 19.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] 权限不够: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 20 17:19:29 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed virtualbox, 6.0.6, 4.18.0-17-generic, x86_64: installed virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:1127] Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] [1025:1128] MachineType: Acer Aspire VX5-591G ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=UUID=a0525f6e-8c28-4e08-9c6e-9745ee51c18a ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/07/2017 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Wish_KLS dmi.board.vendor: KBL dmi.board.version: V1.06 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.06 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.06:bd07/07/2017:svnAcer:pnAspireVX5-591G:pvrV1.06:rvnKBL:rnWish_KLS:rvrV1.06:cvnAcer:ct10:cvrV1.06: dmi.product.family: Aspire VX 15 dmi.product.name: Aspire VX5-591G dmi.product.sku: dmi.product.version: V1.06 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1825626/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836806] Re: Two crashes on raid0 error path (during a member device removal)
Verified in disco kernel 5.0.22-generic (that is available in -proposed
pocket), using the test cases described in the patches.
Thanks,
Guilherme
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836806
Title:
Two crashes on raid0 error path (during a member device removal)
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Won't Fix
Status in linux source package in Disco:
Fix Committed
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* During raid0 error path testing, by removing one member of the
array, we've noticed after kernel 4.18 we can trigger a crash
depending if there's I/O in-flight during the array removal. When
debugging the issue, a second problem was found, that could cause a
different crash.
* For the first and more relevant problem, commit cd4a4ae4683d
("block: don't use blocking queue entered for recursive bio submits")
introduced the flag BIO_QUEUE_ENTERED in order BIOs that were split do bypass
the blocking queue entering routine and use the live non-blocking version. What
happens with md/raid0 though is that their BIOs have their underlying device
changed to the physical disk (array member). If we remove this physical disk
(or if it fails), we could have one BIO that had the flag changed to
BIO_QUEUE_ENTERED and had the device changed to the removed array member
(before its removal); this bio then skips a lot of checks in
generic_make_request_checks(), triggering the following crash:
BUG: unable to handle kernel NULL pointer dereference at 0155
PGD 0 P4D 0
Oops: [#1] SMP PTI
RIP: 0010:blk_throtl_bio+0x45/0x970
[...]
Call Trace:
generic_make_request_checks+0x1bf/0x690
generic_make_request+0x64/0x3f0
raid0_make_request+0x184/0x620 [raid0]
? raid0_make_request+0x184/0x620 [raid0]
md_handle_request+0x126/0x1a0
md_make_request+0x7b/0x180
generic_make_request+0x19e/0x3f0
submit_bio+0x73/0x140
[...]
* When debugging the above issue, by rebuilding the kernel with
CONFIG_BLK_CGROUP=n we've noticed a different crash. Commit
37f9579f4c31 ("blk-mq: Avoid that submitting a bio concurrently with
device removal triggers a crash") introduced a NULL pointer
dereference in generic_make_request(), that manifests as:
BUG: unable to handle kernel NULL pointer dereference at 0078
PGD 0 P4D 0
Oops: [#1] SMP PTI
RIP: 0010:generic_make_request+0x32b/0x400
Call Trace:
submit_bio+0x73/0x140
ext4_io_submit+0x4d/0x60
ext4_writepages+0x626/0xe90
do_writepages+0x4b/0xe0
[...]
* For both the issues, we have simple patches that are present in
linux-stable but not in Linus tree.
## For issue 1 (md removal crash):
869eec894663 ("md/raid0: Do not bypass blocking queue entered for raid0 bios")
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=869eec894663
## For issue 2 (generic_make_request() NULL dereference):
c9d8d3e9d7a0 ("block: Fix a NULL pointer dereference in
generic_make_request()")
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=c9d8d3e9d7a0
The reasoning for both patches not being present in Linus tree is
explained in the commit messages, but in summary Ming Lei submitted a
major clean-up series at the same time I've submitted both patches, it
wouldn't make sense to accept my patches to soon after remove the code
paths with his clean-up. But Ming's series rely on legacy I/O path
removal, and so it's very hard to backport. Hence maintainers
suggested me to submit my small fixes to stable tree only.
[Test case]
For both cases, the test is the same, the only change being a kernel
config option. To reproduce issue 1 (md removal crash), a regular
Ubuntu kernel config is enough. For the issue 2, a kernel rebuild with
CONFIG_BLK_CGROUP=n is necessary.
Steps to reproduce:
a) Create a raid0 md array with 2 NVMe devices as members, and mount it with
an ext4 filesystem.
b) Run the following oneliner (supposing the raid0 is mounted in /mnt):
(dd of=/mnt/tmp if=/dev/zero bs=1M count=999 &); sleep 0.3;\
echo 1 > /sys/block/nvme1n1/device/device/remove
(whereas nvme1n1 is the 2nd array member)
[Regression potential]
The fixes are self-contained and small, both validated by a great
number of subsystem maintainers (including block, raid and stable).
Commit c9d8d3e9d7a0 was also validated by the author of the offender
patch it fixes, and has no functional change. Commit 869eec894663 has
only raid0 driver as scope, and fall-backs raid0 to a previous
behavior before the introduction of BIO_QUEUE_ENTERED flag (which
indeed increases
[Kernel-packages] [Bug 1837788] Re: bcache kernel warning when attaching device
Tested with disco-proposed + patch (problem does not happen) --- # uname -rv 5.0.0-22-generic #23+test20190725b1 SMP Mon Jul 29 14:43:55 -03 2019 # ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1 [ 69.567775] bcache: register_bdev() registered backing device loop0/null 2>&1 [ 69.577141] bcache: run_cache_set() invalidating existing data [ 69.591172] bcache: register_cache() registered cache device loop1 [ 69.591517] bcache: register_bcache() error /dev/loop0: device already registered (emitting change event) [ 73.570620] bcache: bch_cached_dev_attach() Caching loop0 as bcache0 on set 0ed05289-ed85-40da-bcf4-3991f2e18e03 # (no warning message) # reboot # # comment last line in script. # ./setup-bcache-wb_percent-before-attach.sh >/dev/null 2>&1 # [ 40.045968] bcache: register_bdev() registered backing device loop0ev/null 2>& [ 40.050914] bcache: run_cache_set() invalidating existing data [ 40.060793] bcache: register_cache() registered cache device loop1 [ 40.068735] bcache: register_bcache() error /dev/loop1: device already registered (wait a few seconds) (ok no oops anymore) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837788 Title: bcache kernel warning when attaching device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Invalid Bug description: See attached dmesg, each time this server is rebooted it emits a concerning bcache warning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-54-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jul 24 12:28:06 2019 InstallationDate: Installed on 2013-10-04 (2119 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Supermicro X9DAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=8577302d-1f37-40a6-afcd-385beb26059f ro nomodeset elevator=deadline nvme_core.default_ps_max_latency_us=0 nopti noibrs noibpb RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-09 (409 days ago) dmi.bios.date: 05/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DAi dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd05/09/2015:svnSupermicro:pnX9DAi:pvr0123456789:rvnSupermicro:rnX9DAi:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DAi dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837788] Re: bcache kernel warning when attaching device
Attaching test-case script. ** Attachment added: "setup-bcache-wb_percent-before-attach.sh" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837788/+attachment/5279850/+files/setup-bcache-wb_percent-before-attach.sh -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837788 Title: bcache kernel warning when attaching device Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Confirmed Status in linux source package in Eoan: Invalid Bug description: See attached dmesg, each time this server is rebooted it emits a concerning bcache warning. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-54-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D3c', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Wed Jul 24 12:28:06 2019 InstallationDate: Installed on 2013-10-04 (2119 days ago) InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Beta amd64 (20130925.1) MachineType: Supermicro X9DAi ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=8577302d-1f37-40a6-afcd-385beb26059f ro nomodeset elevator=deadline nvme_core.default_ps_max_latency_us=0 nopti noibrs noibpb RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.173.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-06-09 (409 days ago) dmi.bios.date: 05/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X9DAi dmi.board.vendor: Supermicro dmi.board.version: 0123456789 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.2:bd05/09/2015:svnSupermicro:pnX9DAi:pvr0123456789:rvnSupermicro:rnX9DAi:rvr0123456789:cvnSupermicro:ct3:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: X9DAi dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
I just tried Ubuntu Studio 19.10 which uses kernel 5.2.0-8-lowlatency, seems like the issue doesn't happen there. Can you confirm? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787857 Title: USB mouse cursor lags after random time of correct behaviour Status in linux package in Ubuntu: Confirmed Status in rtirq package in Ubuntu: Invalid Bug description: I installed Ubuntu Studio 18.04.1 LTS. After the first apt-get update I noticed the following behaviour: after havig logged in, my USB mouse works normally for about ten seconds, then the cursor starts lagging a lot which makes the mouse pretty much unusable. The last dmesg always contain lines these: (more in attached file) [<9e659b0c>] irq_default_primary_handler threaded [] usb_hcd_irq [<9e659b0c>] irq_default_primary_handler threaded [ ] _rtl_pci_interrupt [rtl_pci] Disabling IRQ #18 Out of frustration & curiosity I disabled most autostart apps (Settings > Session ... > Autostart) and re-enabled them after rebooting. Since then I rarely encounter the lagging cursor. If I open Settings > Mouse & Touchpad and toggle any option on/off the cursor starts lagging. How can make the cursor work reliably? Some comment in dmesg mentions "irqpoll" boot option Ubuntu Studio 18.04.1 4.15.0-20-lowlatency #21-Ubuntu SMP PREEMPT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1838086 (azure-kernel) -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1837567 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Monday, 29. July 2019 15:51 UTC + phase: Ready for Promote to Proposed + phase-changed: Monday, 29. July 2019 18:16 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:building + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-azure/azure-kernel: bug 1838086 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1838087 Title: bionic/linux-azure: 5.0.0-1013.13~18.04.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: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1838086 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837567 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Monday, 29. July 2019 18:16 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-azure/azure-kernel: bug 1838086 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838324] [NEW] 4.15.0-55 Kernel Breaks Wifi
Public bug reported: Network controller: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n Thinkpad T430U Wifi was not operational using kernel 4.15.0-55: no list of available networks and rfkill output indicated there were no hard or soft blocks. Reverted back to 4.10.0-38 to restore functionality. ** 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/1838324 Title: 4.15.0-55 Kernel Breaks Wifi Status in linux package in Ubuntu: New Bug description: Network controller: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n Thinkpad T430U Wifi was not operational using kernel 4.15.0-55: no list of available networks and rfkill output indicated there were no hard or soft blocks. Reverted back to 4.10.0-38 to restore functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835279] Re: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open
** Changed in: linux (Ubuntu) Assignee: Connor Kuehl (connork) => (unassigned) ** Changed in: linux (Ubuntu) Importance: Medium => Undecided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835279 Title: 4.15.0-54.58-generic 4.15.18: oops/BUG on LUKS open Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: This is Linux version 4.15.0-54-generic (buildd@lgw01-amd64-014) (gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)) #58-Ubuntu SMP Mon Jun 24 10:55:24 UTC 2019 (Ubuntu 4.15.0-54.58-generic 4.15.18), from pc- kernel_240.snap Version signature: 4.15.0-54.58-generic 4.15.18 Issue is non-deterministic, and happens in roughly 20% of the attempts. Running on: qemu-kvm, command line: kvm \ -bios /usr/share/ovmf/OVMF.fd \ -smp 2 -m 512 -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \ -device virtio-net-pci,netdev=mynet0 \ -drive file=pc.img,format=raw Commands that caused the problem: cryptsetup -q --type luks2 --key-file luksFormat /dev/sda4 LD_PRELOAD=/lib/no-udev.so cryptsetup --type luks2 --key-file open /dev/sda4 crypt-data Notes: - See https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1589083 for more information on the no-udev workaround. - The commands are scripted. Also tried to add a 200ms and 1s interval before opening the device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838324] 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 1838324 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/1838324 Title: 4.15.0-55 Kernel Breaks Wifi Status in linux package in Ubuntu: Incomplete Bug description: Network controller: Broadcom Inc. and subsidiaries BCM43228 802.11a/b/g/n Thinkpad T430U Wifi was not operational using kernel 4.15.0-55: no list of available networks and rfkill output indicated there were no hard or soft blocks. Reverted back to 4.10.0-38 to restore functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
I'm able to reproduce this with QCA6174 802.11ac Wireless Network Adapter on a Dell XPS 13 9370 (07E6). From a bit of googling this seems to be a widespread problem, but only mentioned solution is to replace the wifi card, as also mentioned in this bug report. Jay, did you have any success from testing the newer kernel + firmware? -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838271] Re: disco/linux: 5.0.0-23.24 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building,main:building,meta:building,signed:building + promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838271 Title: disco/linux: 5.0.0-23.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm 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: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1836856 (bionic/linux-oem-osp1), bug 1838270 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure), bug 1837728 (linux-aws) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Monday, 29. July 2019 15:47 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa lrm:building,main:building,meta:failed,signed:building trackers: bionic/linux-hwe: bug 1838270 disco/linux-aws: bug 1837728 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1838271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828578] Re: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS
** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1828578 Title: dell xps 9570 killer wifi reconnection issue followed by freeze + Ubuntu 18.04.2 LTS Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Bug description: Hello Team, Env - Dell XPS 9570 Ubuntu 18.04.2 , HWE kernel We are facing intermittently wifi reconnection issue on Ubuntu 18.04. Software upgrade is up-to date. Also some time we facing freezing issue due to this hard reset required to make machine back to normal. Please let me know if there are any known issue with this particular model on 18.04 ? Please let me know. Thanks Jay --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: itops 1579 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-04-25 (17 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 27c6:5395 Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. Bus 001 Device 004: ID 0c45:671d Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-18-generic root=UUID=c41f7762-f3a2-4b42-a019-97ca9bd85edc ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-18-generic N/A linux-backports-modules-4.18.0-18-generic N/A linux-firmware 1.173.5 Tags: bionic Uname: Linux 4.18.0-18-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 0HWTMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: IT-07384 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd04/26/2019:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0HWTMH:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1828578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
I can confirm this bug too. But additionally I have noticed one more interesting fact: It seems that this bug affects only PCs with dedicated GPUs (AMD, Nvidia). When I connect monitors into motherboard ports this bugs disappears. In my case via VGA(60Hz) and DVI-D(120Hz), but I believe that with HDMI and DisplayPort there will be the same results as with VGA or DVI. Unfortunately I haven't got a motherboard with DP or HDMI to test it. Because of this behaviour I have a theory that the bug exists only in Nvidia/AMD drivers for dedicated GPUs. I have got i5-4590 with integrated GPU and with this setup (without GPU) everything works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: multiple monitors on xorg = Was recently discussed over on https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 Another user + myself have the following issue: The slowest connected display limits the FPS. The test case we used is over at the top of the other bug report ^^ This we found today happens with either amd vega graphics, or nvidia pascal graphics, the vendor doesn't seem to matter. We have both seen the same issue (xorg). This is on 18.10, and booting into the 'Gnome (xorg)' login option. With the FPS being logged by journalctl -f. With only single monitor attached. Then it initially goes as high as the primary monitor can show. (And glmark2 running in background, to maintain a continued load). Which is 120fps for my case. Then as soon as secondary monitor is plugged in, which is a 60hz TV. This is being plugged into the HDMI port of the same graphics card in real time. Then the FPS logged by 'journalctl -f' drops, and becomes capped to 60hz, in the output being printed by journalctl -f. My setup: kernel 5.0.0-05-lowlatency #201903032031 NVIDIA Driver for UNIX platforms 415.27 (the closed source one) ubuntu 18.10 mutter version: mutter/cosmic-updates,now 3.30.2-1~ubuntu18.10.4 amd64 [installed] mutter-common/cosmic-updates,cosmic-updates,now 3.30.2-1~ubuntu18.10.4 all [installed] To confirm where the '.4' at the very end of the ~ubuntu18.10.4 version number, it seems to be that we have updated now on our client machines the be most recent bugfix updates, kindly provided by Daniel. Which closed the other bug https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1763892 being referred to, as being solved for people's single monitor scenarios. Thanks again for the other recent bug fixes in this area, it is a nice progress. Very helpful! We hope you can also look into this latest problem / issue for the multiple monitor scenario. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1820832/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838258] Re: Unable to configure VLAN on an additional OSA interface
Hi Michael, looks like we added our comments and files in parallel. I guess it's okay for now ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1838258 Title: Unable to configure VLAN on an additional OSA interface Status in Ubuntu on IBM z Systems: Triaged Status in iproute2 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: After installing a base Ubuntu 18.04.1 server, an additional OSA device "e530" is attached and configured with chzdev. Then a VLAN configuration should be applied using the ip command. However this results in the error message "RTNETLINK answers: File exists". >snip ip link add link ence530 name ence530.209 type vlan id 209 RTNETLINK answers: File exists snip< Executing the same steps on an Ubuntu 16.04.5 server, the ip command finishes without an error message but the VLAN interface is also not configured. Reproduction: - Install a 18.04.1 server - attach an additional OSA interface - configure a VLAN using the ip command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1838258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.
@kaihengfeng I'm unable to boot with v5.3-rc2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838141 Title: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling. Status in linux package in Ubuntu: Confirmed Bug description: intel_pstate not working. CPU frequency fixed at 800MHz. I've tried to modify frequency using "cpufreq-set" and also by directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*" to no success. I tried different versions of kernel, it started working on 4.17.0 but stopped working soon. These are the versions I tested. 5.2.3 - Not Working 5.1.0 - Not Working 4.19.60 - Not Working 4.18.20 - Not Working 4.17.19 - Not Working 4.17.10 - Not Working 4.17.5 - Not Working 4.17.3 - Working 4.17.2 - Working 4.17.1 - Working 4.17.0 - Working 4.16.18 - Not Working 4.15.0 - Not Working Please let me know if anything else is needed. thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-55-generic 4.15.0-55.60 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srijan 2219 F pulseaudio CurrentDesktop: KDE Date: Sat Jul 27 11:34:10 2019 InstallationDate: Installed on 2018-11-25 (243 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH315-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 i915.disable_power_well=1 nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-55-generic N/A linux-backports-modules-4.15.0-55-generic N/A linux-firmware 1.173.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_CFS dmi.board.vendor: CFL dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-51 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805631] Re: Freeze when usb-data-collision with usb-mouse
Does the issue still happen? Please attach `journalctl -b -1` after the issue happened and the system rebooted. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805631 Title: Freeze when usb-data-collision with usb-mouse Status in linux package in Ubuntu: Confirmed Bug description: To my computer I have connected a USB-hub and to that I have attached a USB-mouse and a USB-to-Ehternet adapter. The computer sometimes freezes completely and power button is the only escape. This happens when I scroll the mouse, press a button or moves the mouse (any event from the mouse). This can happen in any running program: Firefox, pdf-viewer, Libreoffice Writer... Most often this comes with my usb-to-ethernet LEDs switch off (during blink), but not always. Seems to be a collision event between my USB-mouse and USB-to-ethernet adapter, i.e mutex. An other computer without the USB-to-ethernet adapter never freezes. Configured in the same way. (I used Ubuntu 14.04 for a long time and this freeze never happened. In 18.04 this happens at least every two weeks. It is the same hardware.) $ uname -a Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 5276 F pulseaudio /dev/snd/controlC0: user 5276 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 MachineType: TOSHIBA SATELLITE Z30-B Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-42-generic root=/dev/mapper/hostname--vg--1542473018588400299-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 RfKill: 0: phy0: Wireless LAN Soft blocked: yes Hard blocked: no Tags: bionic Uname: Linux 4.15.0-42-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo vboxusers wireshark WifiSyslog: _MarkForUpload: False dmi.bios.date: 04/09/2015 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 3.20 dmi.board.asset.tag: 00 dmi.board.name: SATELLITE Z30-B dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion3.20:bd04/09/2015:svnTOSHIBA:pnSATELLITEZ30-B:pvrPT258E-007015N5:rvnTOSHIBA:rnSATELLITEZ30-B:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.family: 00 dmi.product.name: SATELLITE Z30-B dmi.product.version: PT258E-007015N5 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805631/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1807155] Re: Laptop doesn't wake up from deep sleep.
What happens if s2idle is used instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1807155 Title: Laptop doesn't wake up from deep sleep. Status in linux package in Ubuntu: Confirmed Bug description: While on battery power, Asus Zenbook UX461U laptop can't wake up from suspend with mem_sleep_default=deep kernel option. Upon opening the lid or pressing the power button the power LED switches from blinking to constant light, the keyboard LEDs blink instantly, but nothing more happens. Apart from the power LED the laptop doesn't show any signs of operation. The keyboard backlight doesn't work. The only way out of this state is powering the laptop off by long pressing the power button. On AC power, the laptop resumes from deep sleep normally. Deep sleep is crucial, because without the mem_sleep_default=deep option battery drain is very high (several percent per hour). ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: misha 2527 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 6 16:24:58 2018 HibernationDevice: RESUME=UUID=28642731-be8e-4c6b-9cfe-74d637c87bf0 InstallationDate: Installed on 2018-07-30 (129 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 13d3:56a2 IMC Networks Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX461UA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-12-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-12-01 (5 days ago) dmi.bios.date: 03/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX461UA.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX461UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX461UA.312:bd03/16/2018:svnASUSTeKCOMPUTERINC.:pnUX461UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX461UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX461UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
