[Kernel-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812310 Title: No more sound on lenovo R61i booting MATE 16.04 Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I was able to listen to a YouTube video from the laptop when booting Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04 Thanks for your consideration, Abu Billy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812310] Re: No more sound on lenovo R61i booting MATE 16.04
[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.] ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812310 Title: No more sound on lenovo R61i booting MATE 16.04 Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Expired Status in pulseaudio package in Ubuntu: Expired Bug description: When booting MATE 16.04 on my lenovo R61i, I no longer have sound. I was able to listen to a YouTube video from the laptop when booting Linux Mint, but can no longer hear ANYTHING when booting MATE 16.04 Thanks for your consideration, Abu Billy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1812310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838208] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280639/+files/ProcCpuinfo.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:
[Kernel-packages] [Bug 1838208] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280635/+files/CRDA.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:pn80X
[Kernel-packages] [Bug 1838208] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280640/+files/ProcCpuinfoMinimal.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05)
[Kernel-packages] [Bug 1838208] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280646/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-1
[Kernel-packages] [Bug 1838208] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280643/+files/PulseList.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnL
[Kernel-packages] [Bug 1838208] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280638/+files/Lspci.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:pn8
[Kernel-packages] [Bug 1838208] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280637/+files/IwConfig.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLEN
[Kernel-packages] [Bug 1838208] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280644/+files/RfKill.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:p
[Kernel-packages] [Bug 1838208] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280642/+files/ProcModules.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:
[Kernel-packages] [Bug 1838208] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280641/+files/ProcInterrupts.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19
[Kernel-packages] [Bug 1838208] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280636/+files/CurrentDmesg.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/201
[Kernel-packages] [Bug 1838208] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1838208/+attachment/5280645/+files/UdevDb.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/1838208 Title: Wifi stops responding sporadically on lenovo-yoga-720-15ikb Status in linux package in Ubuntu: Confirmed Bug description: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asif 1938 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2018-10-31 (276 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80X7 NonfreeKernelModules: wl Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 Tags: eoan wayland-session Uname: Linux 5.2.0-8-generic x86_64 UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/19/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 4MCN33WW(V2.05) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 720-15IKB dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:p
[Kernel-packages] [Bug 1838208] Re: Wifi stops responding sporadically on lenovo-yoga-720-15ikb
apport information ** Tags added: apport-collected ** Description changed: I can make this happen by trying to upload a large file using Firefox Nightly to https://send.firefox.com/ Within a few seconds (like 10-15) my wifi stops responding. Restarting network manager via service network-manager restart temporarily resolves the issue. This issue began appearing a week or so ago -- almost definitely not a month ago; my wifi used to be fine previously. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.18.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 14:59:13 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-10-31 (270 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) IpRoute: default via 192.168.69.1 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.69.0/24 dev wlp1s0 proto kernel scope link src 192.168.69.45 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: Upgraded to eoan on 2018-11-02 (268 days ago) nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 dd-wrt-vap-5g 1 21dd3ba5-f26c-434a-8a95-a87ddd1eb8d5 /org/freedesktop/NetworkManager/ActiveConnection/1 p2p-dev-wlp1s0 wifi-p2p disconnected none none /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.18.0 connected started full enabled enabled enabled enabled enabled + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu7 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: asif 1938 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 19.10 + InstallationDate: Installed on 2018-10-31 (276 days ago) + InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 13d3:5621 IMC Networks EasyCamera + Bus 001 Device 003: ID 06cb:0081 Synaptics, Inc. + Bus 001 Device 002: ID 8087:0a2b Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 80X7 + NonfreeKernelModules: wl + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-8-generic root=UUID=6c974fe8-3286-438d-9acd-d422be92ad9f ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 + RelatedPackageVersions: + linux-restricted-modules-5.2.0-8-generic N/A + linux-backports-modules-5.2.0-8-generic N/A + linux-firmware 1.181 + Tags: eoan wayland-session + Uname: Linux 5.2.0-8-generic x86_64 + UpgradeStatus: Upgraded to eoan on 2018-11-02 (273 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 07/19/2018 + dmi.bios.vendor: LENOVO + dmi.bios.version: 4MCN33WW(V2.05) + dmi.board.asset.tag: NO Asset Tag + dmi.board.name: LNVNB161216 + dmi.board.vendor: LENOVO + dmi.board.version: SDK0J40709 WIN + dmi.chassis.asset.tag: NO Asset Tag + dmi.chassis.type: 31 + dmi.chassis.vendor: LENOVO + dmi.chassis.version: Lenovo YOGA 720-15IKB + dmi.modalias: dmi:bvnLENOVO:bvr4MCN33WW(V2.05):bd07/19/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB: + dmi.product.family: YOGA 720-15IKB + dmi.product.name: 80X7 + dmi.product.sku: LENOVO_MT_80X7_BU_idea_FM_YOGA 720-15IKB + dmi.product.version: Lenovo YOGA 720-15IKB + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bu
[Kernel-packages] [Bug 1838824] Re: Bionic update: upstream stable patchset 2019-08-02
** Description changed: 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-08-02 - Ported from the following upstream stable releases: - v4.14.126, v4.19.51, - v4.14.127*, v4.19.52*, - v4.14.128, v4.19.53, - v4.14.129, v4.19.54, -v4.19.55*, - v4.14.130, v4.19.56, - v4.14.131*, - v4.14.132, v4.19.57, - v4.14.133, v4.19.58, - *Note: Bionic already carried all patches from this set + Ported from the following upstream stable releases: + v4.14.126, v4.19.51, + v4.14.127*, v4.19.52*, + v4.14.128, v4.19.53, + v4.14.129, v4.19.54, +    v4.19.55*, + v4.14.130, v4.19.56, + v4.14.131*, + v4.14.132, v4.19.57, + v4.14.133, v4.19.58, + *Note: Bionic already carried all patches from this set    from git://git.kernel.org/ + + rapidio: fix a NULL pointer dereference when create_workqueue() fails + fs/fat/file.c: issue flush after the writeback of FAT + sysctl: return -EINVAL if val violates minmax + ipc: prevent lockup on alloc_msg and free_msg + ARM: prevent tracing IPI_CPU_BACKTRACE + mm/hmm: select mmu notifier when selecting HMM + hugetlbfs: on restore reserve error path retain subpool reservation + mem-hotplug: fix node spanned pages when we have a node with only ZONE_MOVABLE + mm/cma.c: fix crash on CMA allocation if bitmap allocation fails + mm/cma.c: fix the bitmap status to show failed allocation reason + mm/cma_debug.c: fix the break condition in cma_maxchunk_get() + mm/slab.c: fix an infinite loop in leaks_show() + kernel/sys.c: prctl: fix false positive in validate_prctl_map() + thermal: rcar_gen3_thermal: disable interrupt in .remove + drivers: thermal: tsens: Don't print error message on -EPROBE_DEFER + mfd: tps65912-spi: Add missing of table registration + mfd: intel-lpss: Set the device in reset state when init + drm/nouveau/disp/dp: respect sink limits when selecting failsafe link configuration + mfd: twl6040: Fix device init errors for ACCCTL register + perf/x86/intel: Allow PEBS multi-entry in watermark mode + drm/bridge: adv7511: Fix low refresh rate selection + objtool: Don't use ignore flag for fake jumps + EDAC/mpc85xx: Prevent building as a module + pwm: meson: Use the spin-lock only to protect register modifications + ntp: Allow TAI-UTC offset to be set to zero + f2fs: fix to avoid panic in do_recover_data() + f2fs: fix to clear dirty inode in error path of f2fs_iget() + f2fs: fix to avoid panic in dec_valid_block_count() + f2fs: fix to do sanity check on valid block count of segment + percpu: remove spurious lock dependency between percpu and sched + configfs: fix possible use-after-free in configfs_register_group + uml: fix a boot splat wrt use of cpu_all_mask + mmc: mmci: Prevent polling for busy detection in IRQ context + watchdog: imx2_wdt: Fix set_timeout for big timeout values + watchdog: fix compile time error of pretimeout governors + blk-mq: move cancel of requeue_work into blk_mq_release + iommu/vt-d: Set intel_iommu_gfx_mapped correctly + misc: pci_endpoint_test: Fix test_reg_bar to be updated in pci_endpoint_test + nvme-pci: unquiesce admin queue on shutdown + ALSA: hda - Register irq handler after the chip initialization + nvmem: core: fix read buffer in place + fuse: retrieve: cap requested size to negotiated max_write + nfsd: allow fh_want_write to be called twice + vfio: Fix WARNING "do not call blocking ops when !TASK_RUNNING" + x86/PCI: Fix PCI IRQ routing table memory leak + platform/chrome: cros_ec_proto: check for NULL transfer function + PCI: keystone: Prevent ARM32 specific code to be compiled for ARM64 + soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher + clk: rockchip: Turn on "aclk_dmac1" for suspend on rk3288 + soc: rockchip: Set the proper PWM for rk3288 + ARM: dts: imx51: Specify IMX5_CLK_IPG as "ahb" clock to SDMA + ARM: dts: imx50: Specify IMX5_CLK_IPG as "ahb" clock to SDMA + ARM: dts: imx53: Specify IMX5_CLK_IPG as "ahb" clock to SDMA + ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA + ARM: dts: imx7d: Specify IMX7D_CLK_IPG as "ipg" clock to SDMA + ARM: dts: imx6ul: Specify IMX6UL_CLK_IPG as "ipg" clock to SDMA + ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA + ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as
[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
Hello Ai Lim, I have just uploaded a new version (~ppa2) to the same PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1828495 for Bionic. Could you test this version and let me know if it presents MDS_NO MSR flag ? I'll test on my side (as soon as the package is compiled in the PPA) as well. Thanks a lot for the feedback. I'll provide the same change for Ubuntu 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/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in libvirt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: Fix Released Status in libvirt source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: Fix Committed Status in libvirt source package in Cosmic: Won't Fix Status in linux source package in Cosmic: Won't Fix Status in qemu source package in Cosmic: Won't Fix Status in libvirt source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: Fix Committed Status in libvirt source package in Eoan: Fix Released Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: Fix Released Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported features. They are all based in upstream changes but, for obvious reasons, backporting and/or cherry-picking those could bring issues. Biggest concern is breaking something that currently works. Right now, the parts being changed that could affect other CPU types would be related to a small refactoring of how the features are organized, and that would be seen right away when trying to start a new VM after the package is installed. * Other tests, related to the features being backported, are being done by our KVM regression tests, including migration combinations, to reduce chances that a regression is introduced. [Other Info] * N/A To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1828495/+subscriptions -- Mailing list: https://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 1822363] Re: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected
I have checked v5.2 and it is working. How to install it on upgraded 18.04 frm 16.04 which is not bootable due to this usb bug? Is it possible to install it from bootable 16.04 (I have it on on different partition)? Kai-Heng Feng: > Spotted this commit when I am doing an unrelated task: > commit f7fac17ca925faa03fc5eb854c081a24075f8bad > Author: Andrey Smirnov > Date: Wed May 22 14:34:01 2019 +0300 > > xhci: Convert xhci_handshake() to use readl_poll_timeout_atomic() > > Xhci_handshake() implements the algorithm already captured by > readl_poll_timeout_atomic(). Convert the former to use the latter to > avoid repetition. > > Turned out this patch also fixes a bug on the AMD Stoneyridge platform > where usleep(1) sometimes takes over 10ms. > This means a 5 second timeout can easily take over 15 seconds which will > trigger the watchdog and reboot the system. > > [Add info about patch fixing a bug to commit message -Mathias] > Signed-off-by: Andrey Smirnov > Tested-by: Raul E Rangel > Reviewed-by: Raul E Rangel > Cc: > Signed-off-by: Mathias Nyman > Signed-off-by: Greg Kroah-Hartman > > Can you try this? It's in Linux kernel v5.2. > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822363 Title: Booting hangs when USB 3.0 Etron EJ168 PCI card is detected Status in linux package in Ubuntu: Confirmed Bug description: I have installed Etron EJ168 PCI USB 3.0 [1B6F:7023] which briliantly works in any Windows OS (I use multiboot PC) on my Conroe865PE AGP/PCI Intel Kentsfield QX6800 system with classic BIOS (non UEFI). There are no devices connected to PCI USB card during boot. The desktop Ubuntu 18.04 kernel 4.15.0-46-generic freezes with this card during boot (see attached "photo log" with boot and grub options). I can't access/login Ubuntu or console. It was checked and confirmed on ubuntu-18.04.1-desktop-amd64.iso LIVE CD desktop (with acpi=off option too). Previously I was used and removed USB 3.0 NEC Renesas upd720200 PCI card [1033:0194], which was partially workable under my installation of Ubuntu 18.04 and Windows. It had problems from time to time with FW load from card on start and not detecting USB devices connected even if FW present. I tried and also removed USB 3.0 NEC Renesas upd720202 PCI card [1912:0015] which also was partially workable in the same way (other card bios and newer NEC chip). System was fully bootable with NEC cards. The Etron EJ168 works superb on Windows OS's with directly or with hub connections with USB devices. I can assist in any way to solve this bug as IT Professional. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822363/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837614] Re: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Promote to Proposed - phase-changed: Friday, 02. August 2019 17:00 UTC + phase: Ready for Testing + phase-changed: Friday, 02. August 2019 22:15 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + verification-testing: Ongoing -- testing in progress 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/1837614 Title: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Ready for Testing phase-changed: Friday, 02. August 2019 22:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786894] Re: test_265_config_retpoline in kernel_security_test failed on 3.13 Precise
Sorry for the delay in addressing this, I've fixed up QRT to expect
CONFIG_RETPOLINE for 3.13 kernels on precise, and not fail if earlier
kernels have it enabled where we don't expect it.
https://git.launchpad.net/qa-regression-
testing/commit/?id=e01c4c81828765b3c66870cf4567cd83705b7b0f and
https://git.launchpad.net/qa-regression-
testing/commit/?id=aa614248beb08d904efb5b3a0f0773525a85c6cb .
Thanks.
** Changed in: qa-regression-testing
Status: Confirmed => Fix Released
** Changed in: linux (Ubuntu)
Status: Triaged => 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/1786894
Title:
test_265_config_retpoline in kernel_security_test failed on 3.13
Precise
Status in QA Regression Testing:
Fix Released
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Invalid
Bug description:
== Justification ==
In the Precise 3.13 kernel, the CONFIG_RETPOLINE was set to y in commit
eae992be4, which should be disabled to meet the security team's requirement.
==
 FAIL: test_265_config_retpoline (__main__.KernelSecurityConfigTest)
 Ensure retpoline configuration option is set
 --
 Traceback (most recent call last):
 File "./test-kernel-security.py", line 2445, in test_265_config_retpoline
 self.assertKernelConfig('RETPOLINE', expected)
 File "./test-kernel-security.py", line 209, in assertKernelConfig
 self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
 '%s option was expected to be unset in the kernel config' % name)
 AssertionError: RETPOLINE option was expected to be unset in the kernel
config
In this test case, this config was expected to be NOT set:
elif self.lsb_release['Release'] == 12.04:
self._skipped("RETPOLINE compiler not in precise")
expected = False
self.assertKernelConfig('RETPOLINE', expected)
== Fix ==
[Precise/lts-backport-trusty][SRU][PATCHv2] Revert "UBUNTU: [Config]
CONFIG_RETPOLINE=y"
== Test ==
The test_265_config_retpoline will pass after disabling CONFIG_RETPOLINE
== Regression Potential ==
Minimal.
No code changes, just a config changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1786894/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron I tried with the kernel 5.3-rc2 but the wifi does not work and the previous workround does not work anymore since only the module rtwpci can be loaded. The module r8822be is not present. I tried the module rtw88 but the kernel module in use is always rtwpci. Cheers, Pascal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: 4.4.0-1016.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:55 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copied to Signing signed:retry-needed 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: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:55 UTC reason: promote-to-proposed: Pending -- package copied to Signing signed:retry-needed 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 1759836] Re: systemd-udevd consumes 100% of CPU
Ignore my previous two posts. It's fixed. I uninstalled & reinstalled Nvidia driver related things (which didn't really want to happen). I don't know why it happened nor why it produced symptoms related to one of the posts here (maybe just an unrelated coincidence?) nor why it happened when I moved the hard drive to the Dell laptop. -- 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/1759836 Title: systemd-udevd consumes 100% of CPU Status in linux: Confirmed Status in The Ubuntu Power Consumption Project: New Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Confirmed Bug description: The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not noticing any difference in my computer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 29 08:52:54 2018 InstallationDate: Installed on 2018-03-05 (23 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304) MachineType: Dell Inc. Inspiron N5010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1 SourcePackage: systemd SystemdDelta:  [EXTENDED] /lib/systemd/system/rc-local.service → /lib/systemd/system/rc-local.service.d/debian.conf  [EXTENDED] /lib/systemd/system/user@.service → /lib/systemd/system/user@.service.d/timeout.conf  2 overridden configuration files found. UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 08R0GW dmi.board.vendor: Dell Inc. dmi.board.version: A12 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A12 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12: dmi.product.name: Inspiron N5010 dmi.product.version: A12 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838824] [NEW] Bionic update: upstream stable patchset 2019-08-02
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-08-02 Ported from the following upstream stable releases: v4.14.126, v4.19.51, v4.14.127*, v4.19.52*, v4.14.128, v4.19.53, v4.14.129, v4.19.54, v4.19.55*, v4.14.130, v4.19.56, v4.14.131*, v4.14.132, v4.19.57, v4.14.133, v4.19.58, *Note: Bionic already carried all patches from this set    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-08-02 -upstream stable patchset 2019-08-02 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.14.126, v4.19.51, + v4.14.127*, v4.19.52*, + v4.14.128, v4.19.53, + v4.14.129, v4.19.54, +v4.19.55*, + v4.14.130, v4.19.56, + v4.14.131*, + v4.14.132, v4.19.57, + v4.14.133, v4.19.58, + *Note: Bionic already carried all patches from this set + +    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/1838824 Title: Bionic update: upstream stable patchset 2019-08-02 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-08-02 Ported from the following upstream stable releases: v4.14.126, v4.19.51, v4.14.127*, v4.19.52*, v4.14.128, v4.19.53, v4.14.129, v4.19.54, v4.19.55*, v4.14.130, v4.19.56, v4.14.131*, v4.14.132, v4.19.57, v4.14.133, v4.19.58, *Note: Bionic already carried all patches from this set    from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838824/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837614] Re: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Friday, 02. August 2019 17:00 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync 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/1837614 Title: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Friday, 02. August 2019 17:00 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.16 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:40 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Pending -- package copied to Signing signed:retry-needed 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/1837617 Title: bionic/linux-fips: 4.15.0-1013.16 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:40 UTC reason: promote-to-proposed: Pending -- package copied to Signing signed:retry-needed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581088] Re: Middle mouse (wheel-click) button stopped working after upgrade to 16.04
Embarrassing. Logitec M185. Therefore I put me as 'affects me'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581088 Title: Middle mouse (wheel-click) button stopped working after upgrade to 16.04 Status in linux package in Ubuntu: Confirmed Bug description: Since upgrading to 16.04 clicking the middle mouse button (scroll wheel) on my Logitech M185 stopped working. xev does not even show the event for clicking the wheel, while it shows other button clicks and scroll wheel up/down events. xinput list shows the USB receiver 2 times: ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=9[slave pointer (2)] ⎜ ↳ Logitech USB Receiver id=10 [slave pointer (2)] ⎜ ↳ HID 046a:0023 id=13 [slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=16 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=17 [slave pointer (2)] Listing the capabilities looks like this: $ xinput list 9 Logitech USB Receiver id=9[slave pointer (2)]  Reporting 7 classes:   Class originated from: 9. Type: XIButtonClass   Buttons supported: 24   Button labels: "Button Left" "Button Middle" "Button Right" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right" "Button Side" "Button Extra" "Button Forward" "Button Back" "Button Task" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown" "Button Unknown"   Button state:   Class originated from: 9. Type: XIValuatorClass   Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 9. Type: XIValuatorClass   Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 9. Type: XIValuatorClass   Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 9. Type: XIValuatorClass   Detail for Valuator 3: Label: Rel Vert Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 9. Type: XIScrollClass   Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0   Class originated from: 9. Type: XIScrollClass   Scroll info for Valuator 3 type: 1 (vertical) increment: -1.00 flags: 0x2 ( preferred ) $ xinput list 10 Logitech USB Receiver id=10 [slave pointer (2)]  Reporting 6 classes:   Class originated from: 10. Type: XIButtonClass   Buttons supported: 7   Button labels: "Button 0" "Button Unknown" "Button Unknown" "Button Wheel Up" "Button Wheel Down" "Button Horiz Wheel Left" "Button Horiz Wheel Right"   Button state:   Class originated from: 10. Type: XIKeyClass   Keycodes supported: 248   Class originated from: 10. Type: XIValuatorClass   Detail for Valuator 0: Label: Rel X Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 10. Type: XIValuatorClass   Detail for Valuator 1: Label: Rel Y Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 10. Type: XIValuatorClass   Detail for Valuator 2: Label: Rel Horiz Wheel Range: -1.00 - -1.00 Resolution: 1 units/m Mode: relative   Class originated from: 10. Type: XIScrollClass   Scroll info for Valuator 2 type: 2 (horizontal) increment: 1.00 flags: 0x0 Does anyone have an idea how I can attempt to further debug that issue? Or maybe even a solution? Should I consider this issue a bug? Can I provide more info? --- ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC2: toby 11625 F pulseaudio  /dev/snd/controlC0: toby 11625 F pulseaudio  /dev/snd/pcmC1D0p: toby 11625 F...m pulseaudio  /dev/snd/controlC1: toby 11625 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5e3a6d2e-05f8-4d01-b80c-a9f200e6 InstallationDate: Installed on 2014-04-24 (749 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) MachineType: LENOVO 20AL00C
[Kernel-packages] [Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Promote to Proposed - phase-changed: Thursday, 01. August 2019 21:00 UTC + phase: Promote to Proposed + phase-changed: Friday, 02. August 2019 20:55 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress 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: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:55 UTC reason: promote-to-proposed: Ongoing -- review in progress 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 1831831] Re: Touchpad does not respond IdeaPad L340
Correction to my posting before: Today I once again run $ sudo apt install linux-generic-hwe-18.04-edge and after reboot the touchpad responds! Great. One problem still exists: rightclick on the touchpad is like leftclick. That means, the context menu doesn't open by rightclick on the touchpad. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831831 Title: Touchpad does not respond IdeaPad L340 Status in linux package in Ubuntu: Confirmed Bug description: Lenovo IdeaPad L-340 upon installing Ubuntu 18.04.2 LTS, all other laptop inputs work except for touchpad. Touchpad does not respond to input of any kind - clicks, gestures, or otherwise. dmesg | grep -i elan [2.987373] i2c_hid i2c-ELAN0625:00: i2c-ELAN0625:00 supply vdd not found, using dummy regulator ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-20-generic 4.18.0-20.21~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20 Uname: Linux 4.18.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 5 23:07:23 2019 InstallationDate: Installed on 2019-05-22 (15 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tristan1542 F pulseaudio /dev/snd/pcmC0D0p: tristan1542 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-22 (50 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 04f2:b624 Chicony Electronics Co., Ltd Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LG Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic root=UUID=c3fb3b60-c7d3-40a8-8787-51781e035183 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-21-generic N/A linux-backports-modules-4.18.0-21-generic N/A linux-firmware 1.173.6 Tags: bionic Uname: Linux 4.18.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/20/2018 dmi.bios.vendor: LENOVO dmi.bios.version: ATCN14WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad L340-15IWL dmi.modalias: dmi:bvnLENOVO:bvrATCN14WW:bd12/20/2018:svnLENOVO:pn81LG:pvrLenovoIdeaPadL340-15IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadL340-15IWL: dmi.product.family: IdeaPad L340-15IWL dmi.product.name: 81LG dmi.product.sku: LENOVO_MT_81LG_BU_idea_FM_IdeaPad L340-15IWL dmi.product.version: Lenovo IdeaPad L340-15IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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: 4.4.0-1016.21 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You 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: 4.4.0-1016.21 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837609 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:55 UTC reason: promote-to-proposed: Ongoing -- review in progress 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 1837617] Re: bionic/linux-fips: 4.15.0-1013.16 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Ready for Promote to Proposed - phase-changed: Friday, 02. August 2019 15:20 UTC + phase: Promote to Proposed + phase-changed: Friday, 02. August 2019 20:40 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress 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/1837617 Title: bionic/linux-fips: 4.15.0-1013.16 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:40 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.16 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837617 Title: bionic/linux-fips: 4.15.0-1013.16 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Promote to Proposed phase-changed: Friday, 02. August 2019 20:40 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
yes. Output from lscpu if that helps: Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 48 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: AuthenticAMD CPU family: 21 Model: 2 Model name: AMD FX(tm)-8350 Eight-Core Processor Stepping:0 CPU MHz: 1405.672 CPU max MHz: 4000. CPU min MHz: 1400. BogoMIPS:8035.83 Virtualisation: AMD-V L1d cache: 16K L1i cache: 64K L2 cache:2048K L3 cache:8192K NUMA node0 CPU(s): 0-7 Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 popcnt aes xsave avx f16c lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs xop skinit wdt fma4 tce nodeid_msr tbm topoext perfctr_core perfctr_nb cpb hw_pstate ssbd ibpb vmmcall bmi1 arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold -- You 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 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Promote to Proposed - phase-changed: Friday, 02. August 2019 16:55 UTC + phase: Testing + phase-changed: Friday, 02. August 2019 18:41 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 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/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Friday, 02. August 2019 18:41 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838590] Re: Update thermald to 1.9 release
** Changed in: thermald (Ubuntu) Importance: Medium => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1838590 Title: Update thermald to 1.9 release Status in dptfxtract package in Ubuntu: New Status in thermald package in Ubuntu: New Bug description: The thermald 1.9 release was just tagged, and has potential to help quite a bit with platform performance on some newer platforms when run with kernel 5.3. It would be nice to update eoan to this new release. > - The major change in this version is the active power limits adjustment. This will be useful to improve performance on some newer platform. But this will will lead to increase in CPU and other temperatures. Hence this is important to run dptfxtract version 1.4.1 tool to get performance sensitive thermal limits (https://github.com/intel/dptfxtract/commits/v1.4.1). If the default configuration picked up by thermald is not optimal, user can select other less aggressive configuration. Refer to the README here https://github.com/intel/dptfxtract/blob/master/README.txt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dptfxtract/+bug/1838590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837397] Re: Make possible to load Mellanox OFED modules
I'm still not see kernels in proposed for bionic and xenial. Please let me know if they will not make it into proposed today. -- 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/1837397 Title: Make possible to load Mellanox OFED modules Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Xenial: Fix Committed Status in linux-azure source package in Cosmic: Invalid Status in linux-azure source package in Disco: Fix Committed Bug description: [Impact] Infiniband and Mellanox modules are currently built-in which makes impossible for users to build and load OFED drivers. [Test Case] Users should be able to build and load OFED drivers without conflicting with the built-in drivers. [Regression Potential] The major regression potential is related to the linux-modules or linux-modules-extra packages. The built-in modules should be build as loadable modules and placed at the linux-modules package, having then in the linux-modules-extra package will cause issues for current users. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1837397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280550/+files/UdevDb.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280548/+files/ProcModules.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Friday, 02. August 2019 16:55 UTC reason: - promote-to-proposed: Ongoing -- review in progress + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 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/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Friday, 02. August 2019 16:55 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] Re: TPM event log does not contain events measured after ExitBootServices
apport information ** Tags added: apport-collected bionic ** Description changed: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. - There are upstream patches to fix this in the mainline kernel tree: - https://lkml.org/lkml/2019/5/17/725 + There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.5 + Architecture: amd64 + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2019-06-20 (43 days ago) + InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + eth0 no wireless extensions. + + lono wireless extensions. + Lspci: + + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: Microsoft Corporation Virtual Machine + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 hyperv_fb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro + ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-22-generic N/A + linux-backports-modules-4.18.0-22-generic N/A + linux-firmware 1.173.3 + RfKill: + + Tags: bionic + Uname: Linux 4.18.0-22-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 01/30/2019 + dmi.bios.vendor: Microsoft Corporation + dmi.bios.version: Hyper-V UEFI Release v4.0 + dmi.board.asset.tag: None + dmi.board.name: Virtual Machine + dmi.board.vendor: Microsoft Corporation + dmi.board.version: Hyper-V UEFI Release v4.0 + dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 + dmi.chassis.type: 3 + dmi.chassis.vendor: Microsoft Corporation + dmi.chassis.version: Hyper-V UEFI Release v4.0 + dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: + dmi.product.family: Virtual Machine + dmi.product.name: Virtual Machine + dmi.product.sku: None + dmi.product.version: Hyper-V UEFI Release v4.0 + dmi.sys.vendor: Microsoft Corporation ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280543/+files/AlsaInfo.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4
[Kernel-packages] [Bug 1838796] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280551/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280547/+files/ProcInterrupts.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280546/+files/ProcCpuinfoMinimal.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280544/+files/CurrentDmesg.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280545/+files/ProcCpuinfo.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1838796/+attachment/5280549/+files/PulseList.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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Confirmed Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-06-20 (43 days ago) InstallationMedia: Ubuntu-Server 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eth0 no wireless extensions. lono wireless extensions. Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-22-generic root=UUID=fcb8dc9d-4dd3-490f-9f1c-fa6364770bb0 ro ProcVersionSignature: Ubuntu 4.18.0-22.23~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-22-generic N/A linux-backports-modules-4.18.0-22-generic N/A linux-firmware 1.173.3 RfKill: Tags: bionic Uname: Linux 4.18.0-22-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/30/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: Hyper-V UEFI Release v4.0 dmi.board.asset.tag: None dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: Hyper-V UEFI Release v4.0 dmi.chassis.asset.tag: 8486-4870-7514-9524-5524-7794-69 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: Hyper-V UEFI Release v4.0 dmi.modalias: dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd01/30/2019:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0: dmi.product.family: Virtual Machine dmi.product.name: Virtual Machine dmi.product.sku: None dmi.product.version: Hyper-V UEFI Release v4.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Trying the first kernel without the change event sauce also fails: [ 532.823594] bcache: run_cache_set() invalidating existing data [ 532.828876] bcache: register_cache() registered cache device nvme0n1p2 [ 532.869716] bcache: register_bdev() registered backing device vda1 [ 532.994355] bcache: bch_cached_dev_attach() Caching vda1 as bcache0 on set 21d89237-231d-4af6-a4c8-4b1b8fa5eef5 [ 533.051588] bcache: register_bcache() error /dev/vda1: device already registered [ 533.094717] bcache: register_bcache() error /dev/vda1: device already registered [ 533.120063] bcache: register_bcache() error /dev/vda1: device already registered [ 533.142517] bcache: register_bcache() error /dev/vda1: device already registered [ 533.191069] bcache: register_bcache() error /dev/vda1: device already registered [ 533.249877] bcache: register_bcache() error /dev/vda1: device already registered [ 533.282653] bcache: register_bcache() error /dev/vda1: device already registered [ 533.301225] bcache: register_bcache() error /dev/vda1: device already registered [ 533.310505] bcache: register_bcache() error /dev/vda1: device already registered [ 533.318959] bcache: register_bcache() error /dev/vda1: device already registered [ 533.374121] bcache: register_bcache() error /dev/vda1: device already registered [ 533.536920] bcache: register_bcache() error /dev/vda1: device already registered [ 533.581468] bcache: register_bcache() error /dev/vda1: device already registered [ 533.589270] bcache: register_bcache() error /dev/vda1: device already registered [ 533.595986] bcache: register_bcache() error /dev/vda1: device already registered [ 533.602638] bcache: register_bcache() error /dev/vda1: device already registered [ 533.651848] bcache: register_bcache() error /dev/vda1: device already registered [ 533.677836] bcache: register_bcache() error /dev/vda1: device already registered [ 533.712074] bcache: register_bcache() error /dev/vda1: device already registered [ 533.717682] bcache: register_bcache() error /dev/vda1: device already registered [ 533.723354] bcache: register_bcache() error /dev/vda1: device already registered [ 533.728951] bcache: register_bcache() error /dev/vda1: device already registered [ 533.777602] bcache: register_bcache() error /dev/vda1: device already registered [ 553.784393] md: md0: resync done. [ 725.983387] INFO: task python3:413 blocked for more than 120 seconds. [ 725.985099] Tainted: P O 4.15.0-56-generic #62~lp1796292+1 [ 725.986820] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 725.988649] python3 D0 413405 0x [ 725.988652] Call Trace: [ 725.988684] __schedule+0x291/0x8a0 [ 725.988687] schedule+0x2c/0x80 [ 725.988710] bch_bucket_alloc+0x1fa/0x350 [bcache] [ 725.988722] ? wait_woken+0x80/0x80 [ 725.988726] __bch_bucket_alloc_set+0xfe/0x150 [bcache] [ 725.988729] bch_bucket_alloc_set+0x4e/0x70 [bcache] [ 725.988734] __uuid_write+0x59/0x150 [bcache] [ 725.988738] ? __write_super+0x137/0x170 [bcache] [ 725.988742] bch_uuid_write+0x16/0x40 [bcache] [ 725.988746] __cached_dev_store+0x1d8/0x8a0 [bcache] [ 725.988750] bch_cached_dev_store+0x39/0xc0 [bcache] [ 725.988758] sysfs_kf_write+0x3c/0x50 [ 725.988759] kernfs_fop_write+0x125/0x1a0 [ 725.988765] __vfs_write+0x1b/0x40 [ 725.988766] vfs_write+0xb1/0x1a0 [ 725.988767] SyS_write+0x5c/0xe0 [ 725.988774] do_syscall_64+0x73/0x130 [ 725.988777] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 725.988779] RIP: 0033:0x7fa71a23b154 [ 725.988780] RSP: 002b:7ffec74f2828 EFLAGS: 0246 ORIG_RAX: 0001 [ 725.988783] RAX: ffda RBX: 0008 RCX: 7fa71a23b154 [ 725.988783] RDX: 0008 RSI: 02a90030 RDI: 0003 [ 725.988784] RBP: 7fa71a7366c0 R08: R09: [ 725.988785] R10: 0100 R11: 0246 R12: 0003 [ 725.988785] R13: R14: 02a90030 R15: 027c4e60 -- You 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 remo
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
After some help from Ryan (on IRC) I've been able to run the last
reproducer script and trigger the same trace. Now I should be able to
collect all the information that I need and hopefully post a new test
kernel (fixed for real...) soon.
--
You 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 1838796] 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 1838796 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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: Incomplete Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837614] Re: bionic/linux-ibm-gt: 4.15.0-1029.31 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt - phase: Ready for Promote to Proposed - phase-changed: Friday, 26. July 2019 20:04 UTC + phase: Promote to Proposed + phase-changed: Friday, 02. August 2019 17:00 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress 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/1837614 Title: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Friday, 02. August 2019 17:00 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837614] Re: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837614 Title: bionic/linux-ibm-gt: 4.15.0-1029.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Promote to Proposed phase-changed: Friday, 02. August 2019 17:00 UTC reason: promote-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838796] [NEW] TPM event log does not contain events measured after ExitBootServices
Public bug reported: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 ** 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/1838796 Title: TPM event log does not contain events measured after ExitBootServices Status in linux package in Ubuntu: New Bug description: The TPM event log (/sys/kernel/security/tpm0/binary_bios_measurements) does not contain any events that are measured by UEFI after the kernel's EFI Boot stub calls ExitBootServices(). This means that PCR values calculated from the event log will not match the actual PCR values on the machine for PCR indices into which these events are measured. There are upstream patches to fix this in the mainline kernel tree: https://lkml.org/lkml/2019/5/17/725 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838796/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Ready for Promote to Proposed - phase-changed: Friday, 26. July 2019 17:01 UTC + phase: Promote to Proposed + phase-changed: Friday, 02. August 2019 16:55 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 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/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Friday, 02. August 2019 16:55 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837590] Re: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1837590 Title: bionic/linux-snapdragon: 4.15.0-1059.65 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: 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 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 1837589 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Friday, 02. August 2019 16:55 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1837589 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837590/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837617] Re: bionic/linux-fips: 4.15.0-1013.16 -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 -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Promote to Proposed - phase-changed: Thursday, 01. August 2019 20:50 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 02. August 2019 15:20 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:failed + promote-to-proposed: Pending -- ready for review 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/1837617 Title: bionic/linux-fips: 4.15.0-1013.16 -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-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid 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: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Proposed phase-changed: Friday, 02. August 2019 15:20 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
All tasks have been completed and the bug is being set to Fix Released ** Changed in: kernel-sru-workflow Status: In Progress => Fix Released ** Tags removed: kernel-release-tracking-bug-live -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker Status in Kernel SRU Workflow: Fix Released 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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Complete phase-changed: Friday, 02. August 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Andrea: It might be worth saying whether you have a model with the 'NFC' chip. (For - *I think*, and at least with the sixth generation - the following holds. Once one has Lenovo's BIOS updates applied, then only models with the NFC chip have the sleep/pad problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendo
[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: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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), bug 1837566 (bionic/linux- azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837567 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Friday, 02. August 2019 15:10 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-azure-edge: bug 1837566 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 1838087] Re: bionic/linux-azure: 5.0.0-1013.13~18.04.2 -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 1838086 (azure-kernel), bug 1837566 (bionic/linux- azure-edge) -- 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 + phase: Promote to Proposed + phase-changed: Friday, 02. August 2019 15:10 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-azure-edge: bug 1837566 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: In Progress Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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), bug 1837566 (bionic/linux- azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837567 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Friday, 02. August 2019 15:10 UTC reason: promote-to-proposed: Ongoing -- review in progress trackers: bionic/linux-azure-edge: bug 1837566 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 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty - phase: Release - phase-changed: Friday, 02. August 2019 14:40 UTC + phase: Complete + phase-changed: Friday, 02. August 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true - reason: - promote-to-updates: Ongoing -- packages not yet published variant: debs -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Complete phase-changed: Friday, 02. August 2019 14:51 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty - phase: Ready for Release - phase-changed: Friday, 02. August 2019 12:15 UTC + phase: Release + phase-changed: Friday, 02. August 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Pending -- ready to copy + promote-to-updates: Ongoing -- packages not yet published variant: debs -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Release phase-changed: Friday, 02. August 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-updates Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: In Progress 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Release phase-changed: Friday, 02. August 2019 14:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Ongoing -- packages not yet published variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
I tried the +3 kernel first, and I got 3 installs and then this hang:
[ 549.828710] bcache: run_cache_set() invalidating existing data
[ 549.836485] bcache: register_cache() registered cache device nvme1n1p2
[ 549.937486] bcache: register_bdev() registered backing device vdg
[ 550.018855] bcache: bch_cached_dev_attach() Caching vdg as bcache3 on set
c7abd3ea-f9c9-415a-b8a6-9efeddc3e030
[ 550.074760] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 550.316246] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 550.545840] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 550.565928] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 550.724285] bcache: register_bcache() error /dev/vdg: device already
registered (emitting change event)
[ 562.352520] md: md0: resync done.
[ 725.980380] INFO: task python3:27303 blocked for more than 120 seconds.
[ 725.982364] Tainted: P O 4.15.0-56-generic
#62~lp1796292+3
[ 725.984228] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 725.986284] python3 D0 27303 27293 0x
[ 725.986287] Call Trace:
[ 725.986319] __schedule+0x291/0x8a0
[ 725.986322] schedule+0x2c/0x80
[ 725.986337] bch_bucket_alloc+0x320/0x3a0 [bcache]
[ 725.986359] ? wait_woken+0x80/0x80
[ 725.986363] __bch_bucket_alloc_set+0xfe/0x150 [bcache]
[ 725.986367] bch_bucket_alloc_set+0x4e/0x70 [bcache]
[ 725.986372] __uuid_write+0x59/0x150 [bcache]
[ 725.986377] ? __write_super+0x137/0x170 [bcache]
[ 725.986382] bch_uuid_write+0x16/0x40 [bcache]
[ 725.986386] __cached_dev_store+0x1d8/0x8a0 [bcache]
[ 725.986391] bch_cached_dev_store+0x39/0xc0 [bcache]
[ 725.986399] sysfs_kf_write+0x3c/0x50
[ 725.986401] kernfs_fop_write+0x125/0x1a0
[ 725.986406] __vfs_write+0x1b/0x40
[ 725.986407] vfs_write+0xb1/0x1a0
[ 725.986409] SyS_write+0x5c/0xe0
[ 725.986416] do_syscall_64+0x73/0x130
[ 725.986419] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 725.986421] RIP: 0033:0x7f2d7c39a154
[ 725.986422] RSP: 002b:7fff80c5e048 EFLAGS: 0246 ORIG_RAX:
0001
[ 725.986426] RAX: ffda RBX: 0008 RCX: 7f2d7c39a154
[ 725.986426] RDX: 0008 RSI: 0247e7d0 RDI: 0003
[ 725.986427] RBP: 7f2d7c8956c0 R08: R09:
[ 725.986428] R10: 0100 R11: 0246 R12: 0003
[ 725.986428] R13: R14: 0247e7d0 R15: 021b6e60
--
You 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 1787857] Re: USB mouse cursor lags after random time of correct behaviour
Does your system use AMD CPU? Looks like it only happens to AMD systems. -- You 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 1796292] Re: Tight timeout for bcache removal causes spurious failures
Ryan, unfortunately the last reproducer script is giving me a lot of
errors and I'm still trying to figure out how to make it run to the end
(or at least to a point where it's start to run some bcache commands).
In the meantime (as anticipated on IRC) I've uploaded a test kernel
reverting the patch "UBUNTU: SAUCE: (no-up) bcache: decouple emitting a
cached_dev CHANGE uevent":
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+1/
As we know, this would re-introduce the problem discussed in bug
1729145, but it'd be interesting to test it anyway, just to see if this
patch is somehow related to the bch_bucket_alloc() deadlock.
In addition to that I've spent some time looking at the last kernel
trace and the code. It looks like bch_bucket_alloc() is always releasing
the mutex &ca->set->bucket_lock when it goes to sleep (call to
schedule()), but it doesn't release bch_register_lock, that might be
also acquired. I was wondering if this could the reason of this
deadlock, so I've prepared an additional test kernel that does *not*
revert our "UBUNTU SAUCE" patch, but instead it releases the mutex
bch_register_lock when bch_bucket_alloc() goes to sleep:
https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+3/
Sorry for asking all these tests... if I can't find a way to reproduce
the bug on my side, asking you to test is the only way that I have to
debug this issue. :)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/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 1834875] Re: cloud-init growpart race with udev
(Oh, and thank you for that test run!) -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: In Progress Status in linux-azure package in Ubuntu: New Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev
Now one wrinkle about it being a linux-azure bug: if you _aren't_ seeing this on bionic but _were_ seeing it on cosmic, then there must be something else involved, because I believe (based on the publishing history[0]) that cosmic was on the same kernel version as bionic. This could, of course, still be a kernel bug that's just not hit by bionic's userspace. But, to be sure of where we stand, can you confirm the statement in the original report that this was an issue on cosmic? Do you have enough test history to determine when this started happening? [0] https://launchpad.net/ubuntu/+source/linux-meta-azure/+publishinghistory -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: In Progress Status in linux-azure package in Ubuntu: New Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Okay. Just burned that to USB and booted from USB live image (didn't install). Issue is still present :-( -- You 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 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-precise ** Tags removed: 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 -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty - phase: Testing - phase-changed: Monday, 22. July 2019 12:10 UTC + phase: Ready for Release + phase-changed: Friday, 02. August 2019 12:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - regression-testing: Stalled -- testing FAILED + promote-to-updates: Pending -- ready to copy variant: debs -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Release phase-changed: Friday, 02. August 2019 12:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron, > rtw88 is not working on 5.3-rc2 too. > right? That is correct. rtw88 is not working for me on 5.3-rc2 mainline kernel. I will try to build a kernel with wireless-drivers-next as suggested in #24. And for the time being I will add rtw88 to my /etc/modprobe.d/blacklist.conf and rebuild initrd when using kernels 5.0.0-21+ for disco dingo. Cheers, Jun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838245] Re: dkms script is missing function find_module
the proposed version not include the patch of "priority of OBSOLETE_BY
should higher than "force". #89 https://github.com/dell/dkms/issues/89";
, so I created another ppa [1] to test the regression only
my system installed kernel 4.15.0-1030-oem and 4.15.0-1045-oem and new dkms
from #10, then install the oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms, it
works as expected.
- for kernel 4.15.0-1030-oem, it checked the version of existed module.(line
4763 of my attached log)
- for kernel 4.15.0-1045-oem, it checked the OBSOLETE_BY.(line 9241 of my
attached log)
[1]:https://launchpad.net/~alextu/+archive/ubuntu/lp1838245-test-regression
** Attachment added: "install-ath10k.log"
https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/1838245/+attachment/5280511/+files/install-ath10k.log
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1838245
Title:
dkms script is missing function find_module
Status in DKMS:
In Progress
Status in dkms package in Ubuntu:
Confirmed
Status in dkms source package in Bionic:
Fix Committed
Bug description:
update for SRU process:
[Impact]
1. dkms script is missing function find_module
2. priority of OBSOLETE_BY should higher than "force". #89
https://github.com/dell/dkms/issues/89
[Test case]
install the dkms which already patched (also can be found in my ppa[1])
1. install a dkms which for a kernel module system already installed.
e.g. ath10k of my testing ppa : [1]
1.1. the dkms can be installed well.
2. install a dkms which has OBSOLETE_BY and FORCE
e.g.ath10k of my testing ppa : [1] (source code in [2])
- the target dkms defined OBSOLETE_BY and FORCE
- user install dkms on a system which installed kernel version less than
OBSOLETE_BY and another kernel higher than OBSOLETE_BY
- the dkms can be installed well.
[Regression potential]
medium as it touched the version sanity. This change correct the code logic
and land one more change from upstream as well.
The logic has been verified by #5 and me.
Building a kernel module using dkms in Linux Mint 19.1 shows the following
error:
Running module version sanity check.
/usr/sbin/dkms: Zeile 784: find_module: Befehl nicht gefunden
modinfo: ERROR: missing module or filename.
Checking the file the function is indeed missing and another user
confirmed, that it was removed at some point:
https://github.com/linuxmint/linuxmint/issues/142
Possible solution: Readd
find_module()
{
# tree = $1
# module = $2
find "$1" -name "$2$module_uncompressed_suffix" -o -name
"$2$module_suffix" -type f
return $?
}
as found in https://github.com/dell/dkms/blob/master/dkms
To manage notifications about this bug go to:
https://bugs.launchpad.net/dkms/+bug/1838245/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835189] Re: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -proposed tracker
3.13.0-172.223~12.04.1 - generic Regression test CMPL, RTB. Issue to note in amd64: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) Issue to note in i386: ubuntu_qrt_kernel_security - CONFIG_RETPOLINE=y in kernel (bug 1786894) ** Changed in: kernel-sru-workflow/regression-testing Status: Incomplete => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- 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/1835189 Title: precise/linux-lts-trusty: 3.13.0-172.223~12.04.1 -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: 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-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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 verification-testing series: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-trusty source package in Precise: 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 -- boot-testing-requested: true kernel-stable-master-bug: 1835190 packages: main: linux-lts-trusty meta: linux-meta-lts-trusty signed: linux-signed-lts-trusty phase: Ready for Release phase-changed: Friday, 02. August 2019 12:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic
On Moonshot ARM64, the test result is a bit unstable, sometimes it will pass within 2min, sometimes it will take 8, some even timeout with 30min threshold. I think it's better to just fix it for virtual env now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 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: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro 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.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834875] Re: cloud-init growpart race with udev
** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1834875 Title: cloud-init growpart race with udev Status in cloud-init: In Progress Status in linux-azure package in Ubuntu: New Bug description: On Azure, it happens regularly (20-30%), that cloud-init's growpart module fails to extend the partition to full size. Such as in this example: 2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', '--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', '/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True) 2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds 2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: init-network/config-growpart: FAIL: running config-growpart with frequency always 2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed 2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed Traceback (most recent call last): File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in _run_modules freq=freq) File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run return self._runners.run(name, functor, args, freq, clear_on_fail) File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run results = functor(*args) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 351, in handle func=resize_devices, args=(resizer, devices)) File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in log_time ret = func(*args, **kwargs) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 298, in resize_devices (old, new) = resizer.resize(disk, ptnum, blockdev) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 159, in resize return (before, get_size(partdev)) File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 198, in get_size fd = os.open(filename, os.O_RDONLY) FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3' @rcj suggested this is a race with udev. This seems to only happen on Cosmic and later. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817321] Re: installer does not support iSCSI iBFT
The feature documentation in the Server Guide has been published [1]. [1] https://help.ubuntu.com/lts/serverguide/advanced- installation.html#iscsi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817321 Title: installer does not support iSCSI iBFT Status in debian-installer package in Ubuntu: Fix Released Status in hw-detect package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in partman-iscsi package in Ubuntu: Fix Released Status in debian-installer source package in Bionic: Fix Released Status in hw-detect source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in partman-iscsi source package in Bionic: Fix Released Status in debian-installer source package in Cosmic: Fix Released Status in hw-detect source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in partman-iscsi source package in Cosmic: Fix Released Status in debian-installer source package in Disco: Fix Released Status in hw-detect source package in Disco: Fix Released Status in linux source package in Disco: Fix Released Status in partman-iscsi source package in Disco: Fix Released Status in debian-installer source package in Eoan: Fix Released Status in hw-detect source package in Eoan: Fix Released Status in linux source package in Eoan: Fix Released Status in partman-iscsi source package in Eoan: Fix Released Bug description: [Impact]  * It's not possible to access iBFT (iSCSI Boot Firmware Table) information    (settings for network interface, initiator, and target) in the installer    because the 'iscsi_ibft' module is not present in udeb packages.  * Even if it was, the installer does not handle iBFT information at all,    thus any settings are ignored, and iSCSI-related configuration has to    be done manually or with workarounds.  * This impacts user-experience and automatic installation on systems and    deployments which actually do provide the iBFT feature and information,    but cannot use it practically.  * With proper iBFT support in the installer (kernel module in udeb package    and automatic iSCSI-related configuration) users will be able to rely on    iBFT to install/deploy Ubuntu on their servers and datacenters.  * These fixes add the 'iscsi_ibft' kernel module in the scsi-modules udeb,    and configure network/iSCSI according to iBFT information in disk-detect.    This is done in disk-detect so that the iSCSI LUNs are detected as disks    (useful in case of no other disks in the system so the installer doesn't    complain nor wait too long) and that any partman-related preseed options    are not required and may be still available for the user. [Test Case]  * linux package / kernel module in udeb:    $ dpkg-deb -c scsi-modules_*.udeb | grep iscsi_ibft.ko    Check the module loads in the installer environment.    See comment with example for disco.  * d-i/hw-detect/partman-iscsi package:    See comments 11, 12, 13. [Regression Potential]  * linux package: low, the kernel module is not loaded by default,    and only checks whether iBFT information is present in firmware,    then exposes that in sysfs in read-only mode.  * d-i/hw-detect/partman-iscsi:    - d-i: kernel version update to include iscsi_ibft module,   based on kernel released to -updates plus one week   monitoring bug reports -- it should be OK.   Tested on amd64/i386/arm64/ppc64el on QEMU, plus amd64   on baremetal -- see comment 11.    - hw-detect: low, the changes are enabled by a preseed option. see comment 12.    - partman-iscsi: low, simple changes, plus one fix that has been tested in detail, and falls back to previous behavior if it fails. see comment 13. [Other Info]  * This has been verified both by the developer with a simple iSCSI    iBFT environment (2 VMs: iSCSI target & initiator with UEFI+iPXE)    and by an user with system/firmware that supports iBFT for iSCSI. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1817321/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Jun: Yes, r8822be will be removed in latest kernel. That's why we need to fix the issue on rtw88. rtw88 is not working on 5.3-rc2 too. right? I can not reproduce this issue with b822 wifi card on AMD. Let me check logs first, you can try to build wireless-drivers-next in comment #24 too. I suggest Blacklist rtw88 as a workaround for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
btw I can confirm that viot's workaround in #19 does indeed work on 5.0.0-23-generic which was released from the disco dingo repos yesterday. Jun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Please compile a kernel latest wireless-drivers as the following: $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git $ cd wireless-drivers-next $ yes '' | make localmodconfig $ make -j`nproc` && make -j`nproc` modules && sudo make INSTALL_MOD_STRIP=1 modules_install && sudo make install -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron~ I removed r8822be from the blacklist, rebuilt the mainline kernel with sudo update-initramfs -u -k 5.3.0-050300rc2-generic and rebooted. What is interesting is that in mainline, r8822be is not loaded at all! I have attached journalctl -b0. In future kernels, will the Realtek 8822be card use the rtw88 kernel module? Cheers, Jun output of lsmod below Module Size Used by rfcomm 81920 4 xt_CHECKSUM16384 1 iptable_mangle 16384 1 bridge176128 0 stp16384 1 bridge llc16384 2 bridge,stp ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter cmac 16384 1 overlay 114688 0 bnep 24576 2 binfmt_misc24576 1 nls_iso8859_1 16384 1 snd_hda_codec_realtek 114688 1 snd_hda_codec_generic81920 1 snd_hda_codec_realtek ledtrig_audio 16384 2 snd_hda_codec_generic,snd_hda_codec_realtek snd_hda_codec_hdmi 61440 1 snd_hda_intel 49152 5 snd_hda_codec 131072 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek snd_usb_audio 241664 2 snd_hda_core 90112 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek snd_usbmidi_lib36864 1 snd_usb_audio uvcvideo 98304 0 snd_hwdep 20480 2 snd_usb_audio,snd_hda_codec btusb 57344 0 snd_seq_midi 20480 0 snd_seq_midi_event 16384 1 snd_seq_midi btrtl 20480 1 btusb videobuf2_vmalloc 20480 1 uvcvideo btbcm 16384 1 btusb videobuf2_memops 20480 1 videobuf2_vmalloc snd_rawmidi36864 2 snd_seq_midi,snd_usbmidi_lib btintel24576 1 btusb videobuf2_v4l2 24576 1 uvcvideo videobuf2_common 53248 2 videobuf2_v4l2,uvcvideo bluetooth 577536 31 btrtl,btintel,btbcm,bnep,btusb,rfcomm rtwpci 24576 0 snd_seq69632 2 snd_seq_midi,snd_seq_midi_event rtw88 442368 1 rtwpci snd_pcm 106496 5 snd_hda_codec_hdmi,snd_hda_intel,snd_usb_audio,snd_hda_codec,snd_hda_core edac_mce_amd 32768 0 videodev 208896 3 videobuf2_v4l2,uvcvideo,videobuf2_common kvm_amd98304 0 snd_seq_device 16384 3 snd_seq,snd_seq_midi,snd_rawmidi mc 53248 5 videodev,snd_usb_audio,videobuf2_v4l2,uvcvideo,videobuf2_common input_leds 16384 0 ecdh_generic 16384 2 bluetooth joydev 24576 0 mac80211 847872 2 rtwpci,rtw88 snd_timer 36864 2 snd_seq,snd_pcm ecc28672 1 ecdh_generic snd86016 27 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_usb_audio,snd_usbmidi_lib,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm,snd_rawmidi kvm 647168 1 kvm_amd cfg80211 708608 2 mac80211,rtw88 irqbypass 16384 1 kvm asus_nb_wmi28672 0 wmi_bmof 16384 0 hid_multitouch 28672 0 k10temp16384 0 ccp94208 7 kvm_amd soundcore 16384 1 snd libarc416384 1 mac80211 mac_hid16384 0 asus_wireless 20480 0 ip6t_REJECT16384 1 nf_reject_ipv6 20480 1 ip6t_REJECT nf_log_ipv616384 4 xt_hl 16384 22 ip6t_rt20480 3 ipt_REJECT 16384 3 nf_reject_ipv4 16384 1 ipt_REJECT nf_log_ipv416384 4 nf_log_common 16384 2 nf_log_ipv4,nf_log_ipv6 xt_LOG 20480 8 xt_limit 16384 11 xt_tcpudp 20480 43 xt_addrtype16384 4 xt_MASQUERADE 20480 4 iptable_nat16384 1 sch_fq_codel 20480 7 xt_conntrack 16384 21 ip6table_filter16384 1 ip6_tables 32768 53 ip6table_filter nf_conntrack_netbios_ns16384 0 nf_conntrack_broadcast16384 1 nf_conntrack_netbios_ns nfsd 380928 13 nf_nat_ftp 20480 0 nf_nat 40960 3 nf_nat_ftp,iptable_nat,xt_MASQUERADE nf_conntrack_ftp 24576 1 nf_nat_ftp nf_conntrack 139264 7 xt_conntrack,nf_nat,nf_nat_ftp,nf_conntrack_netbios_ns,nf_conntrack_broadcast,nf_conntrack_ftp,xt_MASQUERADE auth_rpcgss94208 1 nfsd nf_defrag_ipv6 24576 1 nf_conntrack nf_defrag_ipv4 16384 1 nf_conntrack nfs_acl16384 1 nfsd parport_pc 40960 0 lockd 102400 1 nfsd iptable_filter 16384 1 ppdev 24576 0 bpfilter 32768 0 grace 16384 2 nfsd,lockd lp 20480 0 s
[Kernel-packages] [Bug 1787857] Re: USB mouse cursor lags after random time of correct behaviour
It's already in Ubuntu Studio daily image. -- You 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 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron~ I downloaded the mainline kernel 5.3.0 from the ppa you provided and installed as follows: wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux- headers-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux- image- unsigned-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb wget https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3-rc2/linux- modules-5.3.0-050300rc2-generic_5.3.0-050300rc2.201907281631_amd64.deb sudo dpkg -i *.deb I left my blacklist.conf unchanged (r8822be blacklisted, rtwpci not blacklisted). I rebooted and selected the mainline kernel from GRUB and added the rtw88.debug_mask=0x3ff linux cmdline option. But with r8822be blacklisted, wifi does not work even on mainline 5.3.0. I have attached the output from journalctl -b0. Here are the realtek kernel modules that are loaded: junbuntu@pj:~$ lsmod | grep rtw rtwpci 24576 0 rtw88 442368 1 rtwpci mac80211 847872 2 rtwpci,rtw88 cfg80211 708608 2 mac80211,rtw88 Should I try again but this time remove r8822be from blacklist.conf (and also do not blacklist rtwpci)? Best, Jun ** Attachment added: "journalctl -b0 output on mainline 5.3.0 kernel with r8822be blacklisted" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+attachment/5280508/+files/rtwpci_rtw88_mainline_5.3.0_journalctl_b0.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/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786894] Re: test_265_config_retpoline in kernel_security_test failed on 3.13 Precise
** Tags added: sru-20190701 ubuntu-qrt-kernel-security
** Tags added: 3.13
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1786894
Title:
test_265_config_retpoline in kernel_security_test failed on 3.13
Precise
Status in QA Regression Testing:
Confirmed
Status in ubuntu-kernel-tests:
Confirmed
Status in linux package in Ubuntu:
Triaged
Bug description:
== Justification ==
In the Precise 3.13 kernel, the CONFIG_RETPOLINE was set to y in commit
eae992be4, which should be disabled to meet the security team's requirement.
==
 FAIL: test_265_config_retpoline (__main__.KernelSecurityConfigTest)
 Ensure retpoline configuration option is set
 --
 Traceback (most recent call last):
 File "./test-kernel-security.py", line 2445, in test_265_config_retpoline
 self.assertKernelConfig('RETPOLINE', expected)
 File "./test-kernel-security.py", line 209, in assertKernelConfig
 self.assertKernelConfigUnset(name)
 File "./test-kernel-security.py", line 200, in assertKernelConfigUnset
 '%s option was expected to be unset in the kernel config' % name)
 AssertionError: RETPOLINE option was expected to be unset in the kernel
