[Kernel-packages] [Bug 1877728] Re: [nouveau]system freeze when xorg starts up
[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/1877728 Title: [nouveau]system freeze when xorg starts up Status in linux package in Ubuntu: Expired Bug description: Thinkpad X1 Extreme Gen1 with GTX1050Ti MaxQ, BIOS v1.27 Fresh installed xubuntu 20.04, system freeze every time when lightdm starting up. In recovery mode, I found some error message about nouveau driver: [6.458677] kernel: iwlwifi :00:14.3: BIOS contains WGDS but no WRDS [6.488261] kernel: Lockdown: Xorg: raw io port access is restricted; see man kernel_lockdown.7 [6.661527] kernel: nouveau :01:00.0: bus: MMIO read of FAULT at 409800 [ TIMEOUT ] [8.660830] kernel: [ cut here ] [8.660831] kernel: nouveau :01:00.0: timeout [8.660879] kernel: WARNING: CPU: 11 PID: 1021 at drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:1727 gf100_gr_init_ctxctl_ext+0x37a/0x520 [nouveau] (See attachment 'dmesg.0' for the full dmesg) After add nouveau module to blacklist, the system starts up normally. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zh 2810 F pulseaudio /dev/snd/controlC0: zh 2810 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 18:14:24 2020 MachineType: LENOVO 20MFA002CD ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=4cceb104-7532-4fab-91c3-8f5a4989b1ed ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET45W (1.27 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MFA002CD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40675 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET45W(1.27):bd02/06/2020:svnLENOVO:pn20MFA002CD:pvrThinkPadX1Extreme:rvnLENOVO:rn20MFA002CD:rvrSDK0J40675WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MFA002CD dmi.product.sku: LENOVO_MT_20MF_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883386] Re: Navi RX 5700 XT - hardware cursor + vsync causes stutter in compositors, games and even the cursor itself
*** This bug is a duplicate of bug 1883387 *** https://bugs.launchpad.net/bugs/1883387 ** This bug has been marked a duplicate of bug 1883387 Navi RX 5700 XT - hardware cursor + vsync causes stutter in compositors, games and even the cursor itself -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883386 Title: Navi RX 5700 XT - hardware cursor + vsync causes stutter in compositors, games and even the cursor itself Status in linux package in Ubuntu: Confirmed Bug description: With AMD Navi RX 5600/5700 have stuttering in all accelerated applications. affected: kernels <5.7 This bug is fixed in kernel 5.7 version More details https://gitlab.freedesktop.org/drm/amd/-/issues/1001 Need backports for focal (20.04) release for kernel 5.4 or upgrade to kernel 5.7 Also I can't upgrade to 5.7 until zfs-dkms not support this kernel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-oem (not installed) ProcVersionSignature: Ubuntu 5.6.0-1011.11-oem 5.6.14 Uname: Linux 5.6.0-1011-oem x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rnz4328 F pulseaudio /dev/snd/controlC2: rnz4328 F pulseaudio /dev/snd/controlC0: rnz4328 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Jun 13 22:32:50 2020 InstallationDate: Installed on 2015-05-01 (1870 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1011-oem root=UUID=e4e7aa28-c520-4902-86a3-0de1cf7fc9da ro acpi_enforce_resources=lax amd_iommu=on iommu=pt iommu=1 RelatedPackageVersions: linux-restricted-modules-5.6.0-1011-oem N/A linux-backports-modules-5.6.0-1011-oem N/A linux-firmware 1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (32 days ago) dmi.bios.date: 03/06/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12f dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF12f:bd03/06/2020:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-10-26T22:19:16.074320 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888894] Re: Ubuntu 20.04:Wifi drops and speed is degarded periodically
Please run the following command in a terminal to collect logs (requires internet connection): apport-collect 194 ** Package changed: ubuntu => linux (Ubuntu) ** 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/194 Title: Ubuntu 20.04:Wifi drops and speed is degarded periodically Status in linux package in Ubuntu: Incomplete Bug description: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888894] [NEW] Ubuntu 20.04:Wifi drops and speed is degarded periodically
You have been subscribed to a public bug: Hello, For the past several months, I noticed my wifi just drops periodically. Disabling bluetooth reduces the frequency of this. Also Ive noticed speed is slower on wifi for my 02:00.0 Network controller: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter (rev 31). this problem affects others too. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bot-comment -- Ubuntu 20.04:Wifi drops and speed is degarded periodically https://bugs.launchpad.net/bugs/194 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888967] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888967 Title: Lubuntu Lubuntu 18.04 won't boot after applying updates on a 32-bit machine Status in linux package in Ubuntu: Confirmed Bug description: On a Dell Optiplex-gx260 computer, after applying updates, installing linux-image-4.15.0-112-generic, when restarting, the system doesn't boot, and instead ends up in 'rescue mode' (whatever that is). I'm reporting this on another Dell Optiplex machine (32-bit), because although the machine having the problem booted on the older kernel (4.15.0-109-generic), it would not stay alive long enough to report the problem. This machine (fortunately) is still using the 4.15.0-100-generic kernel, so it stays alive long enough to report the problem. I expected the machine to reboot after applying updates. Instead, it ended-up in a text-screen, saying it is in 'rescue mode'. I also attempted to do a fresh install of the latest Lubuntu 18.04 on a different Dell Optiplex GX-260 machine, and it also ended up in a text screen in 'rescue mode'. So I gave up on Lubuntu, and successfully installed Debian 10.4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-100.101-generic 4.15.18 Uname: Linux 4.15.0-100-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-100-generic. ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere 1083 F pulseaudio /dev/snd/controlC2: aere 1083 F pulseaudio Card0.Amixer.info: Card hw:0 'MPD218'/'Akai MPD218 at usb-:00:1d.3-1, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card0.Amixer.values: Card1.Amixer.info: Card hw:1 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sat Jul 25 18:26:13 2020 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2018-06-24 (762 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-100-generic root=UUID=5135b07f-63ee-4502-8ab7-849bb4d17497 ro quiet splash nopti RelatedPackageVersions: linux-restricted-modules-4.15.0-100-generic N/A linux-backports-modules-4.15.0-100-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888967] [NEW] Lubuntu Lubuntu 18.04 won't boot after applying updates on a 32-bit machine
Public bug reported: On a Dell Optiplex-gx260 computer, after applying updates, installing linux-image-4.15.0-112-generic, when restarting, the system doesn't boot, and instead ends up in 'rescue mode' (whatever that is). I'm reporting this on another Dell Optiplex machine (32-bit), because although the machine having the problem booted on the older kernel (4.15.0-109-generic), it would not stay alive long enough to report the problem. This machine (fortunately) is still using the 4.15.0-100-generic kernel, so it stays alive long enough to report the problem. I expected the machine to reboot after applying updates. Instead, it ended-up in a text-screen, saying it is in 'rescue mode'. I also attempted to do a fresh install of the latest Lubuntu 18.04 on a different Dell Optiplex GX-260 machine, and it also ended up in a text screen in 'rescue mode'. So I gave up on Lubuntu, and successfully installed Debian 10.4. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-112-generic 4.15.0-112.113 ProcVersionSignature: Ubuntu 4.15.0-100.101-generic 4.15.18 Uname: Linux 4.15.0-100-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-100-generic. ApportVersion: 2.20.9-0ubuntu7.15 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: aere 1083 F pulseaudio /dev/snd/controlC2: aere 1083 F pulseaudio Card0.Amixer.info: Card hw:0 'MPD218'/'Akai MPD218 at usb-:00:1d.3-1, full speed' Mixer name : 'USB Mixer' Components : 'USB09e8:0034' Controls : 0 Simple ctrls : 0 Card0.Amixer.values: Card1.Amixer.info: Card hw:1 'Interface'/'M-Audio USB Uno MIDI Interface at usb-:00:1d.2-2, full speed' Mixer name : 'USB Mixer' Components : 'USB0763:0150' Controls : 0 Simple ctrls : 0 Card1.Amixer.values: Card2.Amixer.info: Card hw:2 'Live'/'SB Live! 5.1 (rev.7, serial:0x80641102) at 0xdf20, irq 18' Mixer name : 'SigmaTel STAC9708,11' Components : 'AC97a:83847608' Controls : 225 Simple ctrls : 45 Card3.Amixer.info: Card hw:3 'ICH5'/'Intel ICH5 with AD1981B at irq 17' Mixer name : 'Analog Devices AD1981B' Components : 'AC97a:41445374' Controls : 27 Simple ctrls : 19 CurrentDesktop: LXDE Date: Sat Jul 25 18:26:13 2020 HibernationDevice: RESUME=UUID=254efefa-b824-4c7b-ae5c-dcf19ed85430 InstallationDate: Installed on 2018-06-24 (762 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release i386 (20180426) MachineType: Dell Computer Corporation OptiPlex GX270 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-100-generic root=UUID=5135b07f-63ee-4502-8ab7-849bb4d17497 ro quiet splash nopti RelatedPackageVersions: linux-restricted-modules-4.15.0-100-generic N/A linux-backports-modules-4.15.0-100-generic N/A linux-firmware 1.173.19 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2006 dmi.bios.vendor: Dell Computer Corporation dmi.bios.version: A07 dmi.board.name: 0U1325 dmi.board.vendor: Dell Computer Corp. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Computer Corporation dmi.modalias: dmi:bvnDellComputerCorporation:bvrA07:bd06/26/2006:svnDellComputerCorporation:pnOptiPlexGX270:pvr:rvnDellComputerCorp.:rn0U1325:rvr:cvnDellComputerCorporation:ct6:cvr: dmi.product.name: OptiPlex GX270 dmi.sys.vendor: Dell Computer Corporation ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bionic i386 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888967 Title: Lubuntu Lubuntu 18.04 won't boot after applying updates on a 32-bit machine Status in linux package in Ubuntu: New Bug description: On a Dell Optiplex-gx260 computer, after applying updates, installing linux-image-4.15.0-112-generic, when restarting, the system doesn't boot, and instead ends up in 'rescue mode' (whatever that is). I'm reporting this on another Dell Optiplex machine (32-bit), because although the machine having the problem booted on the older kernel (4.15.0-109-generic), it would not stay alive long enough to report the problem. This machine (fortunately) is still using the 4.15.0-100-generic kernel, so it stays alive long enough to report the problem. I expected the machine to reboot after applying updates. Instead, it ended-up in a text-screen, saying it is in 'rescue mode'. I also attempted to do a fresh install of the latest Lubuntu 18.04 on a different Dell Optiplex GX-260 machine, and it also ended up in a text screen in 'rescue mode'. So I gave up on Lubuntu, and successfully installed Debian 10.4. ProblemType: Bug DistroRelease: Ubuntu 18.04
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
Seriously, thank you so much for this!! I don't believe such a breaking change got through however thanks for the swift fix!! (I got on the internet via bluetooth tethering) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: Triaged Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8
[Kernel-packages] [Bug 1884133] Re: Micro SD card not discovered (O2 Micro, Inc. SD/MMC Card Reader)
Hi, I stumbled on the same(?) error. 32 GB SDHC, Lenovo L480, Ubuntu 20.04.1 LTS SD card newly bought for a simple device, so no manufacturer know. But it works with a USB card reader. Please find the log file attached. Thanks for the support! CU ** Attachment added: "journal.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884133/+attachment/5395784/+files/journal.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884133 Title: Micro SD card not discovered (O2 Micro, Inc. SD/MMC Card Reader) Status in linux package in Ubuntu: Incomplete Bug description: Hi, Ubuntu 20.04 fails to discover a micro SD card inserted into the "O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01)". I currently have no other card available for testing, but the one I have tested with is a Lexar 32 GB 633x microSDHC UHS-I, according to the packaging. It works well in a digital camera. I tried intstalling exfat-fuse and exfat-utils - that didn't cut it. Thanks! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steinarne 1562 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jun 18 20:34:15 2020 GvfsMonitorError: This tool has been deprecated, use 'gio mount' instead. See 'gio help mount' for more info. GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit. HotplugNewDevices: HotplugNewMounts: InstallationDate: Installed on 2019-08-08 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20LS0017MX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=12011978-2f19-446b-afb7-6b82d2459023 ro quiet splash psmouse.elantech_smbus=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux Symptom: storage UdevMonitorLog: monitor will print the received events for: UDEV - the event which udev sends out after rule processing UdisksMonitorLog: Monitoring the udisks daemon. Press Ctrl+C to exit. 20:34:46.361: The udisks-daemon is running (name-owner :1.9). UpgradeStatus: Upgraded to focal on 2020-04-13 (66 days ago) dmi.bios.date: 05/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET56W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS0017MX 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.modalias: dmi:bvnLENOVO:bvrR0QET56W(1.33):bd05/05/2019:svnLENOVO:pn20LS0017MX:pvrThinkPadL480:rvnLENOVO:rn20LS0017MX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS0017MX dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884133/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
As long as no solution is found, here is another solution. https://gitlab.manjaro.org/packages/community/lenopow Since it is only a script, this should work in every distribution ;-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Just repeat again - the fix works where an incorrect driver is detected. However, no driver is found at all for the LEGION 5 and the touchpad is therefore not activated. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
These are my latest LOG files https://linux-hardware.org/?probe=27a5d47256 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Thanks Helmut and Ben. These are very precise information and better than any post elsewhere. I got no reply from the email contacts provided by Kai-Heng yet... Anyone with a Lenovo connection ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Nicolas -- I've seen the R7000 Chinese post (https://www.cnblogs.com/mikeguan/p/13126497.html), and what it basically entails is blacklisting hid_multitouch (or disabling it in the kernel and recompiling), which according to other forums seems to have an effect on some touchpads, but has no effect on the MSFT0001:00 04F3:3140 touchpad we have. I attempted his suggestions anyways, and saw the same lack of results -- the touchpad remained dead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05:
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Is part of the issue here that some (most) initramfs-tools created images have an uncompressed early CPU microcode firmware prefixed ? That is stored as ASCII CPIO which is why Con see's that reported by 'file' since that tool checks the magic signatures at start of a file. binwalk reveals more detail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
Given that https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939 has been marked as duplicate of this issue (when it was meant to be about the fact that the grub menu doesn't provide any non-broken kernel to boot from, as all are affected by this issue): While the core issue gets investigated and fixed, it is URGENT that an earlier, non-broken kernel is made readily available to simple human beinig like me that just need to use their computer. I wonder how this hasn't been already done given this issue has been known for at least a year. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
oops false post 72 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic
[Kernel-packages] [Bug 1888948] Re: AMD Oland : failed VCE resume (-110)
Solved, failed resume is part of Oland chipset ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1888948 Title: AMD Oland : failed VCE resume (-110) Status in linux-firmware package in Ubuntu: Invalid Bug description: On fresh Ubuntu Fossa Install, I have no hardware video decoding available. I had same error here on bionic, and was solved : https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130 (version 173.17), 173.18 and 173.19 are broken too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1888948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888939] Re: No available stable kernel to boot from
*** This bug is a duplicate of bug 1848771 *** https://bugs.launchpad.net/bugs/1848771 ** This bug has been marked a duplicate of bug 1848771 Reboot after resume from suspend (deep) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888939 Title: No available stable kernel to boot from Status in linux package in Ubuntu: New Bug description: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888939] Re: Unable to boot with 3.19.0.43-generic
Well then the issue is that tehre is no stable kernel I can boot from! Kernels starting from 5.1 suffer from bug 1848771 and are therefore unusable. ** Summary changed: - Unable to boot with 3.19.0.43-generic + No available stable kernel to boot from ** Changed in: linux (Ubuntu) Status: Invalid => 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/1888939 Title: No available stable kernel to boot from Status in linux package in Ubuntu: New Bug description: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888950] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888950 Title: Touchpad doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I just reinstalled kubuntu and while using my laptop my touchpad stopped working. I restarted my computer and now the touchpad doesn't show up at all and doesn't work. I followed the instructions here https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 and the instructions say to file a bug since I don't see a synaptics touchpad entry in /proc/bus/input/devices. As instructed, I will also attach that file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jul 25 10:33:04 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KH002RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a844f512-56a4-4f99-a77e-b86a753812f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH002RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH002RUS:pvrThinkPadX1Carbon:rvnLENOVO:rn20KH002RUS:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 20KH002RUS dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I am a Manjaro developer and we have kernels 4.4 / 4.9 / 4.14 / 4.19 / 5.4 / 5.7 / 5.8 The touchpad doesn't work with one of the kernels. Screen brightness only works with AMD- or nouveau-Driver, not with the proprietary driver, like 440.100 The brightness display works, but nothing changes. . -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5
[Kernel-packages] [Bug 1888950] [NEW] Touchpad doesn't work
Public bug reported: I just reinstalled kubuntu and while using my laptop my touchpad stopped working. I restarted my computer and now the touchpad doesn't show up at all and doesn't work. I followed the instructions here https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 and the instructions say to file a bug since I don't see a synaptics touchpad entry in /proc/bus/input/devices. As instructed, I will also attach that file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jul 25 10:33:04 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KH002RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a844f512-56a4-4f99-a77e-b86a753812f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH002RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH002RUS:pvrThinkPadX1Carbon:rvnLENOVO:rn20KH002RUS:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 20KH002RUS dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "devices" https://bugs.launchpad.net/bugs/1888950/+attachment/5395759/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888950 Title: Touchpad doesn't work Status in linux package in Ubuntu: New Bug description: I just reinstalled kubuntu and while using my laptop my touchpad stopped working. I restarted my computer and now the touchpad doesn't show up at all and doesn't work. I followed the instructions here https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 and the instructions say to file a bug since I don't see a synaptics touchpad entry in /proc/bus/input/devices. As instructed, I will also attach that file. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 977 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Jul 25 10:33:04 2020 InstallationDate: Installed on 2020-07-25 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20KH002RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=a844f512-56a4-4f99-a77e-b86a753812f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET68W (1.43 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH002RUS dmi.board.vendor: LENOVO dmi.board.version: SDK0K17763 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KH002RUS:pvrThinkPadX1Carbon:rvnLENOVO:rn20KH002RUS:rvrSDK0K17763WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon dmi.product.name: 20KH002RUS dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon dmi.product.version: ThinkPad X1 Carbon dmi.sys.vendor: LENOVO To manage notifications about this bug go to:
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
It's a good question. In my understanding, the Legion R7000 is the name for China of the Legion-5 15ARH05. In the Lenovo forum, the Lenovo employee has no access to the equipment and indicates it's a kernel issue, suggesting it used to work prior to 5.4 kernel. That looks strange. https://forums.lenovo.com/topic/view/2713/5020793 Also in this thread a member of the Lenovo forum points out to a blog, unfortunately in Chinese, of a guy who may have found a workaround. I tried to google translate it but was not sure of the result to try anything : https://www.cnblogs.com/mikeguan/p/13126497.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias:
[Kernel-packages] [Bug 1888948] [NEW] AMD Oland : failed VCE resume (-110)
Public bug reported: On fresh Ubuntu Fossa Install, I have no hardware video decoding available. I had same error here on bionic, and was solved : https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130 (version 173.17), 173.18 and 173.19 are broken too ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1888948 Title: AMD Oland : failed VCE resume (-110) Status in linux-firmware package in Ubuntu: New Bug description: On fresh Ubuntu Fossa Install, I have no hardware video decoding available. I had same error here on bionic, and was solved : https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1865130 (version 173.17), 173.18 and 173.19 are broken too To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1888948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!
version 117.18 and 117.19 are broken again ! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1865130 Title: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Bug description: === SRU Justification === [Impact] Firmware update of radeon/oland_rlc.bin breaks some radeon cards. [Fix] Revert the new firmware. [Regression Potential] Low. The old firmware has been used for a long time. === Original Bug Report === when trying > DRI_PRIME=1 glxgears , the result in dmesg is as following [ +0.91] radeon :01:00.0: WB enabled [ +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 0x8c00 and cpu addr 0x8ac2d26f [ +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 0x8c04 and cpu addr 0xa848de20 [ +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 0x8c08 and cpu addr 0x1e4494a9 [ +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 0x8c0c and cpu addr 0x98a9748e [ +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 0x8c10 and cpu addr 0xb6ff734d [ +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 0x00075a18 and cpu addr 0x6b4da526 [ +0.100566] radeon :01:00.0: failed VCE resume (-110). [ +0.179115] [drm] ring test on 0 succeeded in 1 usecs [ +0.04] [drm] ring test on 1 succeeded in 1 usecs [ +0.04] [drm] ring test on 2 succeeded in 1 usecs [ +0.06] [drm] ring test on 3 succeeded in 3 usecs [ +0.04] [drm] ring test on 4 succeeded in 3 usecs [ +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!! [ +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, giving up!!! [ +0.40] radeon :01:00.0: failed initializing UVD (-1). [ +0.60] [drm] ib test on ring 0 succeeded in 0 usecs [ +0.51] [drm] ib test on ring 1 succeeded in 0 usecs [ +0.32] [drm] ib test on ring 2 succeeded in 0 usecs [ +0.52] [drm] ib test on ring 3 succeeded in 0 usecs [ +0.29] [drm] ib test on ring 4 succeeded in 0 usecs Also it affects the boot time. the used OpenGL renderer is: "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)" ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: communitheme:ubuntu:GNOME Date: Fri Feb 28 11:50:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801] InstallationDate: Installed on 2019-09-17 (163 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: LENOVO 20238 ProcKernelCmdLine:
[Kernel-packages] [Bug 1887977] Re: Bluetooth headset is not reconnecting automatically if disconnected in between
please let me know if more details are needed -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: Incomplete Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:16973 acl:0 sco:0 events:2752 errors:0 TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888939] Re: Unable to boot with 3.19.0.43-generic
Kernel 3.19.x has not been supported since August 2016. Also, booting from kernels leftover from previous releases is not recommended/tested/supported. Kernel support timeframes: https://wiki.ubuntu.com/Kernel/LTSEnablementStack ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888939 Title: Unable to boot with 3.19.0.43-generic Status in linux package in Ubuntu: Invalid Bug description: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887977] Re: Bluetooth headset is not reconnecting automatically if disconnected in between
the model of the head set is boat rockerz 510 -- 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/1887977 Title: Bluetooth headset is not reconnecting automatically if disconnected in between Status in bluez package in Ubuntu: Incomplete Bug description: Some times Bluetooth headset is not reconnecting automatically if disconnected in between. I need to remove the bluetooth headset and again pair it, then it is connecting. 1. Ubuntu Version - 20.04 2. Software version - bluez Installed: 5.53-0ubuntu3 3. Expected result : Every time when I restart the laptop or resume it the headset should connect automatically 4. Issues Faced : Some times when I restart the laptop or resume the laptop, then eventhough headset is switched on bluetooth connection is not established. Instead if I remove the the headset from bluetooth list and again newly pair it with laptop then headset it connected. Verified the bluetooth head set by connecting it to mobile phone and other os like windows/mac os and it seems there is no issue with headset. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 17 19:58:10 2020 InstallationDate: Installed on 2020-05-04 (73 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Nitro AN515-52 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/13/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.19 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Freed_CFS dmi.board.vendor: CFL dmi.board.version: V1.19 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.19 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19: dmi.product.family: Acer Nitro 5 dmi.product.name: Nitro AN515-52 dmi.product.sku: dmi.product.version: V1.19 dmi.sys.vendor: Acer hciconfig: hci0:Type: Primary Bus: USB BD Address: 18:56:80:A6:CA:8D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:16973 acl:0 sco:0 events:2752 errors:0 TX bytes:678011 acl:0 sco:0 commands:2750 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1887977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
I have found the cause so far that the touchpad MSFT0001: 00 04F3: 3140 is recognized, but no suitable driver is found. With the touchpad ELAN0001: 00 04F3: 3140 it seems to work with a few tricks. ELAN is also available in the kernel config, but MSFT is not. I just don't understand why there are two different names (ELAN and MFST) under the same hardware ID - what did Lenovo do? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW 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 Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku:
[Kernel-packages] [Bug 1880125] Re: v3d driver clock problem forces OpenGL to use software rendering
I have verified that the bug is fixed in the most recent software update on both 32-bit and 64-bit installations of ubuntu 20.04 on a pi 4. ** Changed in: linux-raspi (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1880125 Title: v3d driver clock problem forces OpenGL to use software rendering Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: Fix Released Bug description: release: 32-bit ubuntu 20.04 running on a raspberry pi 4 package: linux-raspi 5.4.0.1008.8 I made the configuration change described in: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1876862 and am running a kernel with v3d on a raspberry pi 4. Unfortunately, OpenGL is still not using the GPU; it's using the software renderer, llvmpipe. Setting LIBGL_DEBUG=verbose and running an OpenGL program shows that OpenGL can't open any /dev/dri/renderD* device. Looking in /dev/dri, there are no device files that begin with "render," indicating the v3d driver isn't starting up properly. Adding debugging code to the kernel, I find that: (1) drivers/gpu/drm/v3d/v3d_drv.c:v3d_platform_drm_probe() fails because it can't get a clock - devm_clk_get() returns an error. (2) in drivers/clk/clk.c:of_clk_get_hw(), the call to of_parse_clkspec() for the v3d driver yields a desired clock source of "firmware-clocks". (3) drivers/clk/clk.c:of_clk_get_hw_from_clkspec() fails because it can only find six clock providers (aux@7e215000, cprman@7e101000, clock@7ef0, clk-108M, clk-usb, clk-osc) none of which match the requested "firmware-clocks". The solution is to add a clock definition to the kernel source and a corresponding change to the device tree, but I'm not familiar enough with either to create that solution myself. In the raspbian kernel source tree, drivers/clk/bcm/clk-raspberrypi.c defines BCM2835_CLOCK_V3D, but there is no corresponding definition in the ubuntu source tree. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1880125/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
OK, it seams I had understood You right. After installing the 6 deb-packages from #20 the problem still persistist. You might now provide a kernel with the next step Or if You tell me the correct git-repro I had to checkout to meake the steps by my own, I will do the 8 steps myself and tell You only the final result of bisect (Your choise). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888570/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
Sorry, I did not know what exactly I havee to do now. As far as I can see, bisect is a tool to do a binary search inside a repro to find a commit that causes a failure (a special behaviour). So to use it I have to have a (checked out) repro. So I believe the commands given above (#19) must be given on a checkout of the kernel repro.. On the other hand the link You gave (#19) shows 6 deb-packages (compiled by You) assuumed by doing the above steps on such a repro. I will now try to install these 6 deb-packages, hope this is what I should do. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.23:bd09/02/2015:svnAcer:pnAspireE5-771G:pvrV3.72:rvnAcer:rnEA70_HB:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: BDW dmi.product.name: Aspire E5-771G dmi.product.sku: Aspire E5-771G_0884_1_23 dmi.product.version: V3.72 dmi.sys.vendor: Acer To manage notifications
[Kernel-packages] [Bug 1849084] Re: Freeze on system-resume caused by kwin and amdgpu driver
Anyone try 5.8.0rc6 yet? I decided to try on a whim since this is a really new laptop. It got rid of many error messages I was getting. And, I removed the "EnablePageFlip" entry (so back to default) and sleep does work normally in 5.8.0r6. Maybe try that and see, or wait until stable releases. Furthermore, VLC would get stuck in the background after opening, I would have to kill the process, but now I no longer have to do that either! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849084 Title: Freeze on system-resume caused by kwin and amdgpu driver Status in kwin package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: This is a well investigated bug by me. Problem: a black screen freeze occurs by suspend-resume process Ubuntu version: Kubuntu 19.10 default plasma, or the backported 5.17 Kernel version: default 5.3.10 or the mainline 5.4.0rc3 xserver-xorg-video-amdgpu: 19.* or the newest from git, the 18.0.1-1 works well This freeze can be reproduced only if opengl 2.0 or 3.1 compositor is enabled in Plasma settings. Xrender is OK however I don't like screen tearing. On Ubuntu 19.10 Gnome desktop (X based) this doesn't occur even if the Gnome's compositor is enabled. (I don't know what is the default one there but I haven't disabled it) I think this is a Kwin / amdgpu driver related bug because of the differentiation. These can be fixed even in Kwin/opengl compositor not just in the amdgpu driver or in kernel. One possible solution: disable opengl compositor by suspend and re- enable it after login. Use fe.: Xrender before login / before the system restored from suspend. For Ubuntu's maintainers: Couldn't be this problem solved by a downstream solution? Maybe a proper script could be enough by resume and by suspend. There are a lot of bugs like this reported in freedesktop bugreport and the developers haven't got enough time for fix them fast enough. Syslog: Oct 21 10:57:26 pc kernel: [ 9475.308852] Code: 85 78 ff ff ff e9 9f f8 ff ff 8b b0 98 04 00 00 48 c7 c7 ef 5f a5 c0 e8 49 2d 9d ff 44 0f b6 45 a3 49 8b 4d 08 e9 bf fa ff ff <0f> 0b e9 ca fb ff ff 0f 0b e8 7d 36 84 c1 66 66 2e 0f 1f 84 00 00 Oct 21 10:57:26 pc kernel: [ 9475.308853] RSP: 0018:b7b54274b7b0 EFLAGS: 00010002 Oct 21 10:57:26 pc kernel: [ 9475.308855] RAX: 0202 RBX: 0202 RCX: 046a Oct 21 10:57:26 pc kernel: [ 9475.308856] RDX: 0001 RSI: 0202 RDI: 0002 Oct 21 10:57:26 pc kernel: [ 9475.308857] RBP: b7b54274b870 R08: R09: 94da76b2d170 Oct 21 10:57:26 pc kernel: [ 9475.308858] R10: b7b54274b708 R11: b7b54274b70c R12: 94da76b2d000 Oct 21 10:57:26 pc kernel: [ 9475.308859] R13: 94d970f2c300 R14: 94da758d25d0 R15: 94da270d1400 Oct 21 10:57:26 pc kernel: [ 9475.308861] FS: 7f2a1b9bea80() GS:94da87c4() knlGS: Oct 21 10:57:26 pc kernel: [ 9475.308863] CS: 0010 DS: ES: CR0: 80050033 Oct 21 10:57:26 pc kernel: [ 9475.308864] CR2: 7fb083e9b4a5 CR3: 00012c11 CR4: 003406e0 Oct 21 10:57:26 pc kernel: [ 9475.308865] Call Trace: Oct 21 10:57:26 pc kernel: [ 9475.308977] amdgpu_dm_atomic_commit_tail+0x96f/0x1030 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.308991] commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309000] ? commit_tail+0x50/0xc0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309009] drm_atomic_helper_commit+0x118/0x120 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309115] amdgpu_dm_atomic_commit+0x95/0xa0 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309135] drm_atomic_commit+0x4a/0x50 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309144] drm_atomic_helper_set_config+0x89/0xa0 [drm_kms_helper] Oct 21 10:57:26 pc kernel: [ 9475.309159] drm_mode_setcrtc+0x1cd/0x7a0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309234] ? amdgpu_cs_wait_ioctl+0xd6/0x150 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309249] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309262] drm_ioctl_kernel+0xae/0xf0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309276] drm_ioctl+0x234/0x3d0 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309290] ? drm_mode_getcrtc+0x190/0x190 [drm] Oct 21 10:57:26 pc kernel: [ 9475.309370] amdgpu_drm_ioctl+0x4e/0x80 [amdgpu] Oct 21 10:57:26 pc kernel: [ 9475.309376] do_vfs_ioctl+0x407/0x670 Oct 21 10:57:26 pc kernel: [ 9475.309379] ? do_futex+0x10f/0x1e0 Oct 21 10:57:26 pc kernel: [ 9475.309382] ksys_ioctl+0x67/0x90 Oct 21 10:57:26 pc kernel: [ 9475.309384] __x64_sys_ioctl+0x1a/0x20 Oct 21
[Kernel-packages] [Bug 1888939] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888939 Title: Unable to boot with 3.19.0.43-generic Status in linux package in Ubuntu: Confirmed Bug description: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888939/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888939] [NEW] Unable to boot with 3.19.0.43-generic
Public bug reported: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Acer Aspire V3-571G ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=5830b30e-69e8-4bb4-8a2b-bc2b43c7414a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-07-12 (12 days ago) dmi.bios.date: 10/15/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: VA50_HC_CR dmi.board.vendor: Acer dmi.board.version: Type2 - Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V2.07 dmi.modalias: dmi:bvnAcer:bvrV2.07:bd10/15/2012:svnAcer:pnAspireV3-571G:pvrV2.07:rvnAcer:rnVA50_HC_CR:rvrType2-BoardVersion:cvnAcer:ct10:cvrV2.07: dmi.product.family: Type1Family dmi.product.name: Aspire V3-571G dmi.product.sku: Aspire V3-_0648_V2.07 dmi.product.version: V2.07 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888939 Title: Unable to boot with 3.19.0.43-generic Status in linux package in Ubuntu: New Bug description: My computer is unusable because of bug 1848771, which causes reset on waking from suspend. (that such a bug could slip through to a release in the first place is beyond my understanding. Don't you guys test anything?) Being unable to suspend means being unable to use the computer. Don't tell me I can avoid suspending because (1) seriously? and (2) what if I forget and suspend by accident? Loosing all my data is a disproportionate punishment. So, since the bug seems to affect kernel versions 5.1 and later, I thought I could boot with an earlier one. I am not familiar with booting with different kernel versions (because why should I), but Grub's boot menu has an option "Advanced options for Ubuntu" (or something like that) that opens a submenu where apparently I can choose a linux kernel version. A few in the list are post-5.1. The latest available that is pre-5.1 is 3.19.0.43-generic So I tried that one, but all I get is a black screen saying "Loading liunux 3.19.0.43-generic something..." and a blinking cursor. I waited a few minutes and gave up. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_40_44_generic_69 nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: teo1999 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Jul 25 15:38:39 2020 HibernationDevice: RESUME=UUID=ff7e702a-a05a-47fd-8c14-551e81f9e9e3 InstallationDate: Installed on 2013-10-11 (2478 days ago) InstallationMedia:
[Kernel-packages] [Bug 1888936] Re: cifsd deadlocks / CIFS related Oopses
** Attachment added: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1888936/+attachment/5395685/+files/kern.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1888936 Title: cifsd deadlocks / CIFS related Oopses Status in linux-aws package in Ubuntu: New Bug description: We're running a server at AWS which collects data from machines over CIFS. This involves a a lot of mounting and umounting of CIFS (about 100 targets with 2 shares each with 10 delay in between). The targets might sometimes become unavailable when they turned of for the weekend or rebooted. The server doing this has to be rebooted every few hours because CIFS connection start to hang and don't recover. The usual symptom is: Jul 24 10:12:59 connector kernel: [ 7765.705409] CIFS: Attempting to mount //172.22.2.112/Meldung Jul 24 10:13:01 connector kernel: [ 7767.689258] CIFS: Attempting to mount //172.22.2.112/Wartung Jul 24 10:13:06 connector kernel: [ 7772.758283] CIFS: Attempting to mount //172.30.113.108/Meldung Jul 24 10:13:06 connector kernel: [ 7773.300475] CIFS: Attempting to mount //172.30.113.108/Wartung Jul 24 10:13:09 connector kernel: [ 7776.364516] CIFS: Attempting to mount //172.30.99.55/Meldung Jul 24 10:13:11 connector kernel: [ .978731] CIFS: Attempting to mount //172.30.99.55/Wartung [...] Jul 24 10:16:13 connector kernel: [ 7960.390529] CIFS VFS: \\172.30.113.108 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:15 connector kernel: [ 7962.468649] CIFS VFS: \\172.30.93.171 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:18 connector kernel: [ 7964.999037] CIFS VFS: \\172.30.99.55 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:31 connector kernel: [ 7977.798821] INFO: task cifsd:26252 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.803730] Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 24 10:16:31 connector kernel: [ 7977.808526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 24 10:16:31 connector kernel: [ 7977.820291] cifsd D0 26252 2 0x80004000 Jul 24 10:16:31 connector kernel: [ 7977.820298] Call Trace: Jul 24 10:16:31 connector kernel: [ 7977.820307] __schedule+0x2e3/0x740 Jul 24 10:16:31 connector kernel: [ 7977.820310] ? __switch_to_asm+0x40/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820313] ? __switch_to_asm+0x34/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820315] schedule+0x42/0xb0 Jul 24 10:16:31 connector kernel: [ 7977.820318] rwsem_down_read_slowpath+0x16c/0x4a0 Jul 24 10:16:31 connector kernel: [ 7977.820321] down_read+0x85/0xa0 Jul 24 10:16:31 connector kernel: [ 7977.820324] iterate_supers_type+0x70/0xf0 Jul 24 10:16:31 connector kernel: [ 7977.820411] ? cifs_set_cifscreds.isra.0+0x800/0x800 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820429] cifs_reconnect+0x8a/0xdc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820433] ? vprintk_func+0x4c/0xbc Jul 24 10:16:31 connector kernel: [ 7977.820449] cifs_readv_from_socket+0x17a/0x260 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820465] cifs_read_from_socket+0x4c/0x70 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820482] ? allocate_buffers+0x43/0x130 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820497] cifs_demultiplex_thread+0xe1/0xcc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820500] kthread+0x104/0x140 Jul 24 10:16:31 connector kernel: [ 7977.820516] ? cifs_handle_standard+0x1b0/0x1b0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820518] ? kthread_park+0x90/0x90 Jul 24 10:16:31 connector kernel: [ 7977.820520] ret_from_fork+0x22/0x40 Jul 24 10:16:31 connector kernel: [ 7977.820524] INFO: task cifsd:26328 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.827503] Not tainted 5.4.0-1020-aws #20-Ubuntu That is, cifsd gets stuck fetching credentials for the reconnect. I'm attaching the full syslog with stack traces from all hung cifsd task (I don't see where the deadlock is there). The mounting/unmounting is done in a privileged Docker container. If we restart that, we usually run into an Oops: Jul 25 07:43:29 connector kernel: [64677.164367] Oops: [#1] SMP NOPTI Jul 25 07:43:29 connector kernel: [64677.164370] CPU: 0 PID: 265452 Comm: cifsd Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 25 07:43:29 connector kernel: [64677.164370] Hardware name: Amazon EC2 t3a.large/, BIOS 1.0 10/16/2017 Jul 25 07:43:29 connector kernel: [64677.164400] RIP: 0010:cifs_reconnect+0x9be/0xdc0 [cifs] Jul 25 07:43:29 connector kernel: [64677.164403] Code: e8 bb 43 0c d5 66 90 48 8b 45 c0 48 8d 55 c0 4c 8d 6d b8 48 39 c2 74 62 49 be 00 01 00 00 00 00 ad de 48 8b 45 c0 4c 8d 78 f 8 <48> 8b 00 48 8d 58 f8
[Kernel-packages] [Bug 1888936] [NEW] cifsd deadlocks / CIFS related Oopses
Public bug reported: We're running a server at AWS which collects data from machines over CIFS. This involves a a lot of mounting and umounting of CIFS (about 100 targets with 2 shares each with 10 delay in between). The targets might sometimes become unavailable when they turned of for the weekend or rebooted. The server doing this has to be rebooted every few hours because CIFS connection start to hang and don't recover. The usual symptom is: Jul 24 10:12:59 connector kernel: [ 7765.705409] CIFS: Attempting to mount //172.22.2.112/Meldung Jul 24 10:13:01 connector kernel: [ 7767.689258] CIFS: Attempting to mount //172.22.2.112/Wartung Jul 24 10:13:06 connector kernel: [ 7772.758283] CIFS: Attempting to mount //172.30.113.108/Meldung Jul 24 10:13:06 connector kernel: [ 7773.300475] CIFS: Attempting to mount //172.30.113.108/Wartung Jul 24 10:13:09 connector kernel: [ 7776.364516] CIFS: Attempting to mount //172.30.99.55/Meldung Jul 24 10:13:11 connector kernel: [ .978731] CIFS: Attempting to mount //172.30.99.55/Wartung [...] Jul 24 10:16:13 connector kernel: [ 7960.390529] CIFS VFS: \\172.30.113.108 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:15 connector kernel: [ 7962.468649] CIFS VFS: \\172.30.93.171 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:18 connector kernel: [ 7964.999037] CIFS VFS: \\172.30.99.55 has not responded in 180 seconds. Reconnecting... Jul 24 10:16:31 connector kernel: [ 7977.798821] INFO: task cifsd:26252 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.803730] Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 24 10:16:31 connector kernel: [ 7977.808526] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Jul 24 10:16:31 connector kernel: [ 7977.820291] cifsd D0 26252 2 0x80004000 Jul 24 10:16:31 connector kernel: [ 7977.820298] Call Trace: Jul 24 10:16:31 connector kernel: [ 7977.820307] __schedule+0x2e3/0x740 Jul 24 10:16:31 connector kernel: [ 7977.820310] ? __switch_to_asm+0x40/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820313] ? __switch_to_asm+0x34/0x70 Jul 24 10:16:31 connector kernel: [ 7977.820315] schedule+0x42/0xb0 Jul 24 10:16:31 connector kernel: [ 7977.820318] rwsem_down_read_slowpath+0x16c/0x4a0 Jul 24 10:16:31 connector kernel: [ 7977.820321] down_read+0x85/0xa0 Jul 24 10:16:31 connector kernel: [ 7977.820324] iterate_supers_type+0x70/0xf0 Jul 24 10:16:31 connector kernel: [ 7977.820411] ? cifs_set_cifscreds.isra.0+0x800/0x800 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820429] cifs_reconnect+0x8a/0xdc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820433] ? vprintk_func+0x4c/0xbc Jul 24 10:16:31 connector kernel: [ 7977.820449] cifs_readv_from_socket+0x17a/0x260 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820465] cifs_read_from_socket+0x4c/0x70 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820482] ? allocate_buffers+0x43/0x130 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820497] cifs_demultiplex_thread+0xe1/0xcc0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820500] kthread+0x104/0x140 Jul 24 10:16:31 connector kernel: [ 7977.820516] ? cifs_handle_standard+0x1b0/0x1b0 [cifs] Jul 24 10:16:31 connector kernel: [ 7977.820518] ? kthread_park+0x90/0x90 Jul 24 10:16:31 connector kernel: [ 7977.820520] ret_from_fork+0x22/0x40 Jul 24 10:16:31 connector kernel: [ 7977.820524] INFO: task cifsd:26328 blocked for more than 120 seconds. Jul 24 10:16:31 connector kernel: [ 7977.827503] Not tainted 5.4.0-1020-aws #20-Ubuntu That is, cifsd gets stuck fetching credentials for the reconnect. I'm attaching the full syslog with stack traces from all hung cifsd task (I don't see where the deadlock is there). The mounting/unmounting is done in a privileged Docker container. If we restart that, we usually run into an Oops: Jul 25 07:43:29 connector kernel: [64677.164367] Oops: [#1] SMP NOPTI Jul 25 07:43:29 connector kernel: [64677.164370] CPU: 0 PID: 265452 Comm: cifsd Not tainted 5.4.0-1020-aws #20-Ubuntu Jul 25 07:43:29 connector kernel: [64677.164370] Hardware name: Amazon EC2 t3a.large/, BIOS 1.0 10/16/2017 Jul 25 07:43:29 connector kernel: [64677.164400] RIP: 0010:cifs_reconnect+0x9be/0xdc0 [cifs] Jul 25 07:43:29 connector kernel: [64677.164403] Code: e8 bb 43 0c d5 66 90 48 8b 45 c0 48 8d 55 c0 4c 8d 6d b8 48 39 c2 74 62 49 be 00 01 00 00 00 00 ad de 48 8b 45 c0 4c 8d 78 f 8 <48> 8b 00 48 8d 58 f8 4d 39 ef 74 3d 49 8b 57 10 48 89 50 08 48 89 Jul 25 07:43:29 connector kernel: [64677.218175] RSP: 0018:bf25c0b27cf8 EFLAGS: 00010286 Jul 25 07:43:29 connector kernel: [64677.222539] RAX: RBX: 9cdef66f0800 RCX: 95cd8510 Jul 25 07:43:29 connector kernel: [64677.227607] RDX: bf25c0b27d30 RSI: bf25c0b27d18 RDI: c0aeec18 Jul 25 07:43:29 connector kernel: [64677.232638] RBP: bf25c0b27d70 R08: 0180 R09: Jul 25 07:43:29
[Kernel-packages] [Bug 1848771] Re: Reboot after resume from suspend (deep)
Someone mentioned disabling bluetooth "both in Linux and in the BIOS". I don't have such an option in the BIOS, I disabled it in linux and it didn't help. Actually I'm a bit skeptical of the reports saying that this or that fixed the issue: I'd like to know how many times they have tried suspending and for how long they have been using their laptop after whatever change they say have fixed the issue. The failure happens randomly, so one succesful suspend after changing something proves nothing. Now what's the workaround for those of us who want to be able to suspend our computer without loosing data? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Thank you for fixing this bug. Installing mutter 3.36.4-0ubuntu0.20.04.1 and libmutter 3.36.4-0ubuntu0.20.04.1 from focal-proposed has resolved this issue for me. Note: The updated libmutter from focal-proposed also had to be explicitly installed by me, as it was not automatically pulled in when updating mutter. Steps: 1) Enabled focal-proposed 2) apt update 3) apt install mutter libmutter 4) Disabled focal-proposed 5) Removed ~/.config/monitors.xml and ~gdm/config/monitors.xml 6) Rebooted 7) After login, I successfully applied my desired monitor configuration (changing the primary monitor and setting other monitor to portrait orientation). Side notes: 1) I still had to copy ~/.config/monitors.xml to ~gdm/.config/monitors.xml for the correct primary monitor and orientation to be set on the login screen. 2) After applying the display configuration, the icons in the top-right of the gnome panel appeared blured (network/bluetooth). This was resolved by applying 150% fractional scaling and then applying 100% scaling again in the gnome display settings. I haven't had time to reproduce this to know if it's a one-off or ongoing bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1775717] Re: CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
any progresss? What else information needed to comtinue?
--
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/1775717
Title:
CPU/GPU Fans suddenly go 100% RPM on Asus ROG G752VT
Status in linux package in Ubuntu:
Incomplete
Status in thermald package in Ubuntu:
Confirmed
Bug description:
After upgrading from Ubuntu 16.04 to 18.04, I've noticed that CPU and
GPU fans suddenly go full throttle. It doesn't seem to depend on
temperature, could happen when 32 °C reported, sometimes the laptop
can work for day or two without this issue, but eventually it happens.
The only way to stop fans is to power off the laptop, power on (fans
go 100% at this point again), power off during BIOS splash screen and
power on again. Seems to happen more often after waking up from a
sleep.
Things tried:
Upgrading BIOS to latest available on ASUS site to the date of
writing. No change.
asus-fan kernel module (https://github.com/daringer/asus-fan). Detects
both fans and shows correct speed in /sys/class/hwmon/*/fan{1,2}*, but
does not seem to control it and does not prevent going full throttle.
4.17.0 kernel from Ubuntu mainline builds. Doesn't seem to affect the
issue.
Userspace fan control software (https://github.com/hirschmann/nbfc).
Can control speed of both fans to the point where they go full
throttle, after that has no effect on them.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: whale 3068 F pulseaudio
/dev/snd/controlC0: whale 3068 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
HibernationDevice: RESUME=UUID=ada9b595-bbf2-40a3-8575-5908492bb969
InstallationDate: Installed on 2014-10-20 (1333 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64+mac
(20140722.2)
MachineType: ASUSTeK COMPUTER INC. G752VT
NonfreeKernelModules: nvidia_modeset nvidia wl
Package: linux (not installed)
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic
root=UUID=f6509d56-6183-464c-90bb-9c3be2c8abdf ro quiet splash
acpi_backlight=vendor vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
RelatedPackageVersions:
linux-restricted-modules-4.15.0-23-generic N/A
linux-backports-modules-4.15.0-23-generic N/A
linux-firmware 1.173.1
Tags: bionic
Uname: Linux 4.15.0-23-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dip docker lpadmin plugdev sambashare sudo tty
video
_MarkForUpload: True
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G752VT.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G752VT
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrG752VT.304:bd06/29/2017:svnASUSTeKCOMPUTERINC.:pnG752VT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG752VT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: G
dmi.product.name: G752VT
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1775717/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395652/+files/ProcEnviron.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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395647/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395650/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395656/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395653/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395654/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] Re: Battery drain during sleep. System suspended before kernel suspends all tasks
apport information ** Tags added: apport-collected ** Description changed: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! + --- + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: alice 2262 F pulseaudio + CurrentDesktop: Unity + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd + InstallationDate: Installed on 2019-11-22 (245 days ago) + InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. + Bus 001 Device 002: ID 5986:2113 Acer, Inc + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: LENOVO 20NR001LGE + NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook + Package: linux (not installed) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-112-generic N/A + linux-backports-modules-4.15.0-112-generic N/A + linux-firmware 1.157.23 + Tags: xenial + Uname: Linux 4.15.0-112-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 08/12/2019 + dmi.bios.vendor: LENOVO + dmi.bios.version: R10ET39W (1.24 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20NR001LGE + 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad L390 + dmi.product.name: 20NR001LGE + dmi.product.version: ThinkPad L390 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395645/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux
[Kernel-packages] [Bug 1888924] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395651/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395655/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395658/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395649/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395657/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395646/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1888924/+attachment/5395648/+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/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! --- ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alice 2262 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=5cd85b64-9fb7-4363-bb1d-f25cdad960bd InstallationDate: Installed on 2019-11-22 (245 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:00a2 Synaptics, Inc. Bus 001 Device 002: ID 5986:2113 Acer, Inc Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NR001LGE NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-112-generic root=UUID=f94d702f-ca9f-4f9a-a368-8defce0e5531 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-112.113~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-112-generic N/A linux-backports-modules-4.15.0-112-generic N/A linux-firmware 1.157.23 Tags: xenial Uname: Linux 4.15.0-112-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R10ET39W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NR001LGE 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.modalias: dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NR001LGE:pvrThinkPadL390:rvnLENOVO:rn20NR001LGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L390 dmi.product.name: 20NR001LGE dmi.product.version: ThinkPad L390 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] 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 1888924 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888924] [NEW] Battery drain during sleep. System suspended before kernel suspends all tasks
Public bug reported: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888924 Title: Battery drain during sleep. System suspended before kernel suspends all tasks Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 16.04.6 LTS Release: 16.04 I think this is similar to: Bug #1825636 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825636 Machine: Lenovo ThinkPad L390, fresh install Suspend drains the battery in approx 1 day. journalctl -b | grep -i "should not be sleeping" returns: "cache: parent cpu1 should not be sleeping" for all cpus This is a real problem, as I rely on suspending frequently! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886247] Re: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found
The OEM update fixed the issue, thanks!!! No more using my dongle, so I'm very pleased with the result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1886247 Title: Realtek [10ec:c82f] Subsystem [17aa:c02f] Wifi adapter not found Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: SRU justification: [Impact] New realtek wifi card ID found on ThinkCentre. No driver is loaded to support it. [Fix] This wifi card is very similar as 0xc822 in rtw88. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Add new ID to supported driver. Test on hw, double confirmed by LP bugs. This patch is backported from original link due to the 5.8-rc1 driver file path changed, no function changed. Maintainer had merged: https://github.com/lwfinger/rtlwifi_new/commit/b76b895a90f1168c5223849562fd6e1196b2c351 This git repo is moving by maintainer, not availible by now. = 01:00.0 Network controller: Realtek Semiconductor Co., Ltd. Device c82f Looking for a working solution on a fresh install (USB BOOT) of Ubuntu. A work-around helped, for a while, but I would really like to disconnect my Wifi Dongel and use my brand new laptop! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: christian 1277 F pulseaudio /dev/snd/pcmC0D0c: christian 1277 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 07:58:06 2020 InstallationDate: Installed on 2020-06-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81W8 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f610713f-73ad-468c-8a69-9a47b385acab ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux StagingDrivers: r8712u UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/04/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN26WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32866 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad S145-15IIL dmi.modalias: dmi:bvnLENOVO:bvrDKCN26WW:bd03/04/2020:svnLENOVO:pn81W8:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32866WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL: dmi.product.family: IdeaPad S145-15IIL dmi.product.name: 81W8 dmi.product.sku: LENOVO_MT_81W8_BU_idea_FM_IdeaPad S145-15IIL dmi.product.version: Lenovo IdeaPad S145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886247/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888715] Re: UDP data corruption caused by buggy udp_recvmsg() -> skb_copy_and_csum_datagram_msg()
rcu_access_pointer(sk->sk_filter) is basically the same as
sk->sk_filter.
If sk->sk_filter is true, the change makes no difference.
If sk->sk_filter is false, the change also drops a UDP packet with incorrect
UDP checksum by "goto csum_error;". Without the change, the packet is dropped
in udp_recvmsg(); with the change, the packet is dropped earlier.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1888715
Title:
UDP data corruption caused by buggy udp_recvmsg() ->
skb_copy_and_csum_datagram_msg()
Status in linux package in Ubuntu:
Incomplete
Bug description:
The Xenial v4.4 kernel (https://kernel.ubuntu.com/git/ubuntu/ubuntu-
xenial.git/tag/?h=Ubuntu-4.4.0-184.214) lacks this upstream bug
fix("make skb_copy_datagram_msg() et.al. preserve ->msg_iter on erro"
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2);
as a result, the v4.4 kernel can deliver corrupt data to the
application when a corrupt packet is closely followed by a valid
packet, and actually the UDP payload of the corrupt packet is
delivered to the application with the "from IP/Port" of the valid
packet, so this is actually a security vulnerability that can be used
to trick the application to think the corrupt packet’s payload is sent
from the valid packet’s IP address/port, i.e. a source IP based
security authentication mechanism can be bypassed.
Details:
For a packet longer than 76 bytes (see line 3951,
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/include/linux/skbuff.h?h=v5.8-rc6#n3948),
Linux delays the UDP checksum verification until the application
invokes the syscall recvmsg().
In the recvmsg() syscall handler, while Linux is copying the UDP
payload to the application’s memory, it calculates the UDP checksum.
If the calculated checksum doesn’t match the received checksum, Linux
drops the corrupt UDP packet, and then starts to process the next
packet (if any), and if the next packet is valid (i.e. the checksum is
correct), Linux will copy the valid UDP packet's payload to the
application’s receiver buffer.
The bug is: before Linux starts to copy the valid UDP packet, the data
structure used to track how many more bytes should be copied to the
application memory is not reset to what it was when the application
just entered the kernel by the syscall! Consequently, only a small
portion or none of the valid packet’s payload is copied to the
application’s receive buffer, and later when the application exits
from the kernel, actually most of the application’s receive buffer
contains the payload of the corrupt packet while recvmsg() returns the
size of the UDP payload of the valid packet. Note: this is actually a
security vulnerability that can be used to trick the application to
think the corrupt packet’s payload is sent from the valid packet’s IP
address/port -- so a source IP based security authentication mechanism
can be bypassed.
The bug was fixed in this 2017 patch “make skb_copy_datagram_msg()
et.al. preserve ->msg_iter on error
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=3278682123811dd8ef07de5eb701fc4548fcebf2)”,
but unluckily the patch is only backported to the upstream v4.9+
kernels. I'm reporting this bug to request the bugfix to be backported
to the v4.4 Xenial kernel, which is still used by some users and has
not been EOL'ed (https://ubuntu.com/about/release-cycle).
I have the below one-line workaround patch to force the recvmsg() syscall
handler to return to the userspace when Linux detects a corrupt UDP packet, so
the application will invoke the syscall again to receive the next good UDP
packet:
--- a/net/ipv4/udp.c
+++ b/net/ipv4/udp.c
@@ -1367,6 +1367,7 @@ csum_copy_err:
/* starting over for a new packet, but check if we need to yield */
cond_resched();
msg->msg_flags &= ~MSG_TRUNC;
+ return -EAGAIN;
goto try_again;
}
Note: the patch may not work well with blocking sockets, for which
typically the application doesn’t expect an error of -EAGAIN. I guess
it would be safer to return -EINTR instead.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1888715/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
