[Kernel-packages] [Bug 2077579] Re: Potential regression: Microcode SW error detected in linux 5.4.0.195.193
In the initial automated tests, the WiFi connection could still be established before and after suspend, regardless of the microcode errors displayed in the kernel logs. ** Changed in: linux (Ubuntu Focal) Importance: High => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2077579 Title: Potential regression: Microcode SW error detected in linux 5.4.0.195.193 Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-signed-hwe-5.15 source package in Focal: Invalid Bug description: As part of SRU testing in our HW lab, we are running Checkbox SRU test plan on devices, including this one: https://certification.canonical.com/hardware/202001-27665/submission/387585/ (Dell Precision 5550) This artefact is part of SRU testing visible here: https://test-observer.canonical.com/#/debs/52784 The test case `wireless/check_iwlwifi_microcode_crash_wlp0s20f3` fails with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` I've connected to that device and extracted the full kernel log using `sudo journalctl -k -b-2`; it's attached to this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-121-generic 5.15.0-121.131~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-121.131~20.04.1-generic 5.15.163 Uname: Linux 5.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 16:18:32 2024 InstallationDate: Installed on 2020-08-03 (1478 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077579] Re: Potential regression: Microcode SW error detected in linux 5.4.0.195.193
I found another device failing the firmware check as well as WiFi connection tests for WiFi AC and N: https://certification.canonical.com/hardware/201904-26953/submission/389251/test- results/fail/ This might have the same root cause. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2077579 Title: Potential regression: Microcode SW error detected in linux 5.4.0.195.193 Status in linux package in Ubuntu: Invalid Status in linux-signed-hwe-5.15 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-signed-hwe-5.15 source package in Focal: Invalid Bug description: As part of SRU testing in our HW lab, we are running Checkbox SRU test plan on devices, including this one: https://certification.canonical.com/hardware/202001-27665/submission/387585/ (Dell Precision 5550) This artefact is part of SRU testing visible here: https://test-observer.canonical.com/#/debs/52784 The test case `wireless/check_iwlwifi_microcode_crash_wlp0s20f3` fails with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` I've connected to that device and extracted the full kernel log using `sudo journalctl -k -b-2`; it's attached to this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-121-generic 5.15.0-121.131~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-121.131~20.04.1-generic 5.15.163 Uname: Linux 5.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 16:18:32 2024 InstallationDate: Installed on 2020-08-03 (1478 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077579] Re: Potential regression: Microcode SW error detected in linux 5.4.0.195.193
I think it's because a lot of automated tests are run on the device, and one of them upgrades the system packages. However, 5.4.0-195 is used initially to test, and this is where the issue was found. When I ran `ubuntu-bug linux`, linux-hwe-5.15 was installed. But the journalctl logs I provide are from a previous boot, where 5.4 is used. However, after chatting with Anthony Wong, it seems this might not be related to the kernel, but to the linux-firmware package. (Not sure on this one, I will let the experts decide!) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/2077579 Title: Potential regression: Microcode SW error detected in linux 5.4.0.195.193 Status in linux-signed-hwe-5.15 package in Ubuntu: New Bug description: As part of SRU testing in our HW lab, we are running Checkbox SRU test plan on devices, including this one: https://certification.canonical.com/hardware/202001-27665/submission/387585/ (Dell Precision 5550) This artefact is part of SRU testing visible here: https://test-observer.canonical.com/#/debs/52784 The test case `wireless/check_iwlwifi_microcode_crash_wlp0s20f3` fails with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` I've connected to that device and extracted the full kernel log using `sudo journalctl -k -b-2`; it's attached to this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.15.0-121-generic 5.15.0-121.131~20.04.1 ProcVersionSignature: Ubuntu 5.15.0-121.131~20.04.1-generic 5.15.163 Uname: Linux 5.15.0-121-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudID: maas CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 16:18:32 2024 InstallationDate: Installed on 2020-08-03 (1478 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.15 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.15/+bug/2077579/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077548] [NEW] Potential regression: Microcode SW error detected in linux 5.4.0.195.193
Public bug reported: When testing linux 5.4.0-195.215-generic using Checkbox on a device previously enabled with focal, the after-suspend- wireless/check_iwlwifi_microcode_crash_wlp0s20f3 test case failed with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` See Test Observer for more information: https://test- observer.canonical.com/#/debs/52784 Failure rate: 100% (2 out of 2 runs) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1036-oem 5.6.0-1036.39 ProcVersionSignature: Ubuntu 5.6.0-1036.39-oem 5.6.19 Uname: Linux 5.6.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 22:03:44 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 InstallationDate: Installed on 2024-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.6 (Ubuntu) Importance: Undecided Status: Invalid ** Tags: amd64 apport-bug focal uec-images ** Description changed: - When testing linux 5.4.0.195.193 using Checkbox on a device previously - enabled with focal, the after-suspend- + When testing linux 5.4.0-195.215-generic using Checkbox on a device + previously enabled with focal, the after-suspend- wireless/check_iwlwifi_microcode_crash_wlp0s20f3 test case failed with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` See Test Observer for more information: https://test- observer.canonical.com/#/debs/52784 Failure rate: 100% (2 out of 2 runs) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1036-oem 5.6.0-1036.39 ProcVersionSignature: Ubuntu 5.6.0-1036.39-oem 5.6.19 Uname: Linux 5.6.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 22:03:44 2024 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 InstallationDate: Installed on 2024-08-21 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: linux-signed-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: linux-signed-oem-5.6 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/2077548 Title: Potential regression: Microcode SW error detected in linux 5.4.0.195.193 Status in linux-signed-oem-5.6 package in Ubuntu: Invalid Bug description: When testing linux 5.4.0-195.215-generic using Checkbox on a device previously enabled with focal, the after-suspend- wireless/check_iwlwifi_microcode_crash_wlp0s20f3 test case failed with the following output: ``` Boot -2 c8ba8c3ef8d54d2fb531e1683b5079a6 Tue 2024-08-20 06:05:01 EDT—Tue 2024-08-20 06:25:01 EDT, Microcode SW error detected ``` See Test Observer for more information: https://test- observer.canonical.com/#/debs/52784 Failure rate: 100% (2 out of 2 runs) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.6.0-1036-oem 5.6.0-1036.39 ProcVersionSignature: Ubuntu 5.6.0-1036.39-oem 5.6.19 Uname: Linux 5.6.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip CloudArchitecture: x86_64 CloudName: maas CloudPlatform: maas CloudSubPlatform: seed-dir (http://10.102.164.2:5248/MAAS/metadata/) Date: Wed Aug 21 22:03:44 2024 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-varys+X54 InstallationDate: In
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Confirmed Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
That's weird... I downloaded the last attachment I sent and checked it with vim and I can see past the 28th... Anyway, here is another attempt. Same log, xzipped. I checked and the last line of the log is on Aug 29 09:26:34. ** Attachment added: "journalctl-b0-20230829.log.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+attachment/5696619/+files/journalctl-b0-20230829.log.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
That's what I attached. When I could not get back to a proper graphical environment, I switched to a TTY, ran `sudo journalctl -b0 > journalctl-b0-20230829.log`, and I attached it to that bug. As you can see in the logs, the device had been running since August 21, and on Aug 28 evening I suspended it: Aug 28 19:34:36 coltrane systemd[1]: Reached target Sleep. Aug 28 19:34:36 coltrane systemd[1]: Starting Record successful boot for GRUB... Aug 28 19:34:36 coltrane systemd[1]: Starting Restart Syncthing after resume... Aug 28 19:34:36 coltrane systemd[1]: Starting System Suspend... Aug 28 19:34:36 coltrane systemd-sleep[903135]: Entering sleep state 'suspend'... Aug 28 19:34:36 coltrane kernel: PM: suspend entry (deep) Aug 28 19:34:36 coltrane systemd[1]: grub-common.service: Deactivated successfully. Aug 28 19:34:36 coltrane systemd[1]: Finished Record successful boot for GRUB. Aug 28 19:34:36 coltrane systemd[1]: Starting GRUB failed boot detection... and then resumed it on Aug 29 at 09:12, and this is when the stack trace appears: Aug 29 09:12:26 coltrane kernel: Filesystems sync: 0.018 seconds Aug 29 09:12:31 coltrane kernel: Freezing user space processes Aug 29 09:12:31 coltrane kernel: Freezing user space processes completed (elapsed 0.003 seconds) Aug 29 09:12:31 coltrane kernel: OOM killer disabled. Aug 29 09:12:32 coltrane kernel: Freezing remaining freezable tasks Aug 29 09:12:32 coltrane kernel: Freezing remaining freezable tasks completed (elapsed 0.001 seconds) Aug 29 09:12:32 coltrane kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 29 09:12:32 coltrane kernel: sd 1:0:0:0: [sda] Synchronizing SCSI cache Aug 29 09:12:32 coltrane kernel: sd 1:0:0:0: [sda] Stopping disk Aug 29 09:12:32 coltrane kernel: sd 2:0:0:0: [sdb] Synchronizing SCSI cache Aug 29 09:12:32 coltrane kernel: sd 3:0:0:0: [sdc] Synchronizing SCSI cache Aug 29 09:12:32 coltrane kernel: sd 4:0:0:0: [sdd] Synchronizing SCSI cache Aug 29 09:12:32 coltrane kernel: sd 2:0:0:0: [sdb] Stopping disk Aug 29 09:12:32 coltrane kernel: sd 4:0:0:0: [sdd] Stopping disk Aug 29 09:12:32 coltrane kernel: sd 3:0:0:0: [sdc] Stopping disk (...) Aug 29 09:12:32 coltrane kernel: kworker/u8:24: page allocation failure: order:5, mode:0x40d00(GFP_NOIO|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 Aug 29 09:12:32 coltrane kernel: CPU: 3 PID: 903164 Comm: kworker/u8:24 Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu Aug 29 09:12:32 coltrane kernel: Hardware name: ASUS All Series/B85M-K, BIOS 3602 03/26/2018 Aug 29 09:12:32 coltrane kernel: Workqueue: events_unbound async_run_entry_fn Aug 29 09:12:32 coltrane kernel: Call Trace: Aug 29 09:12:32 coltrane kernel: Aug 29 09:12:32 coltrane kernel: dump_stack_lvl+0x48/0x70 Aug 29 09:12:32 coltrane kernel: dump_stack+0x10/0x20 Aug 29 09:12:32 coltrane kernel: warn_alloc+0x14b/0x1c0 Aug 29 09:12:32 coltrane kernel: ? __alloc_pages_direct_compact+0xa7/0x240 Aug 29 09:12:32 coltrane kernel: __alloc_pages_slowpath.constprop.0+0x910/0x990 Aug 29 09:12:32 coltrane kernel: __alloc_pages+0x32c/0x360 Aug 29 09:12:32 coltrane kernel: __kmalloc_large_node+0x89/0x170 Aug 29 09:12:32 coltrane kernel: kmalloc_large+0x21/0xc0 Aug 29 09:12:32 coltrane kernel: dc_set_power_state+0x49/0x190 [amdgpu] Aug 29 09:12:32 coltrane kernel: dm_suspend+0x9f/0x290 [amdgpu] Aug 29 09:12:32 coltrane kernel: ? vi_common_set_clockgating_state+0xd7/0x190 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_device_ip_suspend_phase1+0xb9/0x1d0 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_device_suspend+0xca/0x1d0 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_pmops_suspend+0x33/0x50 [amdgpu] Aug 29 09:12:32 coltrane kernel: pci_pm_suspend+0x8a/0x1c0 Aug 29 09:12:32 coltrane kernel: ? __pfx_pci_pm_suspend+0x10/0x10 Aug 29 09:12:32 coltrane kernel: dpm_run_callback+0x54/0x1a0 Aug 29 09:12:32 coltrane kernel: __device_suspend+0x14b/0x400 Aug 29 09:12:32 coltrane kernel: async_suspend+0x1f/0x80 Aug 29 09:12:32 coltrane kernel: async_run_entry_fn+0x33/0x130 Aug 29 09:12:32 coltrane kernel: process_one_work+0x21f/0x440 Aug 29 09:12:32 coltrane kernel: worker_thread+0x50/0x3f0 Aug 29 09:12:32 coltrane kernel: ? __pfx_worker_thread+0x10/0x10 Aug 29 09:12:32 coltrane kernel: kthread+0xee/0x120 Aug 29 09:12:32 coltrane kernel: ? __pfx_kthread+0x10/0x10 Aug 29 09:12:32 coltrane kernel: ret_from_fork+0x2c/0x50 Aug 29 09:12:32 coltrane kernel: Aug 29 09:12:32 coltrane kernel: Mem-Info: Aug 29 09:12:32 coltrane kernel: active_anon:6 inactive_anon:2748750 isolated_anon:0 active_file:309 inactive_file:232 isolated_file:0 unevictable:41 dirty:1 writeback:8 slab_reclaimable:60650 slab_unreclaimable:80021 mapped:1 shmem:70425 pagetables:29671 sec_pagetables:0 bounce:0 kern
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
@superm1 Thanks for your feedback! Here is the full journal from that boot. Edit: ah crap, it's the same file, I thought I had originally sent an edited version with just the stack trace... not sure what else to provide. ** Attachment added: "journalctl-b0-20230829.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+attachment/5696590/+files/journalctl-b0-20230829.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696589/+files/acpidump.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696584/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696583/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696585/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696587/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696588/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696586/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696578/+files/Lsusb-t.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696579/+files/Lsusb-v.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696582/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696581/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696580/+files/PaInfo.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696576/+files/Lspci-vt.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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696575/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696577/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696574/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: pieq 2262 F pulseaudio /dev/snd/controlC1: pieq 2262 F pulseaudio /dev/snd/controlC0: pieq 2262 F pulseaudio /dev/snd/controlC2: pieq 2262 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-28 (245 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: ASUS All Series Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: linux-restricted-modules-6.2.0-26-generic N/A linux-backports-modules-6.2.0-26-generic N/A linux-firmware20220329.git681281e4-0ubuntu3.17 RfKill: StagingDrivers: r8188eu Tags: jammy staging Uname: Linux 6.2.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/26/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3602 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
apport information ** Tags added: apport-collected staging ** Description changed: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC3: pieq 2262 F pulseaudio + /dev/snd/controlC1: pieq 2262 F pulseaudio + /dev/snd/controlC0: pieq 2262 F pulseaudio + /dev/snd/controlC2: pieq 2262 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-12-28 (245 days ago) + InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + IwConfig: + lono wireless extensions. + + enp3s0no wireless extensions. + MachineType: ASUS All Series + Package: linux (not installed) + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-26-generic root=UUID=40d932e0-3982-4e4a-a5e0-5c5704eca928 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 + RebootRequiredPkgs: Error: path contained symlinks. + RelatedPackageVersions: + linux-restricted-modules-6.2.0-26-generic N/A + linux-backports-modules-6.2.0-26-generic N/A + linux-firmware20220329.git681281e4-0ubuntu3.17 + RfKill: + + StagingDrivers: r8188eu + Tags: jammy staging + Uname: Linux 6.2.0-26-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/26/2018 + dmi.bios.release: 4.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3602 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: B85M-K + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3602:bd03/26/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnB85M-K:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuAll: + dmi.product.family: ASUS MB + dmi.product.name: All Series + dmi.product.sku: All + dmi.product.version: System Version + dmi.sys.vendor: ASUS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2033327/+attachment/5696573/+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/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux package in Ubuntu: Incomplete Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
Attaching GPU-related logs after reboooting the device. Outputs from: modinfo amdgpu > modinfo.amdgpu.log sudo lshw > lshw.log sudo dmidecode > dmidecode.log lspci -nn > lspci.nn.log lspci -vnn > lspci.vnn.log cp /var/log/Xorg.0.log . lsmod | grep amdgpu > lsmod.amdgpu.log ** Attachment added: "gpu-logs.tgz" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2033327/+attachment/5695800/+files/gpu-logs.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033327] Re: Desktop cannot resume after suspend: screen not detected
Attached are the logs for the last boot. As you can see, the device had been running for a week without any problem, but suspending/resuming killed it. We can see the following stack trace in the logs: Aug 29 09:12:32 coltrane kernel: kworker/u8:24: page allocation failure: order:5, mode:0x40d00(GFP_NOIO|__GFP_COMP|__GFP_ZERO), nodemask=(null),cpuset=/,mems_allowed=0 Aug 29 09:12:32 coltrane kernel: CPU: 3 PID: 903164 Comm: kworker/u8:24 Not tainted 6.2.0-26-generic #26~22.04.1-Ubuntu Aug 29 09:12:32 coltrane kernel: Hardware name: ASUS All Series/B85M-K, BIOS 3602 03/26/2018 Aug 29 09:12:32 coltrane kernel: Workqueue: events_unbound async_run_entry_fn Aug 29 09:12:32 coltrane kernel: Call Trace: Aug 29 09:12:32 coltrane kernel: Aug 29 09:12:32 coltrane kernel: dump_stack_lvl+0x48/0x70 Aug 29 09:12:32 coltrane kernel: dump_stack+0x10/0x20 Aug 29 09:12:32 coltrane kernel: warn_alloc+0x14b/0x1c0 Aug 29 09:12:32 coltrane kernel: ? __alloc_pages_direct_compact+0xa7/0x240 Aug 29 09:12:32 coltrane kernel: __alloc_pages_slowpath.constprop.0+0x910/0x990 Aug 29 09:12:32 coltrane kernel: __alloc_pages+0x32c/0x360 Aug 29 09:12:32 coltrane kernel: __kmalloc_large_node+0x89/0x170 Aug 29 09:12:32 coltrane kernel: kmalloc_large+0x21/0xc0 Aug 29 09:12:32 coltrane kernel: dc_set_power_state+0x49/0x190 [amdgpu] Aug 29 09:12:32 coltrane kernel: dm_suspend+0x9f/0x290 [amdgpu] Aug 29 09:12:32 coltrane kernel: ? vi_common_set_clockgating_state+0xd7/0x190 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_device_ip_suspend_phase1+0xb9/0x1d0 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_device_suspend+0xca/0x1d0 [amdgpu] Aug 29 09:12:32 coltrane kernel: amdgpu_pmops_suspend+0x33/0x50 [amdgpu] Aug 29 09:12:32 coltrane kernel: pci_pm_suspend+0x8a/0x1c0 Aug 29 09:12:32 coltrane kernel: ? __pfx_pci_pm_suspend+0x10/0x10 Aug 29 09:12:32 coltrane kernel: dpm_run_callback+0x54/0x1a0 Aug 29 09:12:32 coltrane kernel: __device_suspend+0x14b/0x400 Aug 29 09:12:32 coltrane kernel: async_suspend+0x1f/0x80 Aug 29 09:12:32 coltrane kernel: async_run_entry_fn+0x33/0x130 Aug 29 09:12:32 coltrane kernel: process_one_work+0x21f/0x440 Aug 29 09:12:32 coltrane kernel: worker_thread+0x50/0x3f0 Aug 29 09:12:32 coltrane kernel: ? __pfx_worker_thread+0x10/0x10 Aug 29 09:12:32 coltrane kernel: kthread+0xee/0x120 Aug 29 09:12:32 coltrane kernel: ? __pfx_kthread+0x10/0x10 Aug 29 09:12:32 coltrane kernel: ret_from_fork+0x2c/0x50 Aug 29 09:12:32 coltrane kernel: Aug 29 09:12:32 coltrane kernel: Mem-Info: Aug 29 09:12:32 coltrane kernel: active_anon:6 inactive_anon:2748750 isolated_anon:0 active_file:309 inactive_file:232 isolated_file:0 unevictable:41 dirty:1 writeback:8 slab_reclaimable:60650 slab_unreclaimable:80021 mapped:1 shmem:70425 pagetables:29671 sec_pagetables:0 bounce:0 kernel_misc_reclaimable:0 free:106406 free_pcp:0 free_cma:0 Aug 29 09:12:32 coltrane kernel: Node 0 active_anon:24kB inactive_anon:10995000kB active_file:1236kB inactive_file:928kB unevictable:164kB isolated(anon):0kB isolated(file):0kB mapped:4kB dirty:4kB writeback:32kB shmem:281700kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 2048kB writeback_tmp:0kB kernel_stack:42288kB pagetables:118684kB sec_pagetables:0kB all_unreclaimable? no Aug 29 09:12:32 coltrane kernel: Node 0 DMA free:13308kB boost:0kB min:64kB low:80kB high:96kB reserved_highatomic:0KB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:15988kB managed:15360kB mlocked:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 29 09:12:32 coltrane kernel: lowmem_reserve[]: 0 3380 15822 15822 15822 Aug 29 09:12:32 coltrane kernel: Node 0 DMA32 free:197068kB boost:32448kB min:46872kB low:50476kB high:54080kB reserved_highatomic:0KB active_anon:0kB inactive_anon:2122496kB active_file:0kB inactive_file:0kB unevictable:80kB writepending:0kB present:3606752kB managed:3541040kB mlocked:80kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 29 09:12:32 coltrane kernel: lowmem_reserve[]: 0 0 12442 12442 12442 Aug 29 09:12:32 coltrane kernel: Node 0 Normal free:215248kB boost:119452kB min:172544kB low:185816kB high:199088kB reserved_highatomic:2048KB active_anon:24kB inactive_anon:8872504kB active_file:1040kB inactive_file:1136kB unevictable:84kB writepending:36kB present:13090816kB managed:12748956kB mlocked:84kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB Aug 29 09:12:32 coltrane kernel: lowmem_reserve[]: 0 0 0 0 0 Aug 29 09:12:32 coltrane kernel: Node 0 DMA: 1*4kB (U) 1*8kB (U) 1*16kB (U) 1*32kB (U) 1*64kB (U) 1*128kB (U) 1*256kB (U) 1*512kB (U) 0*1024kB 2*2048kB (UM) 2*4096kB (M) = 13308kB Aug 29 09:12:32 coltrane kernel: Node 0 DMA32: 49272*4kB (UME) 1*8kB (U)
[Kernel-packages] [Bug 2033327] [NEW] Desktop cannot resume after suspend: screen not detected
Public bug reported: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2033327 Title: Desktop cannot resume after suspend: screen not detected Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: Hardware: - Desktop PC (Intel i5 4th gen) - GPU: AMD RX580 - Ubuntu 22.04 with kernel HWE 6.2 Steps to reproduce: 1. Start the device 2. Suspend 3. Resume by pressing a key on the keyboard Expected results: The screen lights up, showing the screen to put my password to resume the session. Actual result: The screen OSD displays a "No Signal" message before turning off. Nothing seems to happen when I press keyboard keys or move the mouse. Switching to a TTY by pressing Ctrl+Alt+F3 works: I can login and see the logs (that's how I filed this bug). Switching back to graphics session (Ctrl+Alt+F2) does't work: it shows the cursor and nothing else (black screen). Switching to login screen (Ctrl+Alt+F1) works: I can see the list of users, select on and enter my password... but then I'm back to the same black screen with the mouse cursor. This is not a regression, as the same problem happened already with the previous point release (I believe it was Linux kernel 5.15). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Aug 29 09:15:49 2023 InstallationDate: Installed on 2022-12-28 (243 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2033327/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974842] Re: Audio card [8086:9d71] does not work at all (input, output) on 22.04
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974842 Title: Audio card [8086:9d71] does not work at all (input, output) on 22.04 Status in linux package in Ubuntu: Confirmed Bug description: A year ago, I filed lp:1915117 after an kernel update broke the audio on my Acer Swift SF314-54. The bug has been marked as fixed, but I just tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any audio at all. Please check lp:1915117 for some background, and the attached logs from sosreport for more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 00:27:20 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Swift SF314-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1974842/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1974842] [NEW] Audio card [8086:9d71] does not work at all (input, output) on 22.04
Public bug reported: A year ago, I filed lp:1915117 after an kernel update broke the audio on my Acer Swift SF314-54. The bug has been marked as fixed, but I just tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any audio at all. Please check lp:1915117 for some background, and the attached logs from sosreport for more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 00:27:20 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Swift SF314-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ** Attachment added: "sosreport-ubuntu-2022-05-21-mwvqzya.tar.xz" https://bugs.launchpad.net/bugs/1974842/+attachment/5591649/+files/sosreport-ubuntu-2022-05-21-mwvqzya.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1974842 Title: Audio card [8086:9d71] does not work at all (input, output) on 22.04 Status in linux package in Ubuntu: New Bug description: A year ago, I filed lp:1915117 after an kernel update broke the audio on my Acer Swift SF314-54. The bug has been marked as fixed, but I just tried 22.04 this morning, using 5.15.0-25-generic, and I don't have any audio at all. Please check lp:1915117 for some background, and the attached logs from sosreport for more information. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.470 CurrentDesktop: ubuntu:GNOME Date: Sat May 21 00:27:20 2022 LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: Acer Swift SF314-54 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2021 dmi.bios.release: 1.17 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.17 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.17 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.17 dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.17:bd04/16/2021:br1.17:efr1.9:svnAcer:pnSwiftSF314-54:pvrV1.17:rvnKBL:rnStrongbow_KL:rvrV1.17:cvnAcer:ct10:cvrV1.17:sku: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.ne
[Kernel-packages] [Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310
Cheese has a known issue working with some formats (see lp:1882896), which was fixed, but the fix has not been backported to Ubuntu 20.04. Could you also check the resolution found by the https://webcamtests.com/ website? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1945927 Title: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310 Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1945927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945927] Re: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310
Hello! Sorry for the very late reply... First of all, there have been a few Linux kernel updates in Ubuntu 20.04 since you opened this issue. Please upgrade your system and check if you have the latest available version of the kernel installed; in a terminal, you can run these commands: sudo apt update sudo apt upgrade uname -r You should get something like "5.13.0-30-generic". If the problem still persists, install the Video4Linux utility package and check what formats and resolutions are available for the webcam; again, in a terminal: sudo apt install v4l-utils v4l2-ctl -D --list-formats-ext You should get something like: = Driver Info: Driver name : uvcvideo Card type: Video Capture 5 Bus info : usb-:00:14.0-3 Driver version : 5.13.19 Capabilities : 0x84a1 (...) [1]: 'MJPG' (Motion-JPEG, compressed) Size: Discrete 640x480 (...) = Please attach the output of the v4l2-ctl command to this issue so we can investigate. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1945927 Title: Terrible resolution on integrated webcam on Dell XPS 13 Developer Edition 9310 Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: This seems to be a known issue, but I couldn't find any launchpad bug corresponding to it. Apologies if I missed it, or if there is a better place for reporting a bug like this. When I try to use the webcam on my newly purchased Dell XPS-13-9310 Developer Edition, using Cheese (or any other app) on Ubuntu 20.04.2 LTS (fossa-bulbasaur X55), as it came out of the box, I only get a very pixelated low quality 640x480 resolution instead of the hardware's 1280×720 capability as advertised here: https://www.dell.com/en-us/work/shop/dell-laptops-and- notebooks/xps-13-developer-edition/spd/xps-13-9310-laptop From what I gather, no linux driver exist that can use the full resolution of this webcam. I hope that it is somehow possible to get a proper driver from Dell / Realtek. If not, I hope that Realtek can provide documentation for the interface so that a proper driver can be written. I'm tempted to try to make that my first contribution of a driver, but in all likelihood I won't have the time or motivation to learn all that's needed and actually write it. Until a driver is available, I would appreciate if Dell would clarify on their website that their 9310 Developer Edition can only use the full advertised resolution in Windows. (I would not have bought this laptop if I had known about this limitation, as I frequently use Google Meet / Zoom and the current quality is not acceptable to me). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Oct 3 15:40:31 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-09-22 (11 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem-5.10/+bug/1945927/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3
Following Kent's comment #18, a few additional steps are required to complete the test, as described to me by Jacob Wu from Asus. The following steps are a more detailed "step 5" from previous comment, if you will: 1. Create a device image for partition, in this case 400MB memory space: [Command] $ sudo dd if=/dev/zero of=/temp.img bs=1M count=400 [Return] 400+0 records in 400+0 records out 2. Format partition as FAT32 [Command] $ sudo mkdosfs -F 32 /temp.img [Return] mkfs.fat 4.1 (2017-01-24) 3. Load g_mass_storage for partition [Command] $ sudo modprobe g_mass_storage file=/temp.img stall=0 4. From an Ubuntu (or Windows) host, connect a cable to the USB OTG port (on Aaeon EHL board, it's the USB type C connector) of the device under test (DUT), and a new mass storage should be available in the host. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936903] Re: CDTS Network (Ethernet) failures
** Changed in: intel/lookout-canyon Status: New => Incomplete ** Changed in: intel/lookout-canyon Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936903 Title: CDTS Network (Ethernet) failures Status in intel: New Status in intel lookout-canyon series: Incomplete Status in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: New Bug description: [Summary]Some networking tests fail [Steps to reproduce]Run Manual Non-Device Networking Tests $ sudo snap install checkbox20 $ sudo snap install cdts --classic --channel=20.04/stable $ cdts.checkbox-cli (X) Networking tests (manual) [X] + Non-device specific networking tests [Expected result]100% pass [Actual result] networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet port on this board) networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN devices) [Failure rate]100% [Additional information] CID: 202106-28175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot
** Changed in: intel/lookout-canyon Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946223 Title: [iotg][tgl][tgl-aaeon] 20211006 image does not boot Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: The daily build containing the new kernel does not boot. It gets stuck about 2 seconds into the cycle with the message "Run /init as init process" (see attached image file for boot message sequence.) System: TGL-Aaeon (CID: 202110-29509) Steps to reproduce: Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/ Uncompressed file with unxz -k Copied the .img file to my secondary USB drive. Boot 20.04 LTS from primary USB drive. Select Try Ubuntu Wipe out /dev/sda (primary storage) Use dd to copy the image from secondary USB drive to /dev/sda Reboot, removing USB drives when prompted. Expected Result: System should boot Ubuntu Desktop with kernel 5.13-1006 Actual Result: System hangs 2 seconds into the boot cycle with "Run /init as init process" Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1946223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Changed in: intel/lookout-canyon Importance: Undecided => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929890 Title: [EHL][TGL][ADL] PMC Time-aware GPIO Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description GPIO controller on CNL PCH has a new feature which allows for timed trigger of GPIO events. We should consider at least following aspects and if needed we can create subtasks: Translation of ART->System Time on input Any output GPIO Cross-timestamp and/or edge counting of input GPIOs supporting high frequency input Similar feature to input, counting output edges Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment Time Aware GPIO Output - Fire on Trigger Time Aware GPIO Input - Stamp on Edge Detection Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929901] Re: [EHL][TGL][ADL] EDAC support
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL][ADL] EDAC support Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux package in Ubuntu: Triaged Status in linux-intel package in Ubuntu: Fix Released Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929903 Title: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946223 Title: [iotg][tgl][tgl-aaeon] 20211006 image does not boot Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: The daily build containing the new kernel does not boot. It gets stuck about 2 seconds into the cycle with the message "Run /init as init process" (see attached image file for boot message sequence.) System: TGL-Aaeon (CID: 202110-29509) Steps to reproduce: Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/ Uncompressed file with unxz -k Copied the .img file to my secondary USB drive. Boot 20.04 LTS from primary USB drive. Select Try Ubuntu Wipe out /dev/sda (primary storage) Use dd to copy the image from secondary USB drive to /dev/sda Reboot, removing USB drives when prompted. Expected Result: System should boot Ubuntu Desktop with kernel 5.13-1006 Actual Result: System hangs 2 seconds into the boot cycle with "Run /init as init process" Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1946223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform
** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938298 Title: [EHL][Graphic]Removing force probe protection from EHL platform Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in The Focal Fossa: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The graphic driver i915 must be mounted manually instead of automatically. Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://anongit.freedesktop.org/git/drm-tip.git To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938298] Re: [EHL][Graphic]Removing force probe protection from EHL platform
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1938298 Title: [EHL][Graphic]Removing force probe protection from EHL platform Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in Ubuntu: New Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: New Status in The Focal Fossa: New Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The graphic driver i915 must be mounted manually instead of automatically. Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://anongit.freedesktop.org/git/drm-tip.git To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936903] Re: CDTS Network (Ethernet) failures
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1936903 Title: CDTS Network (Ethernet) failures Status in intel: New Status in intel lookout-canyon series: New Status in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: New Bug description: [Summary]Some networking tests fail [Steps to reproduce]Run Manual Non-Device Networking Tests $ sudo snap install checkbox20 $ sudo snap install cdts --classic --channel=20.04/stable $ cdts.checkbox-cli (X) Networking tests (manual) [X] + Non-device specific networking tests [Expected result]100% pass [Actual result] networking/info_device1_enp0s30f4 - skipped by tester (no second ethernet port on this board) networking/info_device2_UNKNOWN - failed by tester (should not have UNKNOWN devices) [Failure rate]100% [Additional information] CID: 202106-28175 SKU: system-manufacturer: Intel Corporation system-product-name: Tiger Lake Client Platform bios-version: TGLIFUI1.R00.3455.A03.2011281547 CPU: Genuine Intel(R) CPU @ 2.60GHz (16x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a60] kernel-version: 5.11.0-1009-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1936903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943524] Re: [EHL] Intel ishtp VNIC driver
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: [ehl] Shutdown hangs on board
** Changed in: intel/lookout-canyon Milestone: None => sprint2 ** Changed in: intel/lookout-canyon Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: [ehl] Shutdown hangs on board Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938408] Re: [ehl] board does not support soft reboot
** Also affects: intel/lookout-canyon Importance: Undecided Status: New ** Changed in: intel/lookout-canyon Status: New => Fix Committed ** Changed in: intel/lookout-canyon Milestone: None => sprint2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938408 Title: [ehl] board does not support soft reboot Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Telling the EHL board to reboot from within Ubuntu causes it to hang, forcing you to do a hard reboot. [Steps to reproduce] 1. Open terminal window. 2. $ reboot [Expected result] System should gracefullyl reboot. [Actual result] Screen goes blank except for a cursor. System does not reboot. You must hard reboot (pull the plug) [Failure rate]100% [Additional information] CID: 202105-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929890] Re: [EHL][TGL][ADL] PMC Time-aware GPIO
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929890 Title: [EHL][TGL][ADL] PMC Time-aware GPIO Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description GPIO controller on CNL PCH has a new feature which allows for timed trigger of GPIO events. We should consider at least following aspects and if needed we can create subtasks: Translation of ART->System Time on input Any output GPIO Cross-timestamp and/or edge counting of input GPIOs supporting high frequency input Similar feature to input, counting output edges Time Aware GPIO Frequency Discipline - GPIO Frequency Adjustment Time Aware GPIO Output - Fire on Trigger Time Aware GPIO Input - Stamp on Edge Detection Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929902] Re: [EHL] enable USB-dw3
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929902 Title: [EHL] enable USB-dw3 Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux package in Ubuntu: Incomplete Status in linux-intel package in Ubuntu: Fix Committed Bug description: Description Enable USB-dw3 for Elkhart Lake Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929889] Re: [TGL][ADL] Enable CET(Control-flow Enforcement Technology)
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1929889 Title: [TGL][ADL] Enable CET(Control-flow Enforcement Technology) Status in intel: New Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Triaged Status in linux-intel source package in Focal: New Bug description: Description Enable Tiger Lake ROP CET(Control-flow Enforcement Technology) An upcoming Intel® processor family feature that counters return/jump-oriented programming (ROP) attacks Hardware: Tiger Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938413] Re: [ehl] Shutdown hangs on board
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1938413 Title: [ehl] Shutdown hangs on board Status in intel: Fix Committed Status in intel lookout-canyon series: Fix Committed Status in linux-intel package in Ubuntu: Fix Committed Bug description: [Summary]Go to Power -> Shutdown and the screen goes blank, but the system does not shut down. You cannot recover and have to perform a hard reboot. [Steps to reproduce] 1. Boot up Ubuntu 2. Power -> Shutdown (click ok) [Expected result] System should cleanly shut down. [Actual result] Screen blanks with a blinking cursor, the system does not shut down, the fan is still on. System is unresponsive, forcing you to do a hard reset. [Failure rate]100% [Additional information] CID: 20215-29063 SKU: system-manufacturer: Intel Corporation system-product-name: Elkhart Lake Embedded Platform bios-version: EHLSFWI1.R00.2091.A00.2002250754 CPU: Genuine Intel(R) CPU @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] kernel-version: 5.11.0-1009-intel [Stage] Device froze, issue reported and logs collected right after a reboot To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1938413/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929901] Re: [EHL][TGL][ADL] EDAC support
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929901 Title: [EHL][TGL][ADL] EDAC support Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux package in Ubuntu: Triaged Status in linux-intel package in Ubuntu: Fix Released Status in linux-intel-5.13 package in Ubuntu: Fix Committed Bug description: Description EDAC driver support on EHL & TGL for reporting ECC error and DIMM location Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929901/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929903] Re: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929903 Title: [EHL][TGL][ADL] Enable Time Coordinated Compute interface driver Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux-intel package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description Time Coordinated Compute (TCC) Pseudo SRAM interface support on top of Cache Allocation Technology Hardware: Tiger Lake & Elkhart Lake & Alder Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z --- [Update, 2021-08-26] Please find the Getting Started Guide for Intel TCC Tools here, has steps to download, install and verify: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top.html You can find the BIOS settings to enable TCC here: https://software.intel.com/content/www/us/en/develop/documentation/get- started-with-tcc-tools-2021-2-ubuntu-yp-uefi/top/step-6-configure- intel-tcc-tools-in-bios.html To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946223] Re: [iotg][tgl][tgl-aaeon] 20211006 image does not boot
** Also affects: intel/lookout-canyon Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1946223 Title: [iotg][tgl][tgl-aaeon] 20211006 image does not boot Status in intel: Fix Committed Status in intel lookout-canyon series: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: The daily build containing the new kernel does not boot. It gets stuck about 2 seconds into the cycle with the message "Run /init as init process" (see attached image file for boot message sequence.) System: TGL-Aaeon (CID: 202110-29509) Steps to reproduce: Downloaded focal-preinstalled-desktop-amd64+intel-iot.img.xz from https://cdimage.ubuntu.com/focal/daily-preinstalled/20211006/ Uncompressed file with unxz -k Copied the .img file to my secondary USB drive. Boot 20.04 LTS from primary USB drive. Select Try Ubuntu Wipe out /dev/sda (primary storage) Use dd to copy the image from secondary USB drive to /dev/sda Reboot, removing USB drives when prompted. Expected Result: System should boot Ubuntu Desktop with kernel 5.13-1006 Actual Result: System hangs 2 seconds into the boot cycle with "Run /init as init process" Reproducibility: 100% To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1946223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
After additional discussion with other members, I retried with the same config as in comment #9: CID: 202109-29496 SKU: AAEON UPN-EHL01 Image used: ubuntu-core-20-amd64+intel-iot.img.xz (20211014.2) kernel: 5.13.0-1007-intel Turns out, as Doug mentioned in comment #11, the UC20 configuration is based on the initial setup wizard when installing UC20. In my case, I had only plugged one of the two network interfaces (enp1s0), so only this one was configured. The other was marked as `disabled` and never used, even when plugging a cable afterwards. The netplan configuration looked like this: $ cat /etc/netplan/00-snapd-config.yaml # This is the network config written by 'console-conf' network: ethernets: enp1s0: dhcp4: true version: 2 In order to change this, I edited it like so: $ cat /etc/netplan/00-snapd-config.yaml # This is the network config written by 'console-conf' network: ethernets: enp1s0: dhcp4: true enp2s0: dhcp4: true version: 2 then ran `sudo netplay apply`, and the second interface (enp2s0) got an IP shortly afterwards. So, at least on my side (Aaeon EHL board), it's a non-issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
Trying this with CID: 202109-29496 SKU: AAEON UPN-EHL01 Image used: ubuntu-core-20-amd64+intel-iot.img.xz (20211014.2) kernel: 5.13.0-1007-intel When plugging in both Ethernet ports, only one of them retrieves an IP: $ ip a 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp2s0: mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 00:07:32:61:5b:08 brd ff:ff:ff:ff:ff:ff 3: enp1s0: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:07:32:61:5b:07 brd ff:ff:ff:ff:ff:ff inet 192.168.1.126/24 brd 192.168.1.255 scope global dynamic enp1s0 valid_lft 86268sec preferred_lft 86268sec inet6 fe80::207:32ff:fe61:5b07/64 scope link valid_lft forever preferred_lft forever Nothing happens in `dmesg -w` when I unplug/replug an Ethernet cable in enp2s0. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Following a discussion with Chris, I checked /usr/share/alsa/ucm2/ and discovered that /usr/share/alsa/ucm2/hda-dsp/ was missing. I created it and put the files from https://github.com/alsa-project /alsa-ucm-conf/tree/master/ucm2/hda-dsp in it. I then restarted the computer and selected the 5.10.0-1035-oem kernel provided by Chris. Now, not only the sound output works as expected from internal speakers, but the internal microphone works as well! I can also plug headsets using the Jack output and the sound is output as expected. I attach pulseaudio logs for reference (without any headset connected). ** Attachment added: "pulseaudio-info.logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5509024/+files/pulseaudio-info.logs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
$ cat /sys/module/snd_intel_dspcfg/parameters/dsp_driver 2 Same result, though... still Dummy Output in Sound Settings. ** Attachment added: "dmesg_kernel_5.10.0-1035-oem_snd_intel_dspcfg.dsp_driver_2.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507896/+files/dmesg_kernel_5.10.0-1035-oem_snd_intel_dspcfg.dsp_driver_2.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Here is the dmesg output as well as some output from aplay and pactl after installing the kernel from: https://people.canonical.com/~mschiu77/lp1915117/v2/ $ uname -a Linux 5.10.0-1035-oem #36 SMP Mon Jun 28 16:41:34 CST 2021 x86_64 x86_64 x86_64 GNU/Linux I can now see the audio card with aplay -l, but it still shows "Dummy Output" in the Sound Settings and no sound can be heard when trying to play a sound with aplay. ** Attachment added: "alsa-pulseaudio-info.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507875/+files/alsa-pulseaudio-info.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Attachment added: "dmesg_kernel_5.10.0-1035-oem.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507874/+files/dmesg_kernel_5.10.0-1035-oem.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
For the sake of testing, I checked on the latest Impish daily image, with kernel 5.11.0-18-generic. Same problem. dmesg attached. Alsa and PulseAudio don't detect any sound card, even though in dmesg we can see: $ sudo dmesg | grep -i snd [ 26.169850] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 26.169858] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SST driver $ aplay -l aplay: device_list:276: no soundcards found... ubuntu@ubuntu:~$ pactl list cards ubuntu@ubuntu:~$ pactl list sources Source #0 State: SUSPENDED Name: auto_null.monitor Description: Monitor of Dummy Output Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 13 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor of Sink: auto_null Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY Properties: device.description = "Monitor of Dummy Output" device.class = "monitor" device.icon_name = "audio-input-microphone" Formats: pcm ubuntu@ubuntu:~$ pactl list sinks Sink #0 State: SUSPENDED Name: auto_null Description: Dummy Output Driver: module-null-sink.c Sample Specification: s16le 2ch 44100Hz Channel Map: front-left,front-right Owner Module: 13 Mute: no Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dB balance 0.00 Base Volume: 65536 / 100% / 0.00 dB Monitor Source: auto_null.monitor Latency: 0 usec, configured 0 usec Flags: DECIBEL_VOLUME LATENCY SET_FORMATS Properties: device.description = "Dummy Output" device.class = "abstract" device.icon_name = "audio-card" Formats: pcm ** Attachment added: "dmesg_kernel_5.11.0-18-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5507056/+files/dmesg_kernel_5.11.0-18-generic.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
This is what I have now, with: kernel command line: BOOT_IMAGE=/vmlinuz-5.10.0-1025-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 uname -a Linux 5.10.0-1025-oem #26 SMP Thu May 6 16:43:31 CST 2021 x86_64 x86_64 x86_64 GNU/Linux ** Attachment added: "dmesg_20210625_kernel_5.10.0-1025-oem.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506963/+files/dmesg_20210625_kernel_5.10.0-1025-oem.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
And related dmesg.log ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506571/+files/dmesg.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
And the related logs from alsa-info when the dsp_driver is set to 2. ** Attachment added: "alsa-info.txt.6e591x7epf" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506569/+files/alsa-info.txt.6e591x7epf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Attached is the output of pactl list sources. Both aplay -l and arecord -l output the following error message: aplay: device_list:274: no soundcards found... I tried "snd_intel_dspcfg.dsp_driver=2", it's activated (cat /sys/module/snd_intel_dspcfg/parameters/dsp_driver returns "2"), but still only a Dummy output. ** Attachment added: "pactl_list_sources.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5506567/+files/pactl_list_sources.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
@Chris thanks for the heads up! Still "Dummy output" in the Sound Settings. Here are the steps I followed: 1. Downdloaded and installed the *.deb you pointed to: $ sudo dpkg -i *.deb 2. Copied the Intel SST firmware binary file to /lib/firmware: $ sudo cp skl_hda_dsp_generic-tplg.bin /lib/firmware/ 3. Rebooted, disabled Secure Boot and selected the new kernel (5.10.0-1025-oem). In dmesg, I see the following: $ dmesg | grep snd [ 10.027748] snd_hda_intel :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 10.027752] snd_hda_intel :00:1f.3: Digital mics found on Skylake+ platform, using SST driver [ 10.051128] snd_soc_skl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 [ 10.051132] snd_soc_skl :00:1f.3: Digital mics found on Skylake+ platform, using SST driver [ 10.051879] snd_soc_skl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 10.103255] snd_soc_skl :00:1f.3: Direct firmware load for 9d71-ACRSYS-ACRPRDCT-2-tplg.bin failed with error -2 [ 10.103261] snd_soc_skl :00:1f.3: tplg fw 9d71-ACRSYS-ACRPRDCT-2-tplg.bin load failed with -2, trying alternative tplg name skl_hda_dsp_generic-tplg.bin [ 10.104296] snd_soc_skl :00:1f.3: ASoC: Parent card not yet available, widget card binding deferred [ 10.129385] snd_hda_codec_realtek ehdaudio0D0: autoconfig for ALC256: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [ 10.129388] snd_hda_codec_realtek ehdaudio0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 10.129389] snd_hda_codec_realtek ehdaudio0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [ 10.129390] snd_hda_codec_realtek ehdaudio0D0:mono: mono_out=0x0 [ 10.129390] snd_hda_codec_realtek ehdaudio0D0:inputs: [ 10.129392] snd_hda_codec_realtek ehdaudio0D0: Internal Mic=0x1a [ 10.129393] snd_hda_codec_realtek ehdaudio0D0: Headset Mic=0x19 Please see the attached log for full dmesg. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5495892/+files/dmesg.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.
[Kernel-packages] [Bug 1924685] [NEW] No sound output/input available after installing 21.04
Public bug reported: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Description changed: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. - Attached are logs from `pactl list` and `alsa-info`. + Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: + + https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 1561 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.11.0-14-generic N/A - linux-backports-modules-5.11.0-14-generic N/A - linux-firmware 1.197 + linux-restricted-modules-5.11.0-14-generic N/A + linux-backports-modules-5.11.0-14-generic N/A + linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1924685 Title: No sound output/input available after installing 21.04 Status in linux package in Ubuntu: New Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroReleas
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Adding alsa-info log from the mainline kernel. ** Attachment added: "alsa-info..mainline-kernel-5.11.0-051100-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5464398/+files/alsa-info..mainline-kernel-5.11.0-051100-generic.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
I installed the following: linux-headers-5.11.0-051100_5.11.0-051100.202102142330_all.deb linux-headers-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb linux-image-unsigned-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb linux-modules-5.11.0-051100-generic_5.11.0-051100.202102142330_amd64.deb I was warned for a bunch of "possible missing firmwares" for module i915: W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 (see install.log attached for complete logs) After disabling Secure Boot and botting in kernel 5.11, I still face the same issue: no input (nor output) sound devices (only "Dummy Output"). ** Attachment added: "install.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5464397/+files/install.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailin
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Attachment added: "dmesg-20.10-kernel-5.4.0-65-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461559/+files/dmesg-20.10-kernel-5.4.0-65-generic.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
As a point of comparison, below are attached logs when using the same device with the same Ubuntu (20.10) but with an older 5.4.0-65-generic kernel. ** Attachment added: "alsa-info.20.10-kernel-5.4.0-65-generic.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461558/+files/alsa-info.20.10-kernel-5.4.0-65-generic.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
I've also tried booting a live USB with the latest alpha version from 21.04, based on kernel 5.8.0-36-generic, and the results are the same: no sound card detected, "Dummy Output" displayed in Sound Settings. See attached archive with same logs (dmesg, pactl, alsa-info). ** Attachment added: "21.04-kernel-5.8.0-36-audio-logs.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461562/+files/21.04-kernel-5.8.0-36-audio-logs.tar.xz ** Description changed: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == - No more sound card detected (Sound Settings display "Dummy Output" in - the list of output devices). + 2. Sound card is available, and sound can be output to the internal speakers. + 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.8.0-41-generic N/A - linux-backports-modules-5.8.0-41-generic N/A - linux-firmware1.190.3 + linux-restricted-modules-5.8.0-41-generic N/A + linux-backports-modules-5.8.0-41-generic N/A + linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generi
[Kernel-packages] [Bug 1915117] Re: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
** Attachment added: "pactl-list-20.10-kernel-5.4.0-65-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+attachment/5461560/+files/pactl-list-20.10-kernel-5.4.0-65-generic.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/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915117] [NEW] [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8
Public bug reported: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-5.8.0-41-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2021-02-03 (5 days ago) dmi.bios.date: 11/21/2018 dmi.bios.release: 1.11 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.11 dmi.board.name: Strongbow_KL dmi.board.vendor: KBL dmi.board.version: V1.11 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.11:bd11/21/2018:br1.11:efr1.6:svnAcer:pnSwiftSF314-54:pvrV1.11:rvnKBL:rnStrongbow_KL:rvrV1.11:cvnAcer:ct10:cvrV1.11: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-54 dmi.product.sku: dmi.product.version: V1.11 dmi.sys.vendor: Acer ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug groovy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1915117 Title: [Regression] Audio card [8086:9d71] not detected after upgrade from linux 5.4 to 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu version: 20.10 (updated from 20.04) Kernel: 5.8.0-41-generic #46-Ubuntu Manufacturer: Acer Product Name: Swift SF314-54 BIOS Revision: 1.11 Audio card: Realtek High Definition Audio Multimedia audio controller [0401]: Intel Corporation Sunrise Point-LP HD Audio [8086:9d71] (rev 21) Summary === After upgrading from linux kernel 5.4 to 5.8, there is no more sound card available. However, if I select kernel 5.4 in GRUB, the sound card is available. Steps to reproduce == 1. Install 20.04 or 20.10 with a kenel 5.4 2. Check that sound output works as excepted (Settings > Sound > Output > Test) 3. Check that `alsa-info` command returns information 4. Upgrade kernel to 5.8 Expected results Sound output still works. Actual results == 2. Sound card is available, and sound can be output to the internal speakers. 4. No more sound card detected (Sound Settings display "Dummy Output" in the list of output devices). ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-41-generic 5.8.0-41.46 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 14:42:00 2021 InstallationDate: Installed on 2019-01-20 (751 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Acer Swift SF314-54 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-41-generic N/A linux-backports-modules-
[Kernel-packages] [Bug 1878271] Re: rpi: no uboot or kernel boot mesages on console during boot on core20
I have the same issue with the armhf image: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:49:33 UTC 2020 armv7l armv7l armv7l GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 633 latest/beta canonical✓ base pi 20-1 5920/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 153 20/beta canonical✓ kernel snapd 2.45 7779 latest/beta canonical✓ snapd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1878271 Title: rpi: no uboot or kernel boot mesages on console during boot on core20 Status in linux-raspi2 package in Ubuntu: New Bug description: I'm currently testing the image from http://cdimage.ubuntu.com/ubuntu- core/20/beta/20200512.3/ on rpi4-4GB. Normally, we would expect to see uboot prompt on screen, as well as kernel boot messages - as well as on serial. I see all of this coming over serial, but nothing on the screen until the system is completely booted. Current kernel version and snaps in this image are: $ uname -a Linux ubuntu 5.4.0-1011-raspi #11-Ubuntu SMP Fri May 8 07:43:33 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux $ snap list Name VersionRev Tracking Publisher Notes core20 20 635 latest/beta canonical✓ base pi 20-1 5820/beta canonical✓ gadget pi-kernel 5.4.0-1011.11 154 20/beta canonical✓ kernel snapd 2.45 7780 latest/beta canonical✓ snapd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1878271/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing
Installed bluez 5.50 -> same result. Installed linux 5.3 -> same result. Tried a combination of all the linux/bluez possibilites -> same result. Until now, I was only looking at the output of btmon (so basically, low level BT commands). Then, while I was doing one of the tests above, I tailed /var/log/syslog, and I saw this weird thing whenever I tried pairing a BT device (just when it turned from "connected" to immediately "disconnected" in g-c-c): bluetoothd[965]: a2dp-sink profile connect failed for 88:C6:26:1A:9E:AF: Protocol not available bluetoothd[965]: a2dp-source profile connect failed for 88:C6:26:1A:9E:AF: Protocol not available Turns out [1] this is because I was lacking the pulseaudio-module- bluetooth package! After installing it and restarting the device, I can pair and connect my usual BT devices... I don't know why it used to work earlier (while I was already on 20.04) and why it broke one day. I kept upgrading regularly using `sudo apt update` and `sudo apt dist-upgrade`... Anyway, it seems the issue was a non-issue... and I wasted a lot of time investigating it! [1] https://donjajo.com/bluetooth-fix-a2dp-source-profile-connect-failed-xx-protocol-not-available-linux/ ** Changed in: bluez (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: Invalid Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UU
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing
Please find attached my dmesg. I don't see anything related to bluetoothd. The same issue happens with two other BT devices (2 earphones from the same brand, TaoTronics), so I'm pretty confident it's not a BT device issue. Plus, as I mention, it works well with the same hardware (laptop and BT devices) on 19.10 (kernel 5.3 + bluez 5.50). How can I install kernel 5.3 on focal? ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343943/+files/dmesg.log -- 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/1869857 Title: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing Status in bluez package in Ubuntu: New Bug description: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetoo
[Kernel-packages] [Bug 1869857] [NEW] [Intel 7265][Regression] Cannot connect BT earphones or speakers
Public bug reported: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control center, either using bluetoothctl. I've tried with previous versions of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) Subsystem: Intel Corporation Dual Band Wireless-AC 7265 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: iwlwifi Kernel modules: iwlwifi $ dmesg | grep -i bluetooth [ 15.748300] Bluetooth: Core ver 2.22 [ 15.748312] Bluetooth: HCI device and connection manager initialized [ 15.748315] Bluetooth: HCI socket layer initialized [ 15.748317] Bluetooth: L2CAP socket layer initialized [ 15.748320] Bluetooth: SCO socket layer initialized [ 15.925524] Bluetooth: hci0: read Intel version: 370810011003110e00 [ 15.926254] Bluetooth: hci0: Intel Bluetooth firmware file: intel/ibt-h
[Kernel-packages] [Bug 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers
** Attachment added: "5.3.0-18-btmon-speaker.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343689/+files/5.3.0-18-btmon-speaker.log ** Description changed: Laptop: Dell Inspiron 7370 CID: 201704-25503 Ubuntu version: 20.04 daily Linux kernel: 5.4.0-18-generic Bluez: 5.53-0ubuntu2 Summary === BT earphones/speaker cannot be connected either using GNOME control - center, either using bluetoothctl. + center, either using bluetoothctl. I've tried with previous versions of + the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue, + so I believe this is a problem with bluez. However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18, - bluez 5.50) + bluez 5.50), so I think it's a regression in bluez. Steps to reproduce == 1. Open GNOME control center, go to Bluetooth, make sure it's turned on 2. Put the BT device in pairing mode (usually, long press on the Power button) - -> in g-c-c, the device appears as "Not Set Up" (OK) + -> in g-c-c, the device appears as "Not Set Up" (OK) 3. Click on the device to pair it - -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) + -> the device is briefly marked as "Connected", then immediately switches to "Disconnected" (Not OK) The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens when I follow steps 1-3 above. I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez 5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log) Back to Ubuntu 20.04, if I try to pair and connect the device using bluetoothctl, it fails: - $ sudo bluetoothctl + $ sudo bluetoothctl Agent registered [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes [bluetooth]# power on Changing power on succeeded [bluetooth]# pairable on Changing pairable on succeeded [bluetooth]# scan on Discovery started [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes [NEW] Device 88:C6:26:1A:9E:AF UE BOOM [CHG] Device 61:E5:46:38:58:8B RSSI: -86 [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value: - 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... + 0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13 .UV.I... [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87 [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90 [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12 [CHG] Device 56:AE:9C:58:00:BA RSSI: -87 [CHG] Device 56:AE:9C:58:00:BA TxPower: 12 [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86 [CHG] Device 75:79:4D:66:E9:FF RSSI: -81 [CHG] Device 75:79:4D:66:E9:FF TxPower: 12 [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87 [bluetooth]# scan off Discovery stopped [CHG] Controller C8:21:58:B7:2E:82 Discovering: no [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil [CHG] Device 75:79:4D:66:E9:FF TxPower is nil [CHG] Device 75:79:4D:66:E9:FF RSSI is nil [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil [CHG] Device 56:AE:9C:58:00:BA TxPower is nil [CHG] Device 56:AE:9C:58:00:BA RSSI is nil [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil [CHG] Device 61:E5:46:38:58:8B RSSI is nil [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil [bluetooth]# pair 88:C6:26:1A:9E:AF Attempting to pair with 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Connected: yes [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes [CHG] Device 88:C6:26:1A:9E:AF Paired: yes Pairing successful [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no [CHG] Device 88:C6:26:1A:9E:AF Connected: no [bluetooth]# trust 88:C6:26:1A:9E:AF [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes Changing 88:C6:26:1A:9E:AF trust succeeded [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed [bluetooth]# connect 88:C6:26:1A:9E:AF Attempting to connect to 88:C6:26:1A:9E:AF Failed to connect: org.bluez.Error.Failed - - Additional information == $ lspci -vv -s 01:00.0 01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59) - Subsystem: Intel Corporation Dual Band
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
Do you know where I can find the Debian packages for this kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Incomplete Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
Hey Kai-Heng, sorry for the late answer, I didn't have time to look into this issue recently. So I formatted the drive on this device and installed 20.04 dev to see if things improved... they did not. I'm now using kernel 5.4.0-9-generic. The problem still happens, even when I don't suspend the device. Steps to reproduce: 1. Start the device and login 2. Launch Firefox, go to Youtube and put any video in fullscreen, pause mode (so that any touch event will start/pause the video) 3. Wait After a delay (from 2 to 15 minutes), the device starts exhibiting the issue described in the bug. I then have to close the lid to suspend the device, wait a few seconds and reopen the lid. I don't see anything weird in dmesg (attached, saved right after resuming from suspend after the problem occurred). ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+attachment/5323680/+files/dmesg.log ** Tags added: 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/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pn
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
When the issue happens, the device goes crazy and it's impossible to perform any action. I have to close the lid (suspend), wait a few seconds, and open the lid (resume). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856098] [NEW] Laptop suddenly keeps sending random (touchscreen?) input events
Public bug reported: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug eoan hwe-touchscreen wayland-session ** Tags added: hwe-touchscreen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend e
[Kernel-packages] [Bug 1822026] Re: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code)
Confirmed still not working with 19.10 (linux 5.3.0-18-generic) on the Precision 7530. It's actually even worse: now, I can't even boot. I'm just shown a black screen. If I select the Safe graphics boot option, I can boot properly. Editing the default boot command line to include `nouveau.modeset=0` works, but editing it to put `nouveau.runpm=0` instead fails (black screen). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822026 Title: [Nvidia Quadro P1000] Live USB freezes or cannot complete install when nouveau driver is loaded (crashing in gp100/gf100 code) Status in linux package in Ubuntu: Triaged Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Incomplete Bug description: When I boot the Disco 19.04 beta live USB, I can see a lot of errors related to nouveau in dmesg. Because of this, `lspci` freezes, so reporting an issue is impossible either with ubuntu-bug or sosreport (in both cases, the log gathering stops when trying to get the output from lspci). In addition, when nouveau is enabled: - the touchpad becomes unresponsive or behaves in a very weird way (slowing down, jumping), forcing me to use an external mouse or the little pointer in the middle of the keyboard. - the device cannot be powered off or restarted. It freezes and nothing can be done (I tried SysRq+REISUB to no avail) To avoid this issue, I need to launch the live USB with the following command line: $ cat /proc/cmdline BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash modprobe.blacklist=nouveau --- (that is, add `modprobe.blacklist=nouveau` to the command line in Grub) In the BIOS, I activated both GPUs (Intel and nvidia), which is the default settings. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubiquity 19.04.7 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CasperVersion: 1.402 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 28 03:23:52 2019 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash modprobe.blacklist=nouveau --- LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1822026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
Device: XPS 13 7390 Image: 19.10 Final Kernel: 5.3.0-19-generic Mice tested: Logitech M585, Microsoft Designer Mouse The issue is gone. @wysiwyg31: could you give it a try? You can boot a live session of Ubuntu 19.10 on your device and try to pair your Bluetooth mouse. If it works for you, I'll mark the issue as Fix Released. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) Status in linux package in Ubuntu: Confirmed Bug description: Hello, I have an issue with a lenovo yoga mouse. This mouse has 2 working mode either bluetooth or with a provided usb dongle. USB dongle works fine, but bluetooth don't. Cursor is slow and laggy. "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse while USB mode and other mouse reports 125Hz. Polling speed is too slow. I tried different howto suggesting to change usbhid mousepoll value => does not help. The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid killed my other mouse, but not the lenovo, while modprobe -r btusb killed the lenovo). I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and an older dell Precision M6400 16.04 kernel 4.15). Bluetooth pairing works well, either with gnome bluetooth interface or with "bluetoothctl" Both laptops reports ~20-22Hz polling speed with evhz (and same laggy behavior) I also tried 2 bluetooth interface on the XPS13 9370 : the integrated bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the Sabrent, I have switched off integrated bluetooth with rfkill). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 12 18:05:16 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-10 (337 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.7-050007-generic root=UUID=d36c5071-0243-427d-8fe1-7416c3b775f1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2019-03-02 (40 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8B:33:C6 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:12041 acl:294 sco:0 events:363 errors:0 TX bytes:8633 acl:76 sco:0 commands:171 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845454] Re: Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10 (but 5.2 works)
Fixed on Dell XPS 13 7390 with 5.3.0-19.
** Tags added: cqa-verified
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Kernel panic in tpm_ functions when booting kernel 5.3 in Ubuntu 19.10
(but 5.2 works)
Status in linux package in Ubuntu:
Fix Released
Bug description:
SRU Justification
Impact: Some systems are getting kernel panics during boot while
parsing tpm event logs from the firmware. This happens only when the
tpm and secure boot are both enabled in the firmware.
Fix: 3 patches which are currently applied to the upstream EFI
maintainer tree.
Test Case: On an affected system, booting a 5.3-based kernel will
panic during boot when the tpm and secure boot are enabled. A patched
kernel will boot successfully. The patches have been verified to fix
the issue on a gen 6 Lenovo X1 Carbon.
Regression Potential: If the patches have bugs they could cause
regressions on systems not currently experiencing issues. The patches
are pretty straightforward though, so I believe the risk is minimal
and (given the severity of the issue on affected hardware) acceptable.
---
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824559] Re: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency)
Device: XPS 13 7390 Image: 19.10 Beta Kernel: updated to 5.3.0-13-generic (from 5.3.0-10-generic) Mice tested: Logitech M585, Microsoft Designer Mouse With kernel 5.3.0-10-generic (the default on 19.10 beta image), I experience exactly the same issue as originally described. After updating to kernel 5.3.0-13-generic, the issue is gone and both mice cursors respond very smoothly. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1824559 Title: Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) Status in linux package in Ubuntu: Incomplete Bug description: Hello, I have an issue with a lenovo yoga mouse. This mouse has 2 working mode either bluetooth or with a provided usb dongle. USB dongle works fine, but bluetooth don't. Cursor is slow and laggy. "evhz" (https://gitlab.com/iankelling/evhz) reports 22Hz in bluetooth mouse while USB mode and other mouse reports 125Hz. Polling speed is too slow. I tried different howto suggesting to change usbhid mousepoll value => does not help. The mouse seems handled by btusb module, not usbhid (modprobe -r usbhid killed my other mouse, but not the lenovo, while modprobe -r btusb killed the lenovo). I tried 2 laptops (XPS9370 with 18.04, kernel 4.18 and kernek 5.07 and an older dell Precision M6400 16.04 kernel 4.15). Bluetooth pairing works well, either with gnome bluetooth interface or with "bluetoothctl" Both laptops reports ~20-22Hz polling speed with evhz (and same laggy behavior) I also tried 2 bluetooth interface on the XPS13 9370 : the integrated bluetooth and a Sabrent USB Bluetooth 4.0 (to connect with the Sabrent, I have switched off integrated bluetooth with rfkill). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) Uname: Linux 5.0.7-050007-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Apr 12 18:05:16 2019 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-10 (337 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS 13 9370 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.7-050007-generic root=UUID=d36c5071-0243-427d-8fe1-7416c3b775f1 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to bionic on 2019-03-02 (40 days ago) dmi.bios.date: 02/14/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd02/14/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 9C:B6:D0:8B:33:C6 ACL MTU: 1024:8 SCO MTU: 50:8 UP RUNNING PSCAN RX bytes:12041 acl:294 sco:0 events:363 errors:0 TX bytes:8633 acl:76 sco:0 commands:171 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1824559/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
Device: XPS 13 7390
Image: 19.10 Beta
Kernel: updated to 5.3.0-13-generic (from 5.3.0-10-generic)
With kernel 5.3.0-10-generic, the device wouldn't suspend properly when
a BT device was connected to it. After updating to 5.3.0-13-generic, the
issue is gone. I can use a BT mouse, then suspend the device (by
pressing the top-right menu, holding Alt key and clicking the "pause"
button), and the device will indeed suspend and only resume when I press
a key on the keyboard or the power button.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux-oem source package in Bionic:
New
Status in linux source package in Disco:
Fix Committed
Status in linux-oem source package in Disco:
New
Status in linux source package in Eoan:
Fix Committed
Status in linux-oem source package in Eoan:
New
Status in linux source package in FF-Series:
Fix Committed
Status in linux-oem source package in FF-Series:
New
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
*** This bug is a duplicate of bug 1824559 *** https://bugs.launchpad.net/bugs/1824559 ** This bug has been marked a duplicate of bug 1824559 Lenovo Yoga mouse is slow & laggy in bluetooth mode (low polling frequency) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: Confirmed Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
Logs are already captured and available in attachment `sosreport-u-XPS-13-7390-20191001145726.tar.xz`. Marking as `Confirmed`. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: Confirmed Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
Here is a video demonstration. Both mice are already paired and connected. It's not extremely clear on the video, but it's very obvious when using it. ** Attachment added: "bluetooth-mouse-cursor-lag.mp4" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+attachment/5293013/+files/bluetooth-mouse-cursor-lag.mp4 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: New Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+attachment/5293011/+files/version.log ** Description changed: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) + These two mice work fine with another device. + Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: New Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
** Attachment added: "sosreport-u-XPS-13-7390-20191001145726.tar.xz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+attachment/5293009/+files/sosreport-u-XPS-13-7390-20191001145726.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: New Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] Re: Bluetooth mouse cursor very laggy
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+attachment/5293010/+files/lspci-vnvn.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/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: New Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846159] [NEW] Bluetooth mouse cursor very laggy
Public bug reported: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bluetooth ce-qa-concern eoan mouse ** Tags added: bluetooth ce-qa-concern eoan mouse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846159 Title: Bluetooth mouse cursor very laggy Status in linux package in Ubuntu: New Bug description: Image: 19.10 beta – http://cdimage.ubuntu.com/daily-live/20190926.1/eoan-desktop-amd64.iso Device: Dell XPS 13 7390 (201908-27305) Steps to reproduce == 1. Go to Bluetooth Settings 2. Pair a Bluetooth 4 mouse Expected Results Bluetooth mouse is connected and can be used smoothly. Actual Results == Bluetooth mouse is connected, but the cursor movement is very laggy, making it unusable. Failure rate: 100% Tested with 2 different mice: - Logitech M585 - Microsoft Designer Mouse (model 1678) These two mice work fine with another device. Additional Info === $ uname -a Linux u-XPS-13-7390 5.3.0-10-generic #11-Ubuntu SMP Mon Sep 9 15:12:17 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux See sosreport archive for more information To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845454] Re: Dell XPS 13 7390 - Kernel panic with 19.10 beta image
** Tags removed: bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1845454
Title:
Dell XPS 13 7390 - Kernel panic with 19.10 beta image
Status in linux package in Ubuntu:
Incomplete
Bug description:
Image: http://cdimage.ubuntu.com/daily-live/20190926/eoan-desktop-amd64.iso
Device: Dell XPS 13 7390 (201908-27305)
When trying to start the live session ("try Ubuntu") or trying to
install the ISO ("install Ubuntu"), the boot process stops within 1
second with a kernel panic (see attached screenshot).
The system could boot with a previous version of Eoan image:
2019-09-09 09:11 (kernel 5.3.0-10)
Workaround: disable TPM2 in the BIOS.
/!\ Please note: the information below (and the attached file
ProcCpuinfoMinimal.txt) come from a 18.04 live session, since I cannot boot
anything with 19.10 beta image.
==
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: syslinux 3:6.03+dfsg1-2
ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15
Uname: Linux 5.0.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 26 07:41:16 2019
Dependencies:
gcc-8-base 8.3.0-6ubuntu1~18.04.1
libc6 2.27-3ubuntu1
libgcc1 1:8.3.0-6ubuntu1~18.04.1
mtools 4.0.18-2ubuntu1
syslinux-common 3:6.03+dfsg1-2
LiveMediaBuild: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: syslinux
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845454/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