config
In this test case, this config was expected to be NOT set:
elif self.lsb_release['Release'] == 12.04:
self._skipped("RETPOLINE compiler not in precise")
expected = False
self.assertKernelConfig('RETPOLINE', expected)
== Fix ==
[Precise/lts-backport-trusty][SRU][PATCHv2] Revert "UBUNTU: [Config]
CONFIG_RETPOLINE=y"
== Test ==
The test_265_config_retpoline will pass after disabling CONFIG_RETPOLINE
== Regression Potential ==
Minimal.
No code changes, just a config changes.
To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1786894/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Aaron~ I have attached the debug info you requested for #16. This time I re-blacklisted r8822be driver in blacklist.conf and removed rtwpci from blacklist.conf, rebuilt initrd, rebooted, and used the rtw88.debug_mask=0x3ff option in linux cmdline in GRUB. As expected, wifi is not working when only rtw88 driver is active (and r8822be is inactive). Next I will try with the mainline kernel. Thanks, Jun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
This issue still persists.Mine is an Hp laptop with an Intel Bay Trail processor, Intel HD graphics(Not Nvidia), 8GB RAM with Dual boot Windows and Ubuntu 16.04.2. Bios version F.46 and kernel version 4.15.0-55-generic Whenever I try to SHUTDOWN/RESTART/SLEEP the Screen goes off(Black) but the Hard Disk keeps spinning with power button light ON. sometimes while doing shutdown the screen hangs on Ubuntu logo with dots. when esc is pressed it's seen that after [OK] Reached Target Shutdown nothing happens cursor blinking or Freeze. I tried to Re-install ubuntu with 16.04.6 while installing it displayed error related to APCI. somehow it got installed and when I checked dmesg it showed this error message "ACPI Error: [\_PR_.CPU0._PPC] Namespace lookup failure, AE_NOT_FOUND (20170831/psargs-364)" and this "ACPI Error: Method parse/execution failed \_SB.PCI0.LPCB.EC0.IPCL, AE_NOT_FOUND (20170831/psparse-550)" I tried almost everything I found on internet acpi=force, acpi=off and other stuff. It's discouraging from 2016 to 2019 there is still no permanent fix for this issue. some people on internet tried some or other fix for some it worked for some it didn't. Did anyone one of you found the fix for this ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1804577] Re: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS
The same bug affects me as well. MainBoard: Gigabyte AB350-Gaming-CF CPU: Amd Ryzen 5 2400G Kernel: 5.1.15-050115-generic (updated via UKUU). lshw attached. [Fri Aug 2 09:44:25 2019] ACPI: Added _OSI(Processor Aggregator Device) [Fri Aug 2 09:44:25 2019] ACPI: Added _OSI(Linux-Dell-Video) [Fri Aug 2 09:44:25 2019] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [Fri Aug 2 09:44:25 2019] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) [Fri Aug 2 09:44:25 2019] ACPI BIOS Error (bug): Failure creating named object [\_SB.SMIC], AE_ALREADY_EXISTS (20190215/dswload2-324) [Fri Aug 2 09:44:25 2019] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20190215/psobject-221) [Fri Aug 2 09:44:25 2019] ACPI BIOS Error (bug): Failure creating named object [\_SB.SMIB], AE_ALREADY_EXISTS (20190215/dsfield-633) [Fri Aug 2 09:44:25 2019] ACPI: 8 ACPI AML tables successfully acquired and loaded [Fri Aug 2 09:44:25 2019] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [Fri Aug 2 09:44:25 2019] ACPI: Interpreter enabled [Fri Aug 2 09:44:25 2019] ACPI: (supports S0 S3 S4 S5) [Fri Aug 2 09:44:25 2019] ACPI: Using IOAPIC for interrupt routing [Fri Aug 2 09:44:25 2019] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [Fri Aug 2 09:44:25 2019] ACPI: Enabled 2 GPEs in block 00 to 1F [Fri Aug 2 09:44:25 2019] ACPI: Power Resource [P0ST] (on) [Fri Aug 2 09:44:25 2019] ACPI: Power Resource [P3ST] (on) [Fri Aug 2 09:44:25 2019] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [Fri Aug 2 09:44:25 2019] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [Fri Aug 2 09:44:25 2019] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [Fri Aug 2 09:44:25 2019] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [Fri Aug 2 09:44:25 2019] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge [Fri Aug 2 09:44:25 2019] PCI host bridge to bus :00 ** Attachment added: "lshw.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+attachment/5280506/+files/lshw.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/1804577 Title: ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS Status in linux package in Ubuntu: Confirmed Bug description: I`m using Ubuntu 18.10 on my B350M GAMING PRO motherboard and AMD 2400G CPU. See some error in dmesg. Hope a fix in the upcoming update. Linux version 4.18.0-10-generic [0.076193] ACPI: Added _OSI(Module Device) [0.076193] ACPI: Added _OSI(Processor Device) [0.076194] ACPI: Added _OSI(3.0 _SCP Extensions) [0.076194] ACPI: Added _OSI(Processor Aggregator Device) [0.076195] ACPI: Added _OSI(Linux-Dell-Video) [0.076196] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) [0.086490] ACPI BIOS Error (bug): Failure creating [\_SB.SMIC], AE_ALREADY_EXISTS (20180531/dswload2-316) [0.086497] ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20180531/psobject-221) [0.086501] ACPI BIOS Error (bug): Failure creating [\_SB.SMIB], AE_ALREADY_EXISTS (20180531/dsfield-594) [0.086582] ACPI: 8 ACPI AML tables successfully acquired and loaded [0.088710] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [0.090528] ACPI: Interpreter enabled [0.090541] ACPI: (supports S0 S3 S4 S5) [0.090542] ACPI: Using IOAPIC for interrupt routing [0.090886] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.091196] ACPI: Enabled 2 GPEs in block 00 to 1F [0.093761] ACPI: Power Resource [P0ST] (on) [0.093793] ACPI: Power Resource [P3ST] (on) [0.100120] ACPI: PCI Root Bridge [PCI0] (domain [bus 00-ff]) [0.100125] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI] [0.100360] acpi PNP0A08:00: _OSC: platform does not support [SHPCHotplug LTR] [0.100583] acpi PNP0A08:00: _OSC: OS now controls [PCIeHotplug PME AER PCIeCapability] [0.100596] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain [bus 00-3f] only partially covers this bridge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804577/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837608] Re: bionic/linux-gcp: 4.15.0-1038.40 -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 1837605 (xenial/linux-gcp) derivatives: bug 1837601 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 29. July 2019 12:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1837601 xenial/linux-gcp: bug 1837605 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1837608 Title: bionic/linux-gcp: 4.15.0-1038.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1837605 (xenial/linux-gcp) derivatives: bug 1837601 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 29. July 2019 12:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1837601 xenial/linux-gcp: bug 1837605 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837608] Re: bionic/linux-gcp: 4.15.0-1038.40 -proposed tracker
4.15.0-1038.40 - gcp Regression test CMPL, RTB. Issue to note in gcp: tsc - failed to build (bug 1831584) ubuntu_kvm_unit_tests - failed due to no KVM support ubuntu_ltp - proc01 (bug 1829849) binfmt_misc02 (bug 1822246) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) memcg_test_3 (bug 1836694) cgroup_fj_* failure caused by memcg_test_3 (bug 1836694) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ltp_acpi (bug 1829982) ubuntu_ltp_syscalls - fanotify09-2 (bug 1804594) msgstress03 (bug 1797341) sync_file_range02 (bug 1819116) Skipped / blacklisted: * libhugetlbfs * ubuntu_seccomp ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) ** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1837608 Title: bionic/linux-gcp: 4.15.0-1038.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 backports: bug 1837605 (xenial/linux-gcp) derivatives: bug 1837601 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1837626 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 29. July 2019 12:24 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1837601 xenial/linux-gcp: bug 1837605 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1837608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
I can confirm that the problem is present on the 7th Generation X1 Carbon as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modal
[Kernel-packages] [Bug 1836694] Re: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic
This issue could be found on B-gcp as well. But set the LTP_TIMEOUT_MUL to 3 can make it pass. It tooks: real8m50.670s user1m54.287s sys 4m39.889s On GCP, so LTP_TIMEOUT_MUL=3 is quite enough. Next is to see if this fix works for Moonshot ARM64. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836694 Title: memcg_test_3 from controllers in LTP failed on Moonshot ARM64 with Bionic Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: This failure could be found in the LTP test suite on a Moonshot ARM64 node with B-4.15, but sometimes it will pass if you try to run it manually. (Sometimes not.) <<>> tag=memcg_test_3 stime=1563249678 cmdline="memcg_test_3" contacts="" analysis=exit <<>> incrementing stop tst_test.c:1100: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! tst_test.c:1140: INFO: If you are running on slow machine, try exporting LTP_TIMEOUT_MUL > 1 tst_test.c:1141: BROK: Test killed! (timeout?) Summary: passed 0 failed 0 skipped 0 warnings 0 tst_tmpdir.c:330: WARN: tst_rmdir: rmobj(/tmp/ltp-nJ05WiJDR1/06EzUc) failed: unlink(/tmp/ltp-nJ05WiJDR1/06EzUc/memcg/cgroup.clone_children) failed; errno=1: EPERM <<>> When it fails, the attempt to remove files will fail, and most of the cgroup_fj_* test will fail: * cgroup_fj_function_memory * cgroup_fj_stress_memory_10_3_each * cgroup_fj_stress_memory_10_3_none * cgroup_fj_stress_memory_10_3_one * cgroup_fj_stress_memory_1_200_each * cgroup_fj_stress_memory_1_200_none * cgroup_fj_stress_memory_1_200_one * cgroup_fj_stress_memory_200_1_each * cgroup_fj_stress_memory_200_1_none * cgroup_fj_stress_memory_200_1_one * cgroup_fj_stress_memory_2_2_each * cgroup_fj_stress_memory_2_2_none * cgroup_fj_stress_memory_2_2_one * cgroup_fj_stress_memory_2_9_each * cgroup_fj_stress_memory_2_9_none * cgroup_fj_stress_memory_2_9_one * cgroup_fj_stress_memory_3_3_each * cgroup_fj_stress_memory_3_3_none * cgroup_fj_stress_memory_3_3_one * cgroup_fj_stress_memory_4_4_each * cgroup_fj_stress_memory_4_4_none * cgroup_fj_stress_memory_4_4_one Steps to run this: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "memcg_test_3memcg_test_3" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-54-generic 4.15.0-54.58 ProcVersionSignature: User Name 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 16 03:46 seq crw-rw 1 root audio 116, 33 Jul 16 03:46 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: arm64 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: Tue Jul 16 04:16:14 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro 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.8 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
Hi Viot and George: Could you try mainline build kernel[1]? I didn't reproduce this issue on both AMD and Intel platform. [1] https://kernel.ubuntu.com/~kernel-ppa/mainline/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/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838133] Re: realtek r8822be kernel module fails after update to linux kernel-headers 5.0.0-21
I propose a workaround (which is not very elegant) When you are using a kernel 5.0.0.21 or higher sudo modprobe -r r8822be rtwpci sudo modprobe r8822be rtwpci In this case, you recover the wifi and if you type lspci -nnk | grep 0280 -A3 you will see 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950] Kernel driver in use: r8822be Kernel modules: rtwpci, r8822be If you try the same command before this trick I obtain Kernel driver in use: rtw_pci By changing the loading order of the modules, the wifi works again. IF you know a more elegant way to load the modules, I am very interested -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838133 Title: realtek r8822be kernel module fails after update to linux kernel- headers 5.0.0-21 Status in linux package in Ubuntu: Triaged Bug description: On July 24th I upgraded to the latest linux-headers-5.0.0-21 as part of the dist-upgrade for latest packages in Disco Dingo 19.04. I didn't notice that wifi was no longer working because at work I exclusively use a wired Ethernet connection. Today, however, when I tried to use my realtek r8822be wireless card, I discovered that it was totally unresponsive and did not work with wpa_supplicant / wpa_cli even when invoked manually from the command line (let alone with NetworkManager). When the problem occurred, I was using 19.04's latest kernel 5.0.0-21. I then rebooted and selected kernel 5.0.0-20 from GRUB menu. "uname -a" shows that I am using the previous kernel version: Linux pj 5.0.0-20-generic #21-Ubuntu SMP Mon Jun 24 09:32:09 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux With this kernel version as well as linux-headers-5.0.0.20, linux- headers-5.0.0-20-generic, my realtek wireless card works fine. While booted into 5.0.0-20 kernel, here are the realtek kernel modules that are loaded: # lsmod | grep r8 r8822be 692224 0 mac80211 806912 1 r8822be cfg80211 671744 2 mac80211,r8822be r8169 81920 0 Hopefully this realtek wireless regression can get fixed in the next minor kernel version. Let me know if you need any more information. Best Regards, Jun To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
@kaihengfeng - How do I find and install that Kernel? Sorry, I'm used to just using the gui and command line tools to upgrade, not sure how I find and install that kernel manually. I am used to using apt for installing general packages, just this scenario is new to me and I can't find any instructions on google. -- You 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 1838678] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280493/+files/RfKill.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280495/+files/WifiSyslog.txt ** Attachment removed: "WifiSyslog.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+attachment/5280495/+files/WifiSyslog.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280491/+files/ProcModules.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280494/+files/UdevDb.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280492/+files/PulseList.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280490/+files/ProcInterrupts.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280486/+files/Lsusb.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb InstallationDate: Installed on 2018-08-09 (357 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Latitude E6540 Package: linux (not installed) ProcFB: 0 inteldrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.173.9 Tags: bionic Uname: Linux 4.18.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/18/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 0725FP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6540 dmi.product.sku: Latitude E6540 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838678/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838678] Re: radeon kernel driver fails to resume from suspend
apport information ** Tags added: apport-collected bionic ** Description changed: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x850C)=0x) [drm:atom_op_jump [radeon]] *ERROR* atombios stuck in loop for more than 5secs aborting [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing CF1C (len 62, WS 0, PS 0) @ 0xCF38 [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B67E (len 236, WS 4, PS 0) @ 0xB74B [drm:atom_execute_table_locked [radeon]] *ERROR* atombios stuck executing B5DC (len 74, WS 0, PS 8) @ 0xB5E4 [drm:si_dpm_enable [radeon]] *ERROR* si_init_smc_table failed [drm:radeon_pm_resume [radeon]] *ERROR* radeon: dpm resume failed The error messages are also shown on connected projectors which is slightly annoying. Mostly, after a minute or two the system resumes successfully with the window manager starting and all applications still running. However, after more and more suspend/resume cycles the resume process takes longer and sometimes X11 will crash so that a new session has to be started. Best regards, Thomas + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.7 + Architecture: amd64 + CurrentDesktop: KDE + DistroRelease: Ubuntu 18.04 + HibernationDevice: RESUME=UUID=255880d2-46ce-4ad0-ae40-cbe8d6448bcb + InstallationDate: Installed on 2018-08-09 (357 days ago) + InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + MachineType: Dell Inc. Latitude E6540 + Package: linux (not installed) + ProcFB: + 0 inteldrmfb + 1 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-25-generic root=UUID=6c1fe528-1808-4de4-8d6e-be8d7e796823 ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20 + RelatedPackageVersions: + linux-restricted-modules-4.18.0-25-generic N/A + linux-backports-modules-4.18.0-25-generic N/A + linux-firmware 1.173.9 + Tags: bionic + Uname: Linux 4.18.0-25-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 02/18/2014 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A08 + dmi.board.name: 0725FP + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA08:bd02/18/2014:svnDellInc.:pnLatitudeE6540:pvr01:rvnDellInc.:rn0725FP:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6540 + dmi.product.sku: Latitude E6540 + dmi.product.version: 01 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1838678/+attachment/5280480/+files/AlsaInfo.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/1838678 Title: radeon kernel driver fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Hello everybody, I'm using a laptop which is a Dell Latitude E6540 with hybrid graphics: 00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Mars XTX [Radeon HD 8790M] (rev ff) The distribution is Ubuntu 18.04.2 LTS with HWE kernel 4.18.0-25-generic and HWE XServer packages. However, the problem described below showed up with the standard kernel as well. Kernel modules amdgpu, radeon, i915 are loaded. From time to time, I suspend the laptop and switch from using the laptop's primary display only to using one or more connected external displays/projectors and back. On resume, the window manager isn't started immediately. Instead, a lot of error messages are displayed on the console: radeon :01:00.0: failed VCE resume (-110). [drm:r600_ring_test [radeon]] *ERROR* r
