[Kernel-packages] [Bug 1839857] Re: apic tests fail to run (5 unexpected failures)
This does not happen on X-oracle-4.15 anymore, the apic test is now
failing with bug 1942162 and 1918689
** Changed in: ubuntu-kernel-tests
Status: New => Invalid
** Changed in: linux-oracle (Ubuntu)
Status: New => Invalid
** Changed in: linux-oracle (Ubuntu Xenial)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oracle in Ubuntu.
https://bugs.launchpad.net/bugs/1839857
Title:
apic tests fail to run (5 unexpected failures)
Status in ubuntu-kernel-tests:
Invalid
Status in linux-oracle package in Ubuntu:
Invalid
Status in linux-oracle source package in Xenial:
Invalid
Bug description:
Originally Affected: linux-oracle
Version: 4.15.0-1021.23~16.04.1
Series: Xenial
Apic tests appear to fail to run , with a series of test failures
itself.
08/09 20:46:23 DEBUG| utils:0153| [stdout] starting broadcast (x2apic)
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
address
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: APIC physical broadcast
shorthand
08/09 20:46:23 DEBUG| utils:0153| [stdout] FAIL: PV IPIs testing
08/09 20:46:23 DEBUG| utils:0153| [stdout] PASS: nmi-after-sti
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: multiple nmi
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: APIC LVT timer one shot
08/09 20:46:28 DEBUG| utils:0153| [stdout] starting apic change mode
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMICT value reset
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have
reached 0
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have a
non-zero value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be
reset to TMICT value
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should be reset to
the initial-count
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should not be
reset to init
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should have reach
zero
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: TMCCT should stay at zero
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
08/09 20:46:28 DEBUG| utils:0153| [stdout] PASS: tsc deadline timer
clearing
08/09 20:46:28 DEBUG| utils:0153| [stdout] SUMMARY: 51 tests, 5
unexpected failures
08/09 20:46:28 DEBUG| utils:0153| [stdout] FAIL apic (51 tests, 5
unexpected failures)
08/09 20:46:28 ERROR| test:0414| Exception escaping from test:
Traceback (most recent call last):
File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec
_call_test_function(self.execute, *p_args, **p_dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 823, in
_call_test_function
return func(*args, **dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute
postprocess_profiled_run, args, dargs)
File "/home/ubuntu/autotest/client/shared/test.py", line 212, in
_call_run_once
self.run_once(*args, **dargs)
File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 88, in run_once
raise error.TestError("Test failed for {}".format(test_name))
TestError: Test failed for apic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839857/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942170] [NEW] hirsute/linux-raspi: Upstream raspberrypi patchset 2021-08-26
Public bug reported: Upstream raspberrypi patchset 2021-08-26 Ported from the following raspberrypi branch: rpi-5.10.y from https://github.com/raspberrypi/linux.git ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Assignee: Juerg Haefliger (juergh) Status: New ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1942170 Title: hirsute/linux-raspi: Upstream raspberrypi patchset 2021-08-26 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Hirsute: New Bug description: Upstream raspberrypi patchset 2021-08-26 Ported from the following raspberrypi branch: rpi-5.10.y from https://github.com/raspberrypi/linux.git To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1942170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942168] [NEW] ALX drivers for ethernet card not coming back from Hibernate Suspend
Public bug reported: Whenever ubuntu 20.04 goes to hibernate the network interface cards specifically ethernet does not come back. Its using ALX drivers, similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 I can correct this issue by doing a script that does modprobe -r alx modprobe -i alx Would be nice if this could be taken care of automatically and drivers dont fail after hibernation Description:Ubuntu 20.04.3 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 22:30:49 2021 InstallationDate: Installed on 2021-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1942168 Title: ALX drivers for ethernet card not coming back from Hibernate Suspend Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: Whenever ubuntu 20.04 goes to hibernate the network interface cards specifically ethernet does not come back. Its using ALX drivers, similar to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772 I can correct this issue by doing a script that does modprobe -r alx modprobe -i alx Would be nice if this could be taken care of automatically and drivers dont fail after hibernation Description: Ubuntu 20.04.3 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 22:30:49 2021 InstallationDate: Installed on 2021-08-31 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1942168/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894012] Re: touchpad and keyboard
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521777/+files/version.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/1894012 Title: touchpad and keyboard Status in linux package in Ubuntu: Confirmed Bug description: I reinstalled Ubuntu on 20.04 version in my laptop on an SSD and the keyboard and touch-pad stopped working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorge 1551 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 00:47:37 2020 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: CHUWI INNOVATION LIMITED AeroBook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=4259a678-3627-47b0-81a7-b8449ea7222c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-133-X133KR110-KJ66B-106-N dmi.board.asset.tag: Default string dmi.board.name: AeroBook dmi.board.vendor: CHUWI INNOVATION LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: CHUWI INNOVATION LIMITED dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-133-X133KR110-KJ66B-106-N:bd09/20/2019:svnCHUWIINNOVATIONLIMITED:pnAeroBook:pvrDefaultstring:rvnCHUWIINNOVATIONLIMITED:rnAeroBook:rvrDefaultstring:cvnCHUWIINNOVATIONLIMITED:ct10:cvrDefaultstring: dmi.product.family: YZ106 dmi.product.name: AeroBook dmi.product.sku: YZ106 dmi.product.version: Default string dmi.sys.vendor: CHUWI INNOVATION LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894012] Re: touchpad and keyboard
Confirmed also on HP EliteBook 2570p, after upgrade from 19.04 laptop keyboard/touch-pad are not working except GRUB menu and safe mode. I was not able to find which kernel module cause this. ** Attachment added: "dmi.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521755/+files/dmi.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/1894012 Title: touchpad and keyboard Status in linux package in Ubuntu: Confirmed Bug description: I reinstalled Ubuntu on 20.04 version in my laptop on an SSD and the keyboard and touch-pad stopped working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorge 1551 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 00:47:37 2020 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: CHUWI INNOVATION LIMITED AeroBook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=4259a678-3627-47b0-81a7-b8449ea7222c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-133-X133KR110-KJ66B-106-N dmi.board.asset.tag: Default string dmi.board.name: AeroBook dmi.board.vendor: CHUWI INNOVATION LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: CHUWI INNOVATION LIMITED dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-133-X133KR110-KJ66B-106-N:bd09/20/2019:svnCHUWIINNOVATIONLIMITED:pnAeroBook:pvrDefaultstring:rvnCHUWIINNOVATIONLIMITED:rnAeroBook:rvrDefaultstring:cvnCHUWIINNOVATIONLIMITED:ct10:cvrDefaultstring: dmi.product.family: YZ106 dmi.product.name: AeroBook dmi.product.sku: YZ106 dmi.product.version: Default string dmi.sys.vendor: CHUWI INNOVATION LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894012] Re: touchpad and keyboard
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+attachment/5521756/+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/1894012 Title: touchpad and keyboard Status in linux package in Ubuntu: Confirmed Bug description: I reinstalled Ubuntu on 20.04 version in my laptop on an SSD and the keyboard and touch-pad stopped working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-generic 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-generic 5.4.55 Uname: Linux 5.4.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jorge 1551 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 3 00:47:37 2020 InstallationDate: Installed on 2020-09-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: CHUWI INNOVATION LIMITED AeroBook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-generic root=UUID=4259a678-3627-47b0-81a7-b8449ea7222c ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-generic N/A linux-backports-modules-5.4.0-45-generic N/A linux-firmware1.187.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YZ-BI-133-X133KR110-KJ66B-106-N dmi.board.asset.tag: Default string dmi.board.name: AeroBook dmi.board.vendor: CHUWI INNOVATION LIMITED dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: CHUWI INNOVATION LIMITED dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYZ-BI-133-X133KR110-KJ66B-106-N:bd09/20/2019:svnCHUWIINNOVATIONLIMITED:pnAeroBook:pvrDefaultstring:rvnCHUWIINNOVATIONLIMITED:rnAeroBook:rvrDefaultstring:cvnCHUWIINNOVATIONLIMITED:ct10:cvrDefaultstring: dmi.product.family: YZ106 dmi.product.name: AeroBook dmi.product.sku: YZ106 dmi.product.version: Default string dmi.sys.vendor: CHUWI INNOVATION LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1894012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521746/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521748/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521751/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521750/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521752/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521740/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521739/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521754/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521745/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521738/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521747/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521743/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521741/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521753/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521749/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521744/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1942160/+attachment/5521742/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1942160 Title: PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: New Status in linux source package in Impish: New Status in linux-oem-5.13 source package in Impish: Invalid Bug description: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1942160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942160] [NEW] PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
Public bug reported: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:464d] (rev 05) Kernel driver in use: pcieport 1:e1:00.0 Non-Volatile memory controller [0108]: Intel Corporation Device [8086:f1aa] (rev 03) Subsystem: Intel Corporation Device [8086:390f] Kernel driver in use: nvme Kernel modules: nvme * ADL-P: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.0 0604: 8086:51b0 (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:f1a8 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ * ADL-S: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:1d.4 0604: 8086:7ab4 (rev 10) (prog-if 00 [Normal decode]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ 1:e1:00.0 0108: 8086:0975 (rev 03) (prog-if 02 [NVM Express]) LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+ See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889384 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1100 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-04-06 (146 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0032 Intel Corp. Bus 001 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel Corporation Alder Lake Client Platform Package: linux-firmware 1.187.16+staging.11 [origin: unknown] PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-9010-oem root=UUID=e38f9e97-de55-4524-ba5b-a0ae4d5ea8a7 ro i915.force_probe=4680 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-9010.11+staging.9-oem 5.13.1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-9010-oem N/A linux-backports-modules-5.13.0-9010-oem N/A linux-firmware 1.187.16+staging.11 Tags: focal third-party-packages Uname: Linux 5.13.0-9010-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLSFWI1.R00.2181.A00.2104261003 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-S ADP-S DDR5 UDIMM CRB dmi.board.vendor: Intel Corporation dmi.board.version: 2 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnIntelCorporation:bvrADLSFWI1.R00.2181.A00.2104261003:bd04/26/2021:efr1.36:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku1004002B0100:rvnIntelCorporation:rnAlderLake-SADP-SDDR5UDIMMCRB:rvr2:cvnIntelCorporation:ct3:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 1004002B0100 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: apport-collected focal oem-priority originate-from-1942030 somerville third-party-packages ** Also affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Tags added: oem-priority originate-from-1942030 somerville ** Tags added: apport-collected focal third-party-packages ** Description changed: * ADL-M: $ sudo lspci -vvn | grep -E '^(1|\s+LnkCtl:)' 1:e0:06.0 PCI bridge [0604]: Intel Corporation
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
https://lists.ubuntu.com/archives/kernel-team/2021-August/123672.html
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
+ ...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
+
It can fix our test failure plus, as mentioned in the commit message,
emulation failures with openbsd as guest and with Windows 10 with
intel HD graphics pass through.
-
- I didn't see any other patch that claims to be a fix of this one in
- upstream tree.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
+ ...
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
- The problem I think of for the moment is that we might see other
- failures when using this in the future.
+ I didn't see any other patch that claims to be a fix of this one in
+ the upstream tree. The problem I think of for the moment is that we
+ might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11
[Kernel-packages] [Bug 1837937] Re: CRASH
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837937 Title: CRASH Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: The screen froze but the mouse was still moving then it all froze and said systemd-journal not able to write entry. I had to press the power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-9-generic 5.2.0-9.10 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 Uname: Linux 5.2.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2068 F pulseaudio /dev/snd/controlC0: administrator 2068 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Jul 25 15:11:47 2019 InstallationDate: Installed on 2019-06-05 (50 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-9-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.2.0-9.10-generic 5.2.1 RelatedPackageVersions: linux-restricted-modules-5.2.0-9-generic N/A linux-backports-modules-5.2.0-9-generic N/A linux-firmware 1.181 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: eoan Uname: Linux 5.2.0-9-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.24 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 82F6 dmi.board.vendor: HP dmi.board.version: 40.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.24:bd06/15/2017:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn82F6:rvr40.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.sku: X7T78UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: administrator 2852 F pulseaudio /dev/snd/controlC0: administrator 2852 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-05 (51 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190605) MachineType: HP HP Notebook Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR=
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
- I didn't see any other patch claim to be a fix of this patch in upstream tree.
+ It can fix our test failure plus, mentioned in the commit message, emulation
failures with openbsd as guest and with Windows 10 with intel HD graphics pass
through.
+
+ I didn't see any other patch claim to be a fix of this patch in upstream
+ tree.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
+ It's just adding new capabilities, the problem I think of for the moment is
that we might see other failures when using this in the future.
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr]
[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
Thanks BinLi, Also confirmed cdc_mbim with Quectel modem OK. ** Also affects: usb-modeswitch (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Invalid Status in network-manager package in Ubuntu: New Status in usb-modeswitch package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940504] Re: Support Alder Lake P graphics
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-firmware source package in Focal: New Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
- PASS: movdqu (read)^M
- PASS: movdqu (write)^M
- PASS: movaps (read)^M
- PASS: movaps (write)^M
- PASS: movapd (read)^M
- PASS: movapd (write)^M
+ PASS: movdqu (read)
+ PASS: movdqu (write)
+ PASS: movaps (read)
+ PASS: movaps (write)
+ PASS: movapd (read)
+ PASS: movapd (write)
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
- * 6ce08235f2 kvm: Add emulation for movups/movupd
+ * 29916968c48691 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
I didn't see any other patch claim to be a fix of this patch in upstream tree.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
+
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG|
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
PASS: movdqu (read)^M
PASS: movdqu (write)^M
PASS: movaps (read)^M
PASS: movaps (write)^M
PASS: movapd (read)^M
PASS: movapd (write)^M
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 6ce08235f2 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
- There is no other patch that claims to be a fix of this one.
+ I didn't see any other patch claim to be a fix of this patch in upstream tree.
[Test]
Test kernel can be found here:
https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
Run the emulator test from ubuntu_kvm_unit_tests, with this patch
applied it will pass without any issue:
PASS: movdqu (read)
PASS: movdqu (write)
PASS: movaps (read)
PASS: movaps (write)
PASS: movapd (read)
PASS: movapd (write)
PASS: movups (read)
PASS: movups (write)
PASS: movupd (read)
PASS: movupd (write)
PASS: movups unaligned
PASS: movupd unaligned
PASS: unaligned movaps exception
PASS: movups unaligned crosspage
PASS: movups crosspage exception
PASS: movq (mmx, read)
PASS: movq (mmx, write)
PASS: movb $imm, 0(%rip)
PASS: shld (cl)
PASS: shrd (cl)
PASS: mov null, %ss
PASS: mov null, %ss (with ss.rpl != cpl)
PASS: Test ret/iret with a nullified segment
PASS: ltr
PASS: cmovnel
SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
PASS: push16
PASS: cross-page mmio read
PASS: cross-page mmio write
PASS: string_io_mmio
PASS: jump to non-canonical address
SKIP: illegal movbe
SUMMARY: 135 tests, 2 skipped
PASS emulator (135 tests, 2 skipped)
[Where problems could occur]
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00
[Kernel-packages] [Bug 1906128] Re: Touchpad not detected on ByteSpeed C15B laptop
Patch already in Hirsute, closing this bug.
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1906128
Title:
Touchpad not detected on ByteSpeed C15B laptop
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Bug description:
[Impact]
Touchpad on a ByteSpeed C15B laptop is not working.
User will need to add i8042.noloop=1 to boot options to make it work.
[Fix]
* a48491c65b513e ("Input: i8042 - add ByteSpeed touchpad to noloop table")
This fix can be cherry-picked into all affected releases.
[Test Case]
Test kernel for Bionic / Focal can be found here:
https://people.canonical.com/~phlin/kernel/lp-1906128-C15B/
And they have been tested with positive test results.
[Where problems could occur]
The fix is just a small and simple hardware quirk. I can't think of any
potential problem for now.
== Original Bug Report ==
Touchpad hardware is OK and works for Win10. Not working for live disc, not
for 18.04 and not for 20.04 after upgrading. I've attached a Logitech wireless
mouse with its USB adapter and that works. Bluetooth is also missing, but I
have not started trying to skull that out. I'm happy to help try debugging
things, and to help resolve the issue.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-54-generic 5.4.0-54.60
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: tom1395 F pulseaudio
/dev/snd/controlC0: tom1395 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 28 19:09:05 2020
InstallationDate: Installed on 2020-01-26 (307 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: ByteSpeed LLC ByteSpeed Laptop C15B
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic
root=UUID=07b919ee-c6ad-41a5-9c64-df3c8e477b6f ro quiet splash i8042.reset
i8042.nomux i8042.nopnp i8042noloop noapic vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-54-generic N/A
linux-backports-modules-5.4.0-54-generic N/A
linux-firmware1.187.4
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to focal on 2020-11-25 (3 days ago)
dmi.bios.date: 03/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: C15B.616
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: C15B
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: ByteSpeed LLC
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrC15B.616:bd03/18/2014:svnByteSpeedLLC:pnByteSpeedLaptopC15B:pvr1.0:rvnPEGATRONCORPORATION:rnC15B:rvr1.0:cvnByteSpeedLLC:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: PEGA Family
dmi.product.name: ByteSpeed Laptop C15B
dmi.product.sku: 0
dmi.product.version: 1.0
dmi.sys.vendor: ByteSpeed LLC
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1906128/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
PASS: movdqu (read)^M
PASS: movdqu (write)^M
PASS: movaps (read)^M
PASS: movaps (write)^M
PASS: movapd (read)^M
PASS: movapd (write)^M
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 6ce08235f2 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
+ There is no other patch that claims to be a fix of this one.
[Test]
- Run the emulator test from ubuntu_kvm_unit_tests, with this patch applied it
will pass without any issue:
+ Test kernel can be found here:
+ https://people.canonical.com/~phlin/kernel/lp-1932966-kvm-emulator/
- PASS: movdqu (read)
- PASS: movdqu (write)
- PASS: movaps (read)
- PASS: movaps (write)
- PASS: movapd (read)
- PASS: movapd (write)
- PASS: movups (read)
- PASS: movups (write)
- PASS: movupd (read)
- PASS: movupd (write)
- PASS: movups unaligned
- PASS: movupd unaligned
- PASS: unaligned movaps exception
- PASS: movups unaligned crosspage
- PASS: movups crosspage exception
- PASS: movq (mmx, read)
- PASS: movq (mmx, write)
- PASS: movb $imm, 0(%rip)
- PASS: shld (cl)
- PASS: shrd (cl)
- PASS: mov null, %ss
- PASS: mov null, %ss (with ss.rpl != cpl)
- PASS: Test ret/iret with a nullified segment
- PASS: ltr
- PASS: cmovnel
- SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
- PASS: push16
- PASS: cross-page mmio read
- PASS: cross-page mmio write
- PASS: string_io_mmio
- PASS: jump to non-canonical address
- SKIP: illegal movbe
- SUMMARY: 135 tests, 2 skipped
- PASS emulator (135 tests, 2 skipped)
+ Run the emulator test from ubuntu_kvm_unit_tests, with this patch
+ applied it will pass without any issue:
+
+ PASS: movdqu (read)
+ PASS: movdqu (write)
+ PASS: movaps (read)
+ PASS: movaps (write)
+ PASS: movapd (read)
+ PASS: movapd (write)
+ PASS: movups (read)
+ PASS: movups (write)
+ PASS: movupd (read)
+ PASS: movupd (write)
+ PASS: movups unaligned
+ PASS: movupd unaligned
+ PASS: unaligned movaps exception
+ PASS: movups unaligned crosspage
+ PASS: movups crosspage exception
+ PASS: movq (mmx, read)
+ PASS: movq (mmx, write)
+ PASS: movb $imm, 0(%rip)
+ PASS: shld (cl)
+ PASS: shrd (cl)
+ PASS: mov null, %ss
+ PASS: mov null, %ss (with ss.rpl != cpl)
+ PASS: Test ret/iret with a nullified segment
+ PASS: ltr
+ PASS: cmovnel
+ SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
+ PASS: push16
+ PASS: cross-page mmio read
+ PASS: cross-page mmio write
+ PASS: string_io_mmio
+ PASS: jump to non-canonical address
+ SKIP: illegal movbe
+ SUMMARY:
[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Triaged ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Triaged Bug description: The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. For ranges the interface understands it can provide a DMA mapped sg_table for use by the ib_umem, allowing user virtual ranges that cannot be supported by get_user_pages() to be used as umems for RDMA. This is designed to preserve the kABI, no functions or structures are changed, only new symbols are added: ib_register_peer_memory_client ib_unregister_peer_memory_client ib_umem_activate_invalidation_notifier ib_umem_get_peer And a bitfield in struct ib_umem uses more bits. This interface is compatible with the two out of tree GPU drivers: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837833] Re: EBS Volumes get stuck detaching from AWS instances
Hi test0830, This particular issue was fixed by AWS on their backend, it wasn't an issue with Ubuntu at all. If you are having similar issues, you should open a new bug or a support ticket on AWS. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837833 Title: EBS Volumes get stuck detaching from AWS instances Status in linux package in Ubuntu: Fix Released Bug description: On AWS, it is possible to get a EBS volume stuck in the detaching state, where it is not present in lsblk or lspci, but the cloud console says the volume is detaching, and pci / nvme errors are output to dmesg every 180 seconds. To reproduce reliably: 1) Start a AWS instance. Can be any type, nitro or regular. I have successfully reproduced on m5.large and t3.small. Add an extra volume during creation, of any size. 2) Connect to the instance. lsblk and lspci show the nvme device there. Detach the volume from the web console. It will detach successfully. You can attach and then detach the volume again, and it will also work successfully. 3) With the volume detached, reboot the instance. I do "sudo reboot". 4) When the instance comes back up and you have logged in, attach the volume. dmesg will have (normal): kernel: [ 67] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 67] pci :00:1f.0: reg 0x10: [mem 0x-0x3fff] kernel: [ 67] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 67] nvme nvme1: pci function :00:1f.0 kernel: [ 67] nvme :00:1f.0: enabling device ( -> 0002) kernel: [ 67] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 5) Detach the volume from the web console. If you keep refreshing the volume view, you will see the volume in the detaching state and the volume is still in use. The device will be missing from lsblk and lspci. dmesg will print these messages every 180 seconds: 4.4 -> 4.15 kernel: [ 603] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 603] pci :00:1f.0: reg 0x10: [mem 0x8000-0x80003fff] kernel: [ 603] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 603] nvme nvme1: pci function :00:1f.0 kernel: [ 603] nvme nvme1: failed to mark controller live kernel: [ 603] nvme nvme1: Removing after probe failure status: 0 Latest mainline kernel: kernel: [ 243] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 243] pci :00:1f.0: reg 0x10: [mem 0xc000-0xc0003fff] kernel: [ 243] pci :00:1f.0: BAR 0: assigned [mem 0xc000-0xc0003fff] kernel: [ 243] nvme nvme1: pci function :00:1f.0 kernel: [ 244] nvme nvme1: failed to mark controller CONNECTING kernel: [ 244] nvme nvme1: Removing after probe failure status: 0 The volume is now stuck detaching and the above will continue until you forcefully detach the volume. This seems to effect all distributions and all kernels. I have tested xenial, bionic, bionic + hwe, bionic + eoan, bionic + mainline 5.2.2, rhel8 and Amazon Linux 2. All are affected with the same symptoms. I tried to trace NVMe on 5.2, but with not much success on finding any problem: https://paste.ubuntu.com/p/c6rmDpvHJk/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942133] Re: Nvidia driver packages prevent suspend due to leftover Systemd units
** Description changed: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. I whink that, when attempting to suspend, the error is logged as this (edited): - ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying - upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying - dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") - systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE - systemd[1]: systemd-logind.service: Failed with result 'exit-code'. - systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. - systemd[1]: Stopped Login Service. - systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. - systemd[1]: Starting Login Service... + ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying + upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying + dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") + systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE + systemd[1]: systemd-logind.service: Failed with result 'exit-code'. + systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. + systemd[1]: Stopped Login Service. + systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. + systemd[1]: Starting Login Service... I've deleted the problematic symlinks while trying to solving the problem, however, they should be these: /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service + + I've briefly checked before removing them; at least a couple of them + were masked, but they were still causing the problem. I don't see any reason why they should hang around the systemd configuration once the packages are purged. Additionally, this is a problem that is not easy to diagnose. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: MATE Date: Mon Aug 30 21:10:52 2021 LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942133 Title: Nvidia driver packages prevent suspend due to leftover Systemd units Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. I whink that, when attempting to suspend, the error is logged as this (edited): ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") systemd[1]: systemd-logind.service: Main process exited,
[Kernel-packages] [Bug 1942133] [NEW] Nvidia driver packages prevent suspend due to leftover Systemd units
Public bug reported: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. I whink that, when attempting to suspend, the error is logged as this (edited): ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: systemd-logind.service: Failed with result 'exit-code'. systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. systemd[1]: Stopped Login Service. systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. systemd[1]: Starting Login Service... I've deleted the problematic symlinks while trying to solving the problem, however, they should be these: /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service I don't see any reason why they should hang around the systemd configuration once the packages are purged. Additionally, this is a problem that is not easy to diagnose. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-driver-470 (not installed) ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445.1 CurrentDesktop: MATE Date: Mon Aug 30 21:10:52 2021 LiveMediaBuild: Ubuntu-MATE 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-470 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Description changed: When the nvidia driver packages are uninstalled, they leave some symlinks that prevent suspend. - I've deleted them while figuring out what the problem was, however, they - should be these: + I whink that, when attempting to suspend, the error is logged as this + (edited): - /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service - /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service - /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service - /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service + ModemManager[3287]: [sleep-monitor] inhibit failed: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying + upowerd[5771]: Could not acquire inhibitor lock: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying + dbus-daemon[2888]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.53' (uid=1000 pid=8227 comm="/usr/lib/x86_64-linux-gnu/indicator-session/indica" label="unconfined") + systemd[1]: systemd-logind.service: Main process exited, code=exited, status=1/FAILURE + systemd[1]: systemd-logind.service: Failed with result 'exit-code'. + systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 7. + systemd[1]: Stopped Login Service. + systemd[1]: Condition check resulted in Load Kernel Module drm being skipped. + systemd[1]: Starting Login Service... - There's not reason to leave them once the driver is uninstalled, and - it's hard to figure out the problem, so they should go away when the - packages are uninstalled. + I've deleted the problematic symlinks while trying to solving the + problem, however, they should be these: + + /etc/systemd/system/systemd-suspend-service.requires/nvidia-suspend.service + /etc/systemd/system/systemd-suspend-service.requires/nvidia-resume.service + /etc/systemd/system/systemd-hibernate-service.requires/nvidia-suspend.service + /etc/systemd/system/systemd-hibernate-service.requires/nvidia-resume.service + + I don't see any reason why they should
[Kernel-packages] [Bug 1939543] Re: Power button no longer has any action after applying updates
Please also run "acpi_listen" and "sudo showkey" to check whether power button events are generated by system BIOS and linux kernel correctly. ** Attachment added: "Screenshot-20210830150034.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+attachment/5521717/+files/Screenshot-20210830150034.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939543 Title: Power button no longer has any action after applying updates Status in linux package in Ubuntu: Confirmed Bug description: When using the live iso image or first install, the power button will either prompt to shut down or sleep depending how the user has it configured in the power settings. however after applying updates the power button no longer does anything. Pressing and holding for 10 seconds will perform the hardware power off (as expected). Software wise, nothing happens. I have had this on 3 pc's now and also on your previous version of Ubuntu Budgie so this is not a new issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diddy 1273 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Aug 11 11:27:26 2021 InstallationDate: Installed on 2021-08-09 (1 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera Bus 001 Device 002: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=6dcedb6d-17fc-4ddc-a907-27b3074282b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP111J.fLHAUGX01.2012039 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 10.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP111J.fLHAUGX01.2012039:bd12/29/2020:br5.12:efr10.2:svnJumper:pnEZbook:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.name: EZbook dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939543] Re: Power button no longer has any action after applying updates
Please check whether action for power button is modified. ** Attachment added: "Screenshot-20210830145942.png" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+attachment/5521716/+files/Screenshot-20210830145942.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939543 Title: Power button no longer has any action after applying updates Status in linux package in Ubuntu: Confirmed Bug description: When using the live iso image or first install, the power button will either prompt to shut down or sleep depending how the user has it configured in the power settings. however after applying updates the power button no longer does anything. Pressing and holding for 10 seconds will perform the hardware power off (as expected). Software wise, nothing happens. I have had this on 3 pc's now and also on your previous version of Ubuntu Budgie so this is not a new issue. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27 ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: diddy 1273 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Wed Aug 11 11:27:26 2021 InstallationDate: Installed on 2021-08-09 (1 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp. USB Camera Bus 001 Device 002: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Jumper EZbook ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=6dcedb6d-17fc-4ddc-a907-27b3074282b2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.197.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/29/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Jumper10x.WP111J.fLHAUGX01.2012039 dmi.board.asset.tag: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 10.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrJumper10x.WP111J.fLHAUGX01.2012039:bd12/29/2020:br5.12:efr10.2:svnJumper:pnEZbook:pvrDefaultstring:rvn:rn:rvrDefaultstring:cvnDefaultstring:ct31:cvrDefaultstring: dmi.product.name: EZbook dmi.product.version: Default string dmi.sys.vendor: Jumper To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939543/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942123] Re: Hirsute update: upstream stable patchset 2021-08-30
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ upstream stable patchset 2021-08-30
-upstream stable patchset 2021-08-30
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v5.10.57, v5.13.9
+ v5.10.58, v5.13.10
+
+ from git://git.kernel.org/
+
+ drm/i915: Revert "drm/i915/gem: Asynchronous cmdparser"
+ Revert "drm/i915: Propagate errors on awaiting already signaled fences"
+ regulator: rtmv20: Fix wrong mask for strobe-polarity-high
+ regulator: rt5033: Fix n_voltages settings for BUCK and LDO
+ spi: stm32h7: fix full duplex irq handler handling
+ ASoC: tlv320aic31xx: fix reversed bclk/wclk master bits
+ r8152: Fix potential PM refcount imbalance
+ qed: fix possible unpaired spin_{un}lock_bh in _qed_mcp_cmd_and_union()
+ ASoC: rt5682: Fix the issue of garbled recording after powerd_dbus_suspend
+ net: Fix zero-copy head len calculation.
+ ASoC: ti: j721e-evm: Fix unbalanced domain activity tracking during startup
+ ASoC: ti: j721e-evm: Check for not initialized parent_clk_id
+ efi/mokvar: Reserve the table only if it is in boot services data
+ nvme: fix nvme_setup_command metadata trace event
+ drm/amd/display: Fix comparison error in dcn21 DML
+ drm/amd/display: Fix max vstartup calculation for modes with borders
+ Revert "Bluetooth: Shutdown controller after workqueues are flushed or
cancelled"
+ firmware: arm_scmi: Add delayed response status check
+ Revert "watchdog: iTCO_wdt: Account for rebooting on second timeout"
+ selftest/bpf: Adjust expected verifier errors
+ bpf, selftests: Adjust few selftest result_unpriv outcomes
+ bpf: Update selftests to reflect new error states
+ bpf, selftests: Adjust few selftest outcomes wrt unreachable code
+ selftest/bpf: Verifier tests for var-off access
+ spi: mediatek: Fix fifo transfer
+ cifs: use helpers when parsing uid/gid mount options and validate them
+ cifs: add missing parsing of backupuid
+ net: dsa: sja1105: parameterize the number of ports
+ ASoC: Intel: boards: handle hda-dsp-common as a module
+ UBUNTU: [Config] updateconfigs for SND_SOC_INTEL_HDA_DSP_COMMON
+ ASoC: Intel: boards: create sof-maxim-common module
+ UBUNTU: [Config] updateconfigs for SND_SOC_INTEL_SOF_MAXIM_COMMON
+ ASoC: Intel: boards: fix xrun issue on platform with max98373
+ r8152: Fix a deadlock by doubly PM resume
+ UBUNTU: upstream stable to v5.10.57, v5.13.9
+ Revert "ACPICA: Fix memory leak caused by _CID repair function"
+ ALSA: seq: Fix racy deletion of subscriber
+ bus: ti-sysc: Fix gpt12 system timer issue with reserved status
+ net: xfrm: fix memory leak in xfrm_user_rcv_msg
+ arm64: dts: ls1028a: fix node name for the sysclk
+ ARM: imx: add missing iounmap()
+ ARM: imx: add missing clk_disable_unprepare()
+ ARM: dts: imx6qdl-sr-som: Increase the PHY reset duration to 10ms
+ arm64: dts: ls1028: sl28: fix networking for variant 2
+ ARM: dts: colibri-imx6ull: limit SDIO clock to 25MHz
+ ARM: imx: fix missing 3rd argument in macro imx_mmdc_perf_init
+ ARM: dts: imx: Swap M53Menlo pinctrl_power_button/pinctrl_power_out pins
+ arm64: dts: armada-3720-turris-mox: fixed indices for the SDHC controllers
+ arm64: dts: armada-3720-turris-mox: remove mrvl,i2c-fast-mode
+ ALSA: usb-audio: fix incorrect clock source setting
+ clk: stm32f4: fix post divisor setup for I2S/SAI PLLs
+ ARM: dts: am437x-l4: fix typo in can@0 node
+ omap5-board-common: remove not physically existing vdds_1v8_main
fixed-regulator
+ dmaengine: uniphier-xdmac: Use readl_poll_timeout_atomic() in atomic state
+ clk: tegra: Implement disable_unused() of tegra_clk_sdmmc_mux_ops
+ dmaengine: stm32-dma: Fix PM usage counter imbalance in stm32 dma ops
+ dmaengine: stm32-dmamux: Fix PM usage counter unbalance in stm32 dmamux ops
+ spi: imx: mx51-ecspi: Reinstate low-speed CONFIGREG delay
+ spi: imx: mx51-ecspi: Fix low-speed CONFIGREG delay calculation
+ scsi: sr: Return correct event when media event code is 3
+ media: videobuf2-core: dequeue if start_streaming fails
+ ARM: dts: stm32: Disable
[Kernel-packages] [Bug 1942123] Re: Hirsute update: upstream stable patchset 2021-08-30
** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942123 Title: Hirsute update: upstream stable patchset 2021-08-30 Status in linux package in Ubuntu: Invalid Status in linux source package in Hirsute: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-30 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942123] [NEW] Hirsute update: upstream stable patchset 2021-08-30
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-30 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942123 Title: Hirsute update: upstream stable patchset 2021-08-30 Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2021-08-30 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942123/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
Hi Chris, both are working, no kernel panic. Regards Cédric On 8/30/21 10:26 AM, Chris Chiu wrote: > The new logs still belongs to 5.13.8 so there's no panic information. > Since there's no difference on hid and input drivers between 5.13.8 and > 5.13.9. I can try to do bisection to find out the possible culprit. > Could you help test the following kernel and give me your test results? > Thanks > > https://people.canonical.com/~mschiu77/lp1941773/3cadaeae64dc/ > https://people.canonical.com/~mschiu77/lp1941773/base/ > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
The patched focal master-next kernel sources are available as PR from here: https://code.launchpad.net/~fheimes/+git/lp1939618 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939618 Title: CryptoExpress EP11 cards are going offline Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941950] Re: linux-riscv: missing kernel signature
The RISC-V platform specification requires UEFI. Secure boot is defined in the UEFI specification. With U-Boot, Shim, GRUB, and a signed kernel I am able demonstrate secure boot on RISC-V. I am upstreaming the necessary patches. Roots of trust for RISC-V are in active development but not yet available on commercial boards: Cf. https://riscv.org/wp-content/uploads/2019/03/15.05-RISC-V-Security-Multizone-v-TrustZone-3-12-19.pdf Canonical has started discussing with SiFive how a root of trust can be supplied. A boot ROM checking the first bootstage (U-Boot SPL) using a certificate from the OTP memory would be a good start. This only requires a software change on the vendor side. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1941950 Title: linux-riscv: missing kernel signature Status in linux-riscv package in Ubuntu: New Bug description: U-Boot and EDK II both support secure boot. But vmlinuz-5.11.0-1014-generic and vmlinuz-5.13.0-1002-generic are not signed via sbsign. Please, adjust the RISC-V build system to sign new kernels. Best regards Heinrich To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1941950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
diff stat graph that provides an indication where the changes mainly are: arch/s390/appldata/appldata_os.c | 2 +- arch/s390/include/asm/sclp.h | 2 + arch/s390/include/uapi/asm/zcrypt.h| 140 +++--- drivers/s390/block/dasd_diag.c | 2 +- drivers/s390/block/dasd_eckd.h | 2 +- drivers/s390/char/Makefile | 2 + drivers/s390/char/raw3270.h| 2 +- drivers/s390/char/sclp.h | 2 +- drivers/s390/char/sclp_ap.c| 63 +++ drivers/s390/char/sclp_pci.c | 2 +- drivers/s390/cio/idset.c | 2 +- drivers/s390/crypto/ap_bus.c | 974 +++- drivers/s390/crypto/ap_bus.h | 139 +++-- drivers/s390/crypto/ap_card.c | 98 ++-- drivers/s390/crypto/ap_debug.h | 8 + drivers/s390/crypto/ap_queue.c | 513 +++ drivers/s390/crypto/pkey_api.c | 20 +- drivers/s390/crypto/zcrypt_api.c | 574 ++--- drivers/s390/crypto/zcrypt_api.h | 49 +- drivers/s390/crypto/zcrypt_card.c | 30 +- drivers/s390/crypto/zcrypt_ccamisc.c | 320 ++-- drivers/s390/crypto/zcrypt_ccamisc.h | 32 +- drivers/s390/crypto/zcrypt_cex2a.c | 8 +- drivers/s390/crypto/zcrypt_cex2c.c | 164 +- drivers/s390/crypto/zcrypt_cex4.c | 197 drivers/s390/crypto/zcrypt_debug.h | 8 + drivers/s390/crypto/zcrypt_ep11misc.c | 41 +- drivers/s390/crypto/zcrypt_error.h | 92 ++-- drivers/s390/crypto/zcrypt_msgtype50.c | 179 +++ drivers/s390/crypto/zcrypt_msgtype6.c | 374 +++--- drivers/s390/crypto/zcrypt_msgtype6.h | 8 +- drivers/s390/crypto/zcrypt_queue.c | 26 +- -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939618 Title: CryptoExpress EP11 cards are going offline Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940113] Re: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected
There are no deb packages in the first link (rc1). The rc2 version started and worked without problem with the dock and the two screens. ** Attachment added: "journalctl.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+attachment/5521666/+files/journalctl.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/1940113 Title: Linux 5.11.0-25 & 5.11.0-27 panic when boot with thunderbolt dock connected Status in linux package in Ubuntu: Confirmed Bug description: Hello, My laptop run well with last 5.4 linux kernel even if I connect my thunderbolt dock. When trying to boot with 5.11.0-25 or 5.11.0-27 (hwe) kernel with dock and 2 monitors connected, the kernel panic after 3 or 4 seconds. Without the dock, he work fine. After a lot of try, I was able to boot sometime on 5.11 with the dock, but randomly and only if I only connect 1 extra monitor (I usually use two). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jmaillar 1988 F pulseaudio /dev/snd/controlC1: jmaillar 1988 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none MachineType: Dell Inc. Precision 7530 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic root=UUID=b21fab6e-02fe-4295-a308-9da15f339a36 ro ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-27-generic N/A linux-backports-modules-5.11.0-27-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-27-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-04-20 (483 days ago) UserGroups: adm audio cdrom dip disk input kismet kvm libvirt libvirtd lpadmin lxd netdev plugdev sambashare sudo systemd-network users vboxusers video wireshark _MarkForUpload: True dmi.bios.date: 05/25/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.1 dmi.board.name: 0425K7 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.1:bd05/25/2021:br1.16:svnDellInc.:pnPrecision7530:pvr:rvnDellInc.:rn0425K7:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 7530 dmi.product.sku: 0831 dmi.sys.vendor: Dell Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2015-11-27T14:42:56.796345 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Until Kernel will be officially released, just use these: https://people.canonical.com/~hwang4/9710/ sudo dpkg -i linux-image- unsigned-5.11.0-33-generic_5.11.0-33.35_amd64.deb linux- modules-5.11.0-33-generic_5.11.0-33.35_amd64.deb linux-modules- extra-5.11.0-33-generic_5.11.0-33.35_amd64.deb Dell XPS 9710 works in Ubuntu 20.04/21.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
A patched kernel (based on 5.4.0-84, current focal master-next) got built and is available for further testing here: https://launchpad.net/~fheimes/+archive/ubuntu/lp1939618 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939618 Title: CryptoExpress EP11 cards are going offline Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940504] Please test proposed package
Hello Timo, or anyone else affected, Accepted mesa into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mesa/21.0.3-0ubuntu0.3~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940504] Re: Support Alder Lake P graphics
Hello Timo, or anyone else affected, Accepted libdrm into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libdrm/2.4.105-3~20.04.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libdrm (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal ** Changed in: mesa (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1940504 Title: Support Alder Lake P graphics Status in libdrm package in Ubuntu: Fix Released Status in linux-oem-5.13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in libdrm source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: NOTE: this is for focal only, hirsute/impish do not and will not have kernel support for this. [Impact] ADL-P machines need to use the native driver. [Fix] Backport support from upstream. libdrm: a single patch from 2.4.107 mesa: three commits to add pci-id's and a workaround kernel: needs drm sync from 5.14 (bug 1940085) plus additional backports [Test case] Boot a machine and check that it's using the native driver and that the usual workloads are fine. [Where things could go wrong] For older gpu's there's little to go wrong, since the commits are for ADL-P only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1940504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Please test proposed package
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Please test proposed package
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.2-1ubuntu0.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939618] Re: CryptoExpress EP11 cards are going offline
** Summary changed: - EP11 cards going offline => Fix backport to U20.04LTS + CryptoExpress EP11 cards are going offline -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939618 Title: CryptoExpress EP11 cards are going offline Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Here is the backport against current git for ubuntu 20.04. It is a zip file with a patches subdir and all the patches in there together with a series file. So just unpack it and apply with quilt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1939618/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
Hello Hui, or anyone else affected, Accepted alsa-ucm-conf into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-ucm- conf/1.2.4-2ubuntu1.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags added: verification-needed verification-needed-hirsute ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942092] [NEW] linux-azure: main(): sched_setscheduler(): Operation not permitted
Public bug reported: [Impact] We have several regressions with RT and ADT with the azure kernels. The tests seem to fail when calling sched_setscheduler() or with related operations. This was probably introduced by LP:#1939024 that enabled CONFIG_RT_GROUP_SCHED. We should revert this change until we better understand the impact it can cause. * ubuntu_ltp_stable The ltp syscall regression test is failing for all the azure kernels with: main(): sched_setscheduler(): Operation not permitted http://10.246.75.167/2021.08.16/hirsute/linux-azure/5.11.0-1014.15/sru- azure-azure-Standard_A2_v2-ubuntu_ltp_stable-log.txt * ubuntu_qrt_apparmor Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' Error: syscall_setscheduler failed. Test 'syscall_setscheduler -- unconfined' was expected to 'pass'. Reason for failure 'FAIL: Can't set SCHED_RR: Operation not permitted' * systemd ADT (Hirsute) https://autopkgtest.ubuntu.com/results/autopkgtest- hirsute/hirsute/amd64/s/systemd/20210827_233206_a2599@/log.gz [Test Plan] The kernel should pass the regression and adt tests. [Where problems could occur] ** Affects: ubuntu-kernel-tests Importance: Undecided Assignee: Marcelo Cerri (mhcerri) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-5.4 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-5.8 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Trusty) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.11 (Ubuntu Trusty) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.4 (Ubuntu Trusty) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.8 (Ubuntu Trusty) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.11 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.4 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.8 (Ubuntu Xenial) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: linux-azure-4.15 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-azure-5.11 (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-azure-5.8 (Ubuntu Bionic) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.11 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-azure-5.4 (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.8 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Hirsute) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.11 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.4 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-azure-5.8 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Tags: 4.15 5.11 5.4 azure bionic focal hirsute kqa-blocker sru-20210816 trusty ubuntu-ltp-stable ubuntu-qrt-apparmor xenial ** Tags added: 4.15 5.11 5.4 azure bionic focal hirsute kqa-blocker sru-20210816 trusty ubuntu-ltp-stable ubuntu-qrt-apparmor xenial ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure-5.4 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure-5.11 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure
[Kernel-packages] [Bug 1941999] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1941999 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941999 Title: ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error Status in linux package in Ubuntu: Incomplete Bug description: Since kernel 5.4.0-80 of ubuntu20.04, unloading of kernel module of amdgpu became an error and could not be done. modprobe -s -r amdgpu It can be unloaded up to kernel 5.4.0-77 without any problem. Can be unloaded with kernel 5.8.0-63 without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942088] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942088 Title: Touchpad not recognized in Samsung NP550XDA Status in linux package in Ubuntu: Confirmed Bug description: Laptop: Samsung NP550XDA-KS1BR Ubuntu 20.04 Laptop had windows 10 pre-installed. Then I installed ubuntu 18.04 and upgrade it to 20.04. The touchpad never worked in none. 2 things: In the BIOS the touchpad works normally. And it used to work at Windows OS. cat /proc/bus/input/devices > ~/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=500f02000403 3803078f870d001 fedffbef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=24ae Product=1100 Version=0110 N: Name="RAPOO Rapoo 2.4G Wireless Device" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/0003:24AE:1100.0001/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=13d3 Product=5a24 Version=2012 N: Name="VGA camera: VGA camera" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-7/3-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: m 1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:54:58 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=aa140181-87e8-4760-b79a-6cc7eeffbc45 ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-26 (3 days ago) dmi.bios.date: 04/10/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P06CFB.032.210410.HQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XDA-KS1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA915A03-C01-G001-S0001+10.0.19042 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP06CFB.032.210410.HQ:bd04/10/2021:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP06CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KS1BR:rvrSGLA915A03-C01-G001-S0001+10.0.19042:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook Plus2 dmi.product.name: 550XDA dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB dmi.product.version: P06CFB dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1941999] Re: ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error
** Package changed: ubuntu => linux (Ubuntu) ** 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/1941999 Title: ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error Status in linux package in Ubuntu: New Bug description: Since kernel 5.4.0-80 of ubuntu20.04, unloading of kernel module of amdgpu became an error and could not be done. modprobe -s -r amdgpu It can be unloaded up to kernel 5.4.0-77 without any problem. Can be unloaded with kernel 5.8.0-63 without any problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942088] [NEW] Touchpad not recognized in Samsung NP550XDA
Public bug reported: Laptop: Samsung NP550XDA-KS1BR Ubuntu 20.04 Laptop had windows 10 pre-installed. Then I installed ubuntu 18.04 and upgrade it to 20.04. The touchpad never worked in none. 2 things: In the BIOS the touchpad works normally. And it used to work at Windows OS. cat /proc/bus/input/devices > ~/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 U: Uniq= H: Handlers=kbd event2 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input4 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=500f02000403 3803078f870d001 fedffbef fffe B: MSC=10 B: LED=7 I: Bus=0003 Vendor=24ae Product=1100 Version=0110 N: Name="RAPOO Rapoo 2.4G Wireless Device" P: Phys=usb-:00:14.0-1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-1/3-1:1.0/0003:24AE:1100.0001/input/input5 U: Uniq= H: Handlers=mouse0 event4 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=903 B: MSC=10 I: Bus=0003 Vendor=13d3 Product=5a24 Version=2012 N: Name="VGA camera: VGA camera" P: Phys=usb-:00:14.0-7/button S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-7/3-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1f.3/sound/card0/input7 U: Uniq= H: Handlers=event6 B: PROP=0 B: EV=21 B: SW=4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-81-generic 5.4.0-81.91 ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128 Uname: Linux 5.4.0-81-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: m 1439 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:54:58 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: SAMSUNG ELECTRONICS CO., LTD. 550XDA ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic root=UUID=aa140181-87e8-4760-b79a-6cc7eeffbc45 ro quiet splash i8042.nopnp=1 pci=nocrs vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-81-generic N/A linux-backports-modules-5.4.0-81-generic N/A linux-firmware1.187.16 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-26 (3 days ago) dmi.bios.date: 04/10/2021 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: P06CFB.032.210410.HQ dmi.board.asset.tag: No Asset Tag dmi.board.name: NP550XDA-KS1BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: SGLA915A03-C01-G001-S0001+10.0.19042 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP06CFB.032.210410.HQ:bd04/10/2021:svnSAMSUNGELECTRONICSCO.,LTD.:pn550XDA:pvrP06CFB:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP550XDA-KS1BR:rvrSGLA915A03-C01-G001-S0001+10.0.19042:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A: dmi.product.family: Notebook Plus2 dmi.product.name: 550XDA dmi.product.sku: SCAI-A5A5-A5A5-TGL3-PCFB dmi.product.version: P06CFB dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942088 Title: Touchpad not recognized in Samsung NP550XDA Status in linux package in Ubuntu: New Bug description: Laptop: Samsung NP550XDA-KS1BR Ubuntu 20.04 Laptop had windows 10 pre-installed. Then I installed ubuntu 18.04 and upgrade it to 20.04. The touchpad never worked in none. 2 things: In the BIOS the touchpad works normally. And it used to work at Windows OS. cat /proc/bus/input/devices > ~/devices I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0
[Kernel-packages] [Bug 1942060] Re: ath11k firmware and driver crash
The crash seems to be caused by VHT160. With VHT80 configured at the AP no crash happens. -- 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/1942060 Title: ath11k firmware and driver crash Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: When connecting with WLAN, the firmware and driver keeps crashing with kernel 5.10.0-1044-oem. This happens in an environment with many WLANs when connecting to a certain AP. It works OK with kernel 5.6.0.1047-oem. In other locations, WLAN works OK with the 5.10.0-1044-oem kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1044-oem 5.10.0-1044.46 ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19 Uname: Linux 5.6.0-1047-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:04:30 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/1942060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942080] Re: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000
** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942080 Title: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000 Status in OEM Priority Project: In Progress Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Split from bug LP: #1940262 The following modalias of RTX A5000 (notably, for Dell OEM) is missing: pci:v10DEd2231sv1028sd147Ebc03sc00i00 This results in ubuntu-drivers not suggesting nvidia-driver-470. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941999] [NEW] ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error
You have been subscribed to a public bug: Since kernel 5.4.0-80 of ubuntu20.04, unloading of kernel module of amdgpu became an error and could not be done. modprobe -s -r amdgpu It can be unloaded up to kernel 5.4.0-77 without any problem. Can be unloaded with kernel 5.8.0-63 without any problems. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ubuntu 20.04 kernel 5.4.0-80 modprobe -r amdgpu error https://bugs.launchpad.net/bugs/1941999 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu4 --- alsa-ucm-conf (1.2.4-2ubuntu4) impish; urgency=medium * d/p/0006-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0007-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 10:36:38 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
This bug was fixed in the package alsa-ucm-conf - 1.2.4-2ubuntu4 --- alsa-ucm-conf (1.2.4-2ubuntu4) impish; urgency=medium * d/p/0006-sof-soundwire-rt1316-DAC-L-and-R-is-replaced-by-DAC.patch The mixer name is changed in the codec driver rt1316-sdw.c, so need to handle the new mixer name. https://github.com/alsa-project/alsa-ucm-conf/pull/109 (LP: #1937980) * d/p/0007-sof-hda-dsp-Set-Capture-Switch-on-in-the-BootSequenc.patch The input volume of the external microphone is 0 by default for all machines with sof audio driver, that is because the capture switch is set to off by default, need to set it to on in the ucm. https://github.com/alsa-project/alsa-ucm-conf/pull/107 (LP: #1940788) -- Hui Wang Mon, 23 Aug 2021 10:36:38 +0800 ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Released Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
KDE NEON 5.22 Kernel Version 5.11.0.27-generic Issue still with dummy output Dell 9710 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: In Progress Status in linux source package in Hirsute: In Progress Status in linux source package in Impish: In Progress Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942080] Re: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000
https://github.com/tseliot/nvidia-graphics-drivers/pull/40 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942080 Title: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Split from bug LP: #1940262 The following modalias of RTX A5000 (notably, for Dell OEM) is missing: pci:v10DEd2231sv1028sd147Ebc03sc00i00 This results in ubuntu-drivers not suggesting nvidia-driver-470. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940262] Re: The modalias in 470 is not compatible to 460
Splitting RTX A5000 from Dell to LP: #1942080 ** Tags removed: originate-from-1941823 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1940262 Title: The modalias in 470 is not compatible to 460 Status in OEM Priority Project: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Fix Committed Bug description: There are many modalias be removed from 470 those supporting in 460. If 470 is a LTS version and 460 will be transited to 470 then the driver installing will have different behavior between both version. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1940262/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942080] [NEW] ubuntu-driver should suggest nvidia-driver-470 for RTX A5000
Public bug reported: Split from bug LP: #1940262 The following modalias of RTX A5000 (notably, for Dell OEM) is missing: pci:v10DEd2231sv1028sd147Ebc03sc00i00 This results in ubuntu-drivers not suggesting nvidia-driver-470. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1941823 somerville ** Tags added: oem-priority originate-from-1941823 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1942080 Title: ubuntu-driver should suggest nvidia-driver-470 for RTX A5000 Status in OEM Priority Project: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Split from bug LP: #1940262 The following modalias of RTX A5000 (notably, for Dell OEM) is missing: pci:v10DEd2231sv1028sd147Ebc03sc00i00 This results in ubuntu-drivers not suggesting nvidia-driver-470. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1782709] Re: Updating systemd kills network on bionic
I changed my networking setup to use netplan and the problem disappeared. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1782709 Title: Updating systemd kills network on bionic Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: I do have an ubuntu bionic server installation without a graphical interface. The server has two active network adapters, both connected to the internet. One is used for outgoing internet traffic, the other for incoming. The incoming adapter lives on a public network segment (something like 88.236.133.104/29). I do have multiple servers within this segment. Typically, I update the server regularly, meaning: * ssh to the incoming adapter: ssh 88.236.133.108 * apt-get update * apt-get upgrade * apt-get dist-upgrade * apt-get clean * reboot It used to work ok. BUT: Today, "apt-get upgrade" seem to take really long when updating systemd. After a could of minutes, I realized that the ssh session became inactive. I couldn't type into it, I had to abort it via ~. . * ssh from the internet to the incoming adapter was not working anymore - ssh 88.236.133.108 * ssh via another server within the public network segment worked * ssh 88.236.133.106 -> ssh 88.236.133.108 * After running "netplan apply" everything was fine again Here my netplan configuration (I changed the ip addresses): network: version: 2 renderer: networkd ethernets: eno1: dhcp4: yes eno2: dhcp4: no addresses: [88.236.133.108/29] #gateway4: 88.236.133.105 routes: - to: 0.0.0.0/0 via: 88.236.133.105 table: 120 routing-policy: - from: 88.236.133.108/32 table: 120 - to: 88.236.133.108/32 table: 120 Unfortunately, I don't have the console output avalable anymore. Shall I provide additional info? Best regards, Uli --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 20 08:10 seq crw-rw 1 root audio 116, 33 Jul 20 08:10 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-14 (5 days ago) InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: IBM IBM System x -[794582G]- Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic root=UUID=a41b3020-8359-4fe2-8fc3-1c97011f71ec ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/07/2014 dmi.bios.vendor: IBM Corp. dmi.bios.version: -[D6E162AUS-1.20]- dmi.board.asset.tag: (none) dmi.board.name: 00D4062 dmi.board.vendor: IBM dmi.board.version: (none) dmi.chassis.asset.tag: none dmi.chassis.type: 23 dmi.chassis.vendor: IBM dmi.chassis.version: none dmi.modalias: dmi:bvnIBMCorp.:bvr-[D6E162AUS-1.20]-:bd05/07/2014:svnIBM:pnIBMSystemx-[794582G]-:pvr00:rvnIBM:rn00D4062:rvr(none):cvnIBM:ct23:cvrnone: dmi.product.family: System x dmi.product.name: IBM System x -[794582G]- dmi.product.version: 00 dmi.sys.vendor: IBM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1782709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925261] Re: memory leak on AWS kernels when using docker
Hi Paul - I'm having trouble figuring out exactly which kernel you're
using. The backport of commit a308c71bf1e6e19cc2e4ced31853ee0fc7cb439a
("mm/gup: Remove enfornced COW mechanism") to Focal:linux-aws
5.4.0-1056.59 is not clean, and doesn't look correct. There are likely
prerequisite patches required before
a308c71bf1e6e19cc2e4ced31853ee0fc7cb439a can be applied. I'm leery of
patching the mm subsystem too much since it could have unintended side
effects.
Have you considered using the Focal:linux-aws-5.11 kernel ? I understand
that could be a big change.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1925261
Title:
memory leak on AWS kernels when using docker
Status in linux-aws package in Ubuntu:
New
Status in linux-aws source package in Focal:
New
Bug description:
Ever since the "ubuntu-bionic-18.04-amd64-server-20200729" EC2 Ubuntu
AMI was released which has the "5.3.0-1032-aws" kernel we have been
hitting a 100% repro memory leak that causes our app that is running
under docker to be OOM killed.
The scenario is that we have an app running in a docker container and
it occasionally catches a crash happening within itself and when that
happens it creates another process which triggers a gdb dump of that
parent app. Normally this works fine but under these specific kernels
it causes the memory usage to grow and grow until it hits the maximum
allowed memory for the container at which point the container is
killed.
I have tested using several of the latest available Ubuntu AMIs
including the latest "ubuntu-bionic-18.04-amd64-server-20210415" which
has the "5.4.0-1045-aws" kernel and the bug still exists.
I also tested a bunch of the mainline kernels and found the fix was
introduced for this memory leak in the v5.9-rc4 kernel
(https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9-rc4/CHANGES).
Do you all have any idea if or when that set of changes will be
backported into a supported kernel for Ubuntu 18.04 or 20.04?
Release we are running:
root@:~# lsb_release -rd
Description: Ubuntu 18.04.5 LTS
Release: 18.04
Docker / containerd.io versions:
- containerd.io: 1.4.4-1
- docker-ce: 5:20.10.5~3-0~ubuntu-bionic
Latest supported kernel I tried which still sees the memory leak:
root@hostname:~# apt-cache policy linux-aws
linux-aws:
Installed: 5.4.0.1045.27
Candidate: 5.4.0.1045.27
Version table:
*** 5.4.0.1045.27 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu
bionic-updates/main amd64 Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64
Packages
100 /var/lib/dpkg/status
4.15.0.1007.7 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu bionic/main amd64
Packages
Thanks,
Paul
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1925261/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
[Impact]
Our Bionic 4.15 kernel lacks of movups/movupd emulation support.
With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
Author: Jacob Xu
Date: Wed Apr 21 16:12:57 2021 -0700
x86: add movups/movupd sse testcases to emulator.c
Here we add movups/movupd tests corresponding to functionality
introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
Signed-off-by: Jacob Xu
Message-Id: <20210421231258.2583654-1-jacob...@google.com>
Signed-off-by: Paolo Bonzini
It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
PASS: movdqu (read)^M
PASS: movdqu (write)^M
PASS: movaps (read)^M
PASS: movaps (write)^M
PASS: movapd (read)^M
PASS: movapd (write)^M
KVM internal error. Suberror: 1
emulation failure
RAX=000a RBX=e000 RCX=03fd
RDX=03f8
RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
R8 =000a R9 =03f8 R10=000d
R11=
R12=e000 R13= R14=d000
R15=
RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
ES =0010 00c09300 DPL=0 DS [-WA]
CS =0008 00a09b00 DPL=0 CS64 [-RA]
SS =0010 00c09300 DPL=0 DS [-WA]
DS =0010 00c09300 DPL=0 DS [-WA]
FS =0010 00c09300 DPL=0 DS [-WA]
GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
LDT= 8200 DPL=0 LDT
TR =0080 0041207a 8b00 DPL=0 TSS64-busy
GDT= 0041100a 106f
IDT= 0041 0fff
CR0=80010011 CR2= CR3=01007000 CR4=0220
DR0= DR1= DR2=
DR3=
DR6=0ff0 DR7=0400
EFER=0500
Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8 07
qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
FAIL emulator (timeout; duration=90s)
[Fix]
* 6ce08235f2 kvm: Add emulation for movups/movupd
This patch can be cherry-picked into Bionic.
+ [Test]
+ Run the emulator test from ubuntu_kvm_unit_tests, with this patch applied it
will pass without any issue:
+
+ PASS: movdqu (read)
+ PASS: movdqu (write)
+ PASS: movaps (read)
+ PASS: movaps (write)
+ PASS: movapd (read)
+ PASS: movapd (write)
+ PASS: movups (read)
+ PASS: movups (write)
+ PASS: movupd (read)
+ PASS: movupd (write)
+ PASS: movups unaligned
+ PASS: movupd unaligned
+ PASS: unaligned movaps exception
+ PASS: movups unaligned crosspage
+ PASS: movups crosspage exception
+ PASS: movq (mmx, read)
+ PASS: movq (mmx, write)
+ PASS: movb $imm, 0(%rip)
+ PASS: shld (cl)
+ PASS: shrd (cl)
+ PASS: mov null, %ss
+ PASS: mov null, %ss (with ss.rpl != cpl)
+ PASS: Test ret/iret with a nullified segment
+ PASS: ltr
+ PASS: cmovnel
+ SKIP: skipping register-only tests, use kvm.force_emulation_prefix=1 to
enable
+ PASS: push16
+ PASS: cross-page mmio read
+ PASS: cross-page mmio write
+ PASS: string_io_mmio
+ PASS: jump to non-canonical address
+ SKIP: illegal movbe
+ SUMMARY: 135 tests, 2 skipped
+ PASS emulator (135 tests, 2 skipped)
+
+ [Where problems could occur]
+
+
[Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010
[Kernel-packages] [Bug 1837833] Re: EBS Volumes get stuck detaching from AWS instances
Hello @mruffell , How to find this patch for this problem? thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837833 Title: EBS Volumes get stuck detaching from AWS instances Status in linux package in Ubuntu: Fix Released Bug description: On AWS, it is possible to get a EBS volume stuck in the detaching state, where it is not present in lsblk or lspci, but the cloud console says the volume is detaching, and pci / nvme errors are output to dmesg every 180 seconds. To reproduce reliably: 1) Start a AWS instance. Can be any type, nitro or regular. I have successfully reproduced on m5.large and t3.small. Add an extra volume during creation, of any size. 2) Connect to the instance. lsblk and lspci show the nvme device there. Detach the volume from the web console. It will detach successfully. You can attach and then detach the volume again, and it will also work successfully. 3) With the volume detached, reboot the instance. I do "sudo reboot". 4) When the instance comes back up and you have logged in, attach the volume. dmesg will have (normal): kernel: [ 67] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 67] pci :00:1f.0: reg 0x10: [mem 0x-0x3fff] kernel: [ 67] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 67] nvme nvme1: pci function :00:1f.0 kernel: [ 67] nvme :00:1f.0: enabling device ( -> 0002) kernel: [ 67] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10 5) Detach the volume from the web console. If you keep refreshing the volume view, you will see the volume in the detaching state and the volume is still in use. The device will be missing from lsblk and lspci. dmesg will print these messages every 180 seconds: 4.4 -> 4.15 kernel: [ 603] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 603] pci :00:1f.0: reg 0x10: [mem 0x8000-0x80003fff] kernel: [ 603] pci :00:1f.0: BAR 0: assigned [mem 0x8000-0x80003fff] kernel: [ 603] nvme nvme1: pci function :00:1f.0 kernel: [ 603] nvme nvme1: failed to mark controller live kernel: [ 603] nvme nvme1: Removing after probe failure status: 0 Latest mainline kernel: kernel: [ 243] pci :00:1f.0: [1d0f:8061] type 00 class 0x010802 kernel: [ 243] pci :00:1f.0: reg 0x10: [mem 0xc000-0xc0003fff] kernel: [ 243] pci :00:1f.0: BAR 0: assigned [mem 0xc000-0xc0003fff] kernel: [ 243] nvme nvme1: pci function :00:1f.0 kernel: [ 244] nvme nvme1: failed to mark controller CONNECTING kernel: [ 244] nvme nvme1: Removing after probe failure status: 0 The volume is now stuck detaching and the above will continue until you forcefully detach the volume. This seems to effect all distributions and all kernels. I have tested xenial, bionic, bionic + hwe, bionic + eoan, bionic + mainline 5.2.2, rhel8 and Amazon Linux 2. All are affected with the same symptoms. I tried to trace NVMe on 5.2, but with not much success on finding any problem: https://paste.ubuntu.com/p/c6rmDpvHJk/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837833/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Description changed:
+ [Impact]
+ Our Bionic 4.15 kernel lack of movups/movupd emulation support.
+
+ With the following commit added into the emulator test in
ubuntu_kvm_unit_tests:
+ 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9 is the first bad commit
+ commit 8726f9771911d6749dbd36ab2fc70f0f25e2b1a9
+ Author: Jacob Xu
+ Date: Wed Apr 21 16:12:57 2021 -0700
+
+ x86: add movups/movupd sse testcases to emulator.c
+
+ Here we add movups/movupd tests corresponding to functionality
+ introduced in commit 29916968c486 ("kvm: Add emulation for
movups/movupd").
+
+ Signed-off-by: Jacob Xu
+ Message-Id: <20210421231258.2583654-1-jacob...@google.com>
+ Signed-off-by: Paolo Bonzini
+
+
+ It will cause the emulator test in ubuntu_kvm_unit_tests fail with timeout:
+ PASS: movdqu (read)^M
+ PASS: movdqu (write)^M
+ PASS: movaps (read)^M
+ PASS: movaps (write)^M
+ PASS: movapd (read)^M
+ PASS: movapd (write)^M
+ KVM internal error. Suberror: 1
+ emulation failure
+ RAX=000a RBX=e000 RCX=03fd
RDX=03f8
+ RSI=00419991 RDI=00419991 RBP=0051b490
RSP=0051b470
+ R8 =000a R9 =03f8 R10=000d
R11=
+ R12=e000 R13= R14=d000
R15=
+ RIP=00400a1f RFL=00010006 [-P-] CPL=0 II=0 A20=1 SMM=0 HLT=0
+ ES =0010 00c09300 DPL=0 DS [-WA]
+ CS =0008 00a09b00 DPL=0 CS64 [-RA]
+ SS =0010 00c09300 DPL=0 DS [-WA]
+ DS =0010 00c09300 DPL=0 DS [-WA]
+ FS =0010 00c09300 DPL=0 DS [-WA]
+ GS =0010 0051a510 00c09300 DPL=0 DS [-WA]
+ LDT= 8200 DPL=0 LDT
+ TR =0080 0041207a 8b00 DPL=0 TSS64-busy
+ GDT= 0041100a 106f
+ IDT= 0041 0fff
+ CR0=80010011 CR2= CR3=01007000 CR4=0220
+ DR0= DR1= DR2=
DR3=
+ DR6=0ff0 DR7=0400
+ EFER=0500
+ Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66 0f 6f 45 e0 <0f> 11 03
48 89 de 48 8d 7d e0 e8 e5 f9 ff ff 0f b6 f8 be a1 8f 41 00 b8 00 00 00 00 e8
07
+ qemu-system-x86_64: terminating on signal 15 from pid 15758 (timeout)
+ FAIL emulator (timeout; duration=90s)
+
+
+ [Fix]
+ * 6ce08235f2 kvm: Add emulation for movups/movupd
+
+ This patch can be cherry-picked into Bionic.
+
+
+
+ [Original Bug Report]
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
- 18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
+ 18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40
[Kernel-packages] [Bug 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.
After debug, this issue is not related to kernel. cdc_ether was unregistered by usb-modeswitch. After I installed the old verison of usb-modeswitch, this issue is fixed, it looks like a regression. Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwan0: register 'cdc_ether' at usb-:00:14.0-9, Mobile Broadband Network Device, 02:1e:10:1f:00:00 Aug 30 05:54:32 u-ThinkPad-L460 kernel: usbcore: registered new interface driver cdc_ether Aug 30 05:54:32 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: renamed from wwan0 Aug 30 05:54:33 u-ThinkPad-L460 kernel: cdc_ether 1-9:2.0 wwx021e101f: unregister 'cdc_ether' usb-:00:14.0-9, Mobile Broadband Network Device -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940377 Title: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute. Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: New Bug description: u@u-ThinkPad-L460:~$ uname -a Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux u@u-ThinkPad-L460:~$ cat /etc/issue Ubuntu 21.04 \n \l CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module [Steps] 1. Make a Live CD for Ubuntu Hirsute 2. Plug in the Live CD 3. Boot ThinkPad L460 4. Install Ubuntu Hirsute and completed all configurations 5. Make sure the installation done 6. Boot the system and log in 7. Enable the proposed channel 8. Do the update and upgrade 9. Reboot the system and check mmcli is upgraded to 1.16.6 7. Verify the WWAN working or not. [Actual result] The WWAN can not be detected. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: ubuntu-release-upgrader-core 1:21.04.16 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu Date: Wed Aug 18 01:32:17 2021 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-18 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) IpRoute: default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 169.254.0.0/16 dev wlp3s0 scope link metric 1000 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.30.0-1ubuntu3 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.30.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1940377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939528] Re: Need support of Qualcomm WCN6856
latest ath11k firmware from
https://github.com/kvalo/ath11k-firmware/commit/443060f416bc71e3cc9dbd105cbaf86c66906d82
and board file from
https://chromium.googlesource.com/chromiumos/third_party/linux-
firmware/+/d233ddd89abe06448070471963a58c0a7da81d79
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1939528
Title:
Need support of Qualcomm WCN6856
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-firmware package in Ubuntu:
New
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Incomplete
Status in linux-oem-5.13 source package in Focal:
Incomplete
Status in linux source package in Hirsute:
Won't Fix
Status in linux-firmware source package in Hirsute:
New
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Incomplete
Status in linux-firmware source package in Impish:
New
Status in linux-oem-5.13 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Qualcomm WCN6856 not supported yet.
[Fix]
Upstream fixes in thread
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
has been merged in mainline starting from commit 755b1f73173e ("ath11k:
add hw reg support for WCN6855").
[Test Case]
TBD.
[Where problems could occur]
While this introduces a new hardware, it might need further polishments.
== original bug report ==
Wireless Driver support: PCI\VEN_17CB_1103_E0B8105B_01
BT driver support: USB\VID_0489_E0C9_0001
Wireless Driver support: PCI\VEN_17CB_1103_01
BT driver support: USB\VID_0489_E0CC_0001
https://lore.kernel.org/linux-wireless/20210511162214.29475-8-jo...@codeaurora.org/
Already landed to mainline kernel v5.14-rc1.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939528/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
dpkg: erreur: cannot access archive '*-generic*.deb': Aucun fichier ou dossier de ce type -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932966] Re: kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
** Package changed: linux-kvm (Ubuntu) => linux (Ubuntu)
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: ubuntu-kernel-tests
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1932966
Title:
kvm_unit_tests: emulator test fails on 4.15 kernel, timeout
Status in ubuntu-kernel-tests:
In Progress
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
In Progress
Bug description:
Found this on B/KVM, current cycle (sru-20210531):
18:27:11 DEBUG| [stdout] PASS: movapd (write)^M
18:27:11 DEBUG| [stderr] KVM internal error. Suberror: 1
18:27:11 DEBUG| [stderr] emulation failure
18:27:11 DEBUG| [stderr] RAX=000a RBX=e000
RCX=03fd RDX=03f8
18:27:11 DEBUG| [stderr] RSI=00419991 RDI=00419991
RBP=0051b440 RSP=0051b420
18:27:11 DEBUG| [stderr] R8 =000a R9 =03f8
R10=000d R11=
18:27:11 DEBUG| [stderr] R12=e000 R13=
R14=d000 R15=
18:27:11 DEBUG| [stderr] RIP=00400a0c RFL=00010006 [-P-] CPL=0
II=0 A20=1 SMM=0 HLT=0
18:27:11 DEBUG| [stderr] ES =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] CS =0008 00a09b00 DPL=0
CS64 [-RA]
18:27:11 DEBUG| [stderr] SS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] DS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] FS =0010 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] GS =0010 0051a4d0 00c09300 DPL=0 DS
[-WA]
18:27:11 DEBUG| [stderr] LDT= 8200 DPL=0 LDT
18:27:11 DEBUG| [stderr] TR =0080 0041207a 8b00 DPL=0
TSS64-busy
18:27:11 DEBUG| [stderr] GDT= 0041100a 106f
18:27:11 DEBUG| [stderr] IDT= 0041 0fff
18:27:11 DEBUG| [stderr] CR0=80010011 CR2=
CR3=01007000 CR4=0220
18:27:11 DEBUG| [stderr] DR0= DR1=
DR2= DR3=
18:27:11 DEBUG| [stderr] DR6=0ff0 DR7=0400
18:27:11 DEBUG| [stderr] EFER=0500
18:27:11 DEBUG| [stderr] Code=00 c7 45 e8 03 00 00 00 c7 45 ec 04 00 00 00 66
0f 6f 45 e0 <0f> 11 03 48 89 de 48 8d 7d e0 e8 f8 f9 ff ff 0f b6 f8 be a1 8f 41
00 b8 00 00 00 00 e8 05
18:28:40 DEBUG| [stderr] qemu-system-x86_64: terminating on signal 15 from
pid 13634 (timeout)
18:28:40 DEBUG| [stdout] FAIL emulator (timeout; duration=90s)
[...]
TestError: Test failed for emulator
18:28:40 ERROR| child process failed
18:28:40 DEBUG| Traceback (most recent call last):
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/parallel.py", line 25,
in fork_start
18:28:40 DEBUG| l()
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/job.py", line 505, in
18:28:40 DEBUG| l = lambda: test.runtest(self, url, tag, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/test.py", line 125, in
runtest
18:28:40 DEBUG| job.sysinfo.log_after_each_iteration)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
913, in runtest
18:28:40 DEBUG| mytest._exec(args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
411, in _exec
18:28:40 DEBUG| _call_test_function(self.execute, *p_args, **p_dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
823, in _call_test_function
18:28:40 DEBUG| return func(*args, **dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
291, in execute
18:28:40 DEBUG| postprocess_profiled_run, args, dargs)
18:28:40 DEBUG| File "/home/ubuntu/autotest/client/shared/test.py", line
212, in _call_run_once
18:28:40 DEBUG| self.run_once(*args, **dargs)
18:28:40 DEBUG| File
"/home/ubuntu/autotest/client/tests/ubuntu_kvm_unit_tests/ubuntu_kvm_unit_tests.py",
line 82, in run_once
18:28:40 DEBUG| raise error.TestError("Test failed for
{}".format(test_name))
18:28:40 DEBUG| TestError: Test failed for emulator
18:28:41 INFO | ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun 18
18:28:41 Test failed for emulator
18:28:41 INFO | END ERROR ubuntu_kvm_unit_tests.emulator
ubuntu_kvm_unit_tests.emulator timestamp=1624040921localtime=Jun
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
Upload to hirsute and focal as well now ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1894017] Re: Keyboard not working
I just typed a long email in reply to someone asking about the keyboard not working by email. The contents of that email are likely useful for other people who are still experiencing the keyboard not working too, so I've copy and pasted my entire reply below. If you still need help with this please follow the provided debug instructions and provide the requested info. ### First of all lets see if we can find the root cause. Bug 1894017 is about the keyboard events being discarded in userspace, because userspace thinks the device is folded in tablet mode with the keyboard behind the display (and any key-presses are thus done accidentally). Please install evemu and then run: sudo evemu-record This will give you a list of available input devices. The problems reported in bug #1894017 are caused by a false-positive reporting of SW_TABLET_MODE with a value of 1. By one of the following input-devices: "Intel HID events" "Intel HID switches" "Intel Virtual Buttons" "Intel Virtual Switches" Or something like this, you can select a device by typing the number of its /dev/input/event# node. After selecting a device evemu-record will print which events the device can report. If it can report SW_TABLET_MODE then the output will also contain the current value of SW_TABLET_MODE, if this is 1 then that is the cause. (press CTRL+c to exit evemu-record) But you write "seems to stop responding at random" where as with the SW_TABLET_MODE problem I would expect it to simply not work at all (with certain kernel versions). So you may very well have a different problem then the one described in launchpad issue 1894017. What you can also try is running "sudo evemu-record" and then selecting the "AT Translated Set 2 keyboard" keyboard. After this if you type some keys on the keyboard they should show up in evemu-record as key-presses. If this works, then try doing it again (over e.g. ssh, or with an external usb kbd) when the keyboard has stopped responding. I suspect that you will find that at this point evemu-record will also no longer report keys, which means that the problem is happening at a lower level. I suspect that you will find that the problem indeed is happening at a lower-level and that you need something like this: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=addab6febc42ed94e4eee1abbe486150e4f8b9e9 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e5b1032a656e9aa4c7a4df77cb9156a2a651a5f9 In order to determine what is necessary to fix things I need a number of things: 1. output of: "grep . /sys/class/dmi/id/* 2> /dev/null" run from a terminal 2. Install acpica-tools and then run: "sudo acpidump -o acpidump.txt" and then attach the generated acpidump.txt file to your next email 3. It would help a lot if we can go from "seems to stop responding at random" to "stops responding when I do a, followed by b..." some ideas here are: 3.1 perhaps it stops responding after folding the display past 180 degrees (so a little beyond it lyinf fully flat on the table) and then back again? 3.2 perhaps it stops responding after folding the display all the way back so that the device is fully in tablet mode; and then back to laptop mode again ? 3.3 perhaps it stops responding after a suspend/resume? Regards, Hans -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1894017 Title: Keyboard not working Status in linux package in Ubuntu: Fix Released Bug description: The laptop keyboard doesn't work at login or in the de. If I ctrl+alt+F3 from an external usb keyboard to a terminal the laptop keyboard works. An external usb keyboard works everywhere. The laptop's keyboard does work everywhere with the previous kernel 5.4.0.42. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-45-lowlatency 5.4.0-45.49 ProcVersionSignature: Ubuntu 5.4.0-45.49-lowlatency 5.4.55 Uname: Linux 5.4.0-45-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu Sep 3 03:09:49 2020 InstallationDate: Installed on 2019-08-07 (392 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Hewlett-Packard HP Pavilion 11 x360 PC ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-45-lowlatency root=UUID=6035c42c-766d-44fd-b45c-6cdf9c74e0b5 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.4.0-45-lowlatency N/A linux-backports-modules-5.4.0-45-lowlatency N/A linux-firmware 1.187.3 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-06 (149 days ago) dmi.bios.date: 03/13/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.30 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name:
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
** Changed in: alsa-ucm-conf (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1937980] Re: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13
Thanks, uploaded to impish now. A small side comment since that's the first time I notice that but somehow you end up adding empty lines between debian/patches/series entries ** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1937980 Title: [SRU] the speaker doesn't work on Dell sdw sdca machine with kernel-5.13 Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: [Impact] After upgrade the linux kernel to 5.13, the mixer names of rt1316 is changed, the current alsa-ucm-conf will fail to initialize that codec, then users can't output sound from internal speaker since the internal speaker is routed to the codec rt1316. [Fix] Backport 1 commit (https://github.com/alsa-project/alsa-ucm-conf/pull/109), after applying the commit, the ucm conf file doesn't initialize the codec with hardcoded mixer names anymore, it will check the existence of the mixer name first, then conditionally initialize the codec. [Test] sudo rm /var/lib/alsa/*; alsactl init; reboot, play the sound from internal speaker, the speaker works well. [Where problems will occur] The change only affects the rt1316 codec, so far, that codec only connects to the internal speaker on Dell soundwire sdca audio machine, so it could introduce regression on the internal speaker like users can't output sound via internal speaker anymore on the Dell soundwire sdca audio machine. But this possibility is very low since we already tested the commit on the Dell soundwire sdca audio machine. We tested it with old kernel and new kernel, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1937980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940788] Re: [SRU] the input volume of external mic for sof driver is 0 by default
** Changed in: alsa-ucm-conf (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1940788 Title: [SRU] the input volume of external mic for sof driver is 0 by default Status in HWE Next: New Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Focal: In Progress Status in alsa-ucm-conf source package in Hirsute: Fix Committed Status in alsa-ucm-conf source package in Impish: Fix Committed Bug description: The change of this SRU has been squashed to https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1937980. [Impact] For the machines with sof audio driver, after we freshly install the ubuntu linux and plug a microphone or headset-mic to the audio jack, we can't record sound through them since the default input volume is 0, users need to adjust the input volume to non-zero manually, then could record sound successfully. [Fix] Backport 1 patch (https://github.com/alsa-project/alsa-ucm-conf/pull/107), after applying the patch, the ucm will set the 'Capture Switch' to on in the bootsequence, and set the Capture volume to 60%, then users could record sound without manually adjust the input volume. [Test] sudo rm /var/lib/alsa/*; rm ~/.config/pulse/*; alsactl init; reboot, plug a headset to the audio jack, use the headset-mic to record the sound, it could record successfully. [Where problems will occur] This SRU changes the Capture Switch and Capture Volume in the ucm, this could make the whole ucm can't be parsed if the syntax is not correct, then the whole audio will fail to work like audio jack can't detect plugin/plugout and the internal mic can't be found. But this regression possibility is very low since we already tested the change on lenovo and Dell machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940788/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941963] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1941963 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941963 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520 From /proc/version: Linux version 5.11.0-27-lowlatency (buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 17:06:56 UTC 2021 # apt-cache policy shim-signed shim-signed: Installed: 1.40.7+15.4-0ubuntu9 Candidate: 1.40.7+15.4-0ubuntu9 Version table: *** 1.40.7+15.4-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages >What you expected to happen Running `apt upgrade` would complete without issue. >What happened instead System hard lock, becomes completely unresponsive both from the local terminal and over established SSH. Eventually memory is exhausted and the machine reboots. Upon restart, running `apt upgrade` returns the error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Running `dpkg --configure -a` attempts to complete installation of shim-signed, segfaults, requiring a cold boot. Only a fraction of the errors generated get written to the logs before the crash as the crash prevents a final flush to disk. From a remote machine I tailed several logs and triggered the crash again, then copied the results from the terminal and attached to report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.11.0.34.36)
All autopkgtests for the newly accepted linux-meta (5.11.0.34.36) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: evdi/1.9.1-1ubuntu1 (s390x) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939347] Re: Ubuntu 20.04 freeze since kernel 5.11
Can you post the result of the command down below? "dpkg -i *-generic*.deb" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939347 Title: Ubuntu 20.04 freeze since kernel 5.11 Status in linux package in Ubuntu: Confirmed Bug description: Since the last kernel update 5.11.0-25-generic, the system freezes in a few seconds or minutes, sometimes even on the login screen. The machine is a recent dell latitude 7490. The graphics card is Intel Corporation UHD Graphics 620 (rev 07). No multiboot. No problem with the previous kernel 5.8.0-63. I had the same problem with fedora a few months ago, which forced me to switch to ubuntu without any problems so far. Thanks for your help. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: plawrence 1996 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-06-21 (414 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 002: ID 1bcf:2b96 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 004: ID 0a5c:5834 Broadcom Corp. 5880 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 7490 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=01fd281b-07d7-45f2-846b-d5b79ed5d431 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-25-generic N/A linux-backports-modules-5.11.0-25-generic N/A linux-firmware 1.187.15 Tags: focal Uname: Linux 5.11.0-25-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: 02/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.19.0 dmi.board.name: 0KP0FT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.19.0:bd02/23/2021:br1.19:svnDellInc.:pnLatitude7490:pvr:rvnDellInc.:rn0KP0FT:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7490 dmi.product.sku: 081C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941963] Re: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock
** Package changed: shim-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941963 Title: package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock Status in linux package in Ubuntu: New Bug description: Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520 From /proc/version: Linux version 5.11.0-27-lowlatency (buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 17:06:56 UTC 2021 # apt-cache policy shim-signed shim-signed: Installed: 1.40.7+15.4-0ubuntu9 Candidate: 1.40.7+15.4-0ubuntu9 Version table: *** 1.40.7+15.4-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages >What you expected to happen Running `apt upgrade` would complete without issue. >What happened instead System hard lock, becomes completely unresponsive both from the local terminal and over established SSH. Eventually memory is exhausted and the machine reboots. Upon restart, running `apt upgrade` returns the error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Running `dpkg --configure -a` attempts to complete installation of shim-signed, segfaults, requiring a cold boot. Only a fraction of the errors generated get written to the logs before the crash as the crash prevents a final flush to disk. From a remote machine I tailed several logs and triggered the crash again, then copied the results from the terminal and attached to report. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941963/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941773] Re: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver
The new logs still belongs to 5.13.8 so there's no panic information. Since there's no difference on hid and input drivers between 5.13.8 and 5.13.9. I can try to do bisection to find out the possible culprit. Could you help test the following kernel and give me your test results? Thanks https://people.canonical.com/~mschiu77/lp1941773/3cadaeae64dc/ https://people.canonical.com/~mschiu77/lp1941773/base/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941773 Title: kernel panic 5.13.9, 5.13.11, 5.13.13 related to elantech driver Status in linux package in Ubuntu: Confirmed Bug description: I do not know how to find information to help debug. The laptop is lenovo E15 with latest BIOS 1.13 kubuntu 21.04 laptop boots correctly with 5.13.8 and trackpad works. with 5.13.9, 5.13.11, 5.13.13 it makes a kernel panic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (13 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-08-12 (14 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Package: linux (not installed) Tags: hirsute Uname: Linux 5.13.8-051308-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1941773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942060] [NEW] ath11k firmware and driver crash
Public bug reported: When connecting with WLAN, the firmware and driver keeps crashing with kernel 5.10.0-1044-oem. This happens in an environment with many WLANs when connecting to a certain AP. It works OK with kernel 5.6.0.1047-oem. In other locations, WLAN works OK with the 5.10.0-1044-oem kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1044-oem 5.10.0-1044.46 ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19 Uname: Linux 5.6.0-1047-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:04:30 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "dmesg-ath11k-crash.txt" https://bugs.launchpad.net/bugs/1942060/+attachment/5521603/+files/dmesg-ath11k-crash.txt -- 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/1942060 Title: ath11k firmware and driver crash Status in linux-signed-oem-5.10 package in Ubuntu: New Bug description: When connecting with WLAN, the firmware and driver keeps crashing with kernel 5.10.0-1044-oem. This happens in an environment with many WLANs when connecting to a certain AP. It works OK with kernel 5.6.0.1047-oem. In other locations, WLAN works OK with the 5.10.0-1044-oem kernel. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1044-oem 5.10.0-1044.46 ProcVersionSignature: Ubuntu 5.6.0-1047.51-oem 5.6.19 Uname: Linux 5.6.0-1047-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 30 10:04:30 2021 InstallationDate: Installed on 2021-08-25 (4 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.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/1942060/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Tags removed: verification-needed-focal verification-needed-hirsute ** Tags added: verification-done-focal verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.11 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-hwe-5.11 source package in Hirsute: Invalid Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1941963] [NEW] package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock
You have been subscribed to a public bug: Ubuntu-Studio 20.04.3 LTS on MacPro 5,1, dual W3520 >From /proc/version: Linux version 5.11.0-27-lowlatency >(buildd@lcy01-amd64-019) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld >(GNU Binutils for Ubuntu) 2.34) #29~20.04.1-Ubuntu SMP PREEMPT Wed Aug 11 >17:06:56 UTC 2021 # apt-cache policy shim-signed shim-signed: Installed: 1.40.7+15.4-0ubuntu9 Candidate: 1.40.7+15.4-0ubuntu9 Version table: *** 1.40.7+15.4-0ubuntu9 500 500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1.40.3+15+1533136590.3beb971-0ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages >What you expected to happen Running `apt upgrade` would complete without issue. >What happened instead System hard lock, becomes completely unresponsive both from the local terminal and over established SSH. Eventually memory is exhausted and the machine reboots. Upon restart, running `apt upgrade` returns the error: "E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem." Running `dpkg --configure -a` attempts to complete installation of shim- signed, segfaults, requiring a cold boot. Only a fraction of the errors generated get written to the logs before the crash as the crash prevents a final flush to disk. From a remote machine I tailed several logs and triggered the crash again, then copied the results from the terminal and attached to report. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- package shim-signed 1.40.7+15.4-0ubuntu9 failed to install/upgrade: kernel segfault. Hard lock https://bugs.launchpad.net/bugs/1941963 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933716] Re: Black screen on boot after stable update
It's a kernel problem, I think. There is another thread for Arch Linux: https://bugs.archlinux.org/task/71003 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933716 Title: Black screen on boot after stable update Status in linux package in Ubuntu: Confirmed Bug description: After kernel update from 5.11.0-18-generic to 5.11.0-22-generic system boots into black screen. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: marcin 1374 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jun 26 11:55:00 2021 InstallationDate: Installed on 2021-05-02 (55 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: HP HP Pavilion Laptop 15-eg0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=9625a19f-eeea-4a92-ab4b-1549d4950f3b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/17/2021 dmi.bios.release: 15.12 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 87CB dmi.board.vendor: HP dmi.board.version: 34.27 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 34.27 dmi.modalias: dmi:bvnInsyde:bvrF.12:bd03/17/2021:br15.12:efr34.27:svnHP:pnHPPavilionLaptop15-eg0xxx:pvrType1ProductConfigId:rvnHP:rn87CB:rvr34.27:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-eg0xxx dmi.product.sku: 2Q2T4EA#AKD dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1941030] Re: [Fujitsu Lifebook U7411] Screen Flickers
Hi Daniel, Surprisingly, it's not happening at the moment. I will keep monitoring and send the log if/when it happens. 2 of my office colleagues are also using the same laptop and were experiencing the issue. let me also check with them if they are facing the same issue after the grub update. Thanks lot for your help and support On Mon, Aug 30, 2021 at 1:05 PM Daniel van Vugt <1941...@bugs.launchpad.net> wrote: > Thanks but that doesn't seem to show a hang. That log shows the system > just shut down cleanly. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1941030 > > Title: > [Fujitsu Lifebook U7411] Screen Flickers > > Status in linux-hwe-5.11 package in Ubuntu: > Incomplete > > Bug description: > After the laptop goes to sleep mode, it starts to flicker when i try > to use the laptop. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: xorg 1:7.7+19ubuntu14 > ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 > Uname: Linux 5.11.0-27-generic x86_64 > ApportVersion: 2.20.11-0ubuntu27.18 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Wed Aug 25 10:10:33 2021 > DistUpgraded: Fresh install > DistroCodename: focal > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA > controller]) > Subsystem: Fujitsu Client Computing Limited Device [1e26:0050] > InstallationDate: Installed on 2021-08-18 (6 days ago) > InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 > (20210209.1) > MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411 > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic > root=UUID=2ef2e3af-1c99-45d0-8bdf-5c9bd7e07ab9 ro quiet splash > pcie_aspm=off vt.handoff=7 > SourcePackage: xorg > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 06/28/2021 > dmi.bios.release: 2.21 > dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED > dmi.bios.version: Version 2.21 > dmi.board.name: FJNB2E7 > dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED > dmi.board.version: A3 > dmi.chassis.type: 10 > dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED > dmi.modalias: > dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.21:bd06/28/2021:br2.21:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7411:pvr:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E7:rvrA3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvr: > dmi.product.family: LIFEBOOK-FPCA > dmi.product.name: LIFEBOOK U7411 > dmi.product.sku: SK01 > dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED > version.compiz: compiz N/A > version.libdrm2: libdrm2 2.4.105-3~20.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200226-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1941030/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941030 Title: [Fujitsu Lifebook U7411] Screen Flickers Status in linux-hwe-5.11 package in Ubuntu: Incomplete Bug description: After the laptop goes to sleep mode, it starts to flicker when i try to use the laptop. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Aug 25 10:10:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Fujitsu Client Computing Limited Device [1e26:0050] InstallationDate: Installed on 2021-08-18 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7411 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-27-generic
[Kernel-packages] [Bug 1933518] Re: Update SmartPQI driver
Thank you, Don! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1933518 Title: Update SmartPQI driver Status in linux package in Ubuntu: In Progress Status in linux-hwe-5.11 package in Ubuntu: New Status in linux source package in Focal: Won't Fix Status in linux-hwe-5.11 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-hwe-5.11 source package in Hirsute: Invalid Bug description: [Impact] Improves support in SmartPQI for most recent controllers [Fixes] All are in mainline currently and cleanly cherry pick into Hirsute. c64aab41c5e1 scsi: smartpqi: Remove unused functions 5cad5a507241 scsi: smartpqi: Fix device pointer variable reference static checker issue 667298ceaf04 scsi: smartpqi: Fix blocks_per_row static checker issue d56030f882a7 scsi: smartpqi: Update version to 2.1.8-045 75fbeacca3ad scsi: smartpqi: Add new PCI IDs 43e97ef482ee scsi: smartpqi: Correct system hangs when resuming from hibernation d0cba99fd7a3 scsi: smartpqi: Update enclosure identifier in sysfs 18ff5f0877be scsi: smartpqi: Add additional logging for LUN resets 55732a46d6c5 scsi: smartpqi: Update SAS initiator_port_protocols and target_port_protocols ec504b23df9d scsi: smartpqi: Add phy ID support for the physical drives a425625277a1 scsi: smartpqi: Convert snprintf() to scnprintf() 3268b8a8cf77 scsi: smartpqi: Fix driver synchronization issues 66f1c2b40270 scsi: smartpqi: Update device scan operations 2790cd4d3f6a scsi: smartpqi: Update OFA management 5be9db069d3f scsi: smartpqi: Update RAID bypass handling 9fa820233609 scsi: smartpqi: Update suspend/resume and shutdown 37f3318199ce scsi: smartpqi: Synchronize device resets with mutex 4ccc354bac14 scsi: smartpqi: Update soft reset management for OFA 06b41e0d1800 scsi: smartpqi: Update event handler 7a84a821f194 scsi: smartpqi: Add support for wwid ae0c189db4f1 scsi: smartpqi: Remove timeouts from internal cmds 99a12b487f19 scsi: smartpqi: Disable WRITE SAME for HBA NVMe disks 5be746d7d74b scsi: smartpqi: Add host level stream detection enable c7ffedb3a774 scsi: smartpqi: Add stream detection 583891c9e509 scsi: smartpqi: Align code with oob driver 598bef8d7942 scsi: smartpqi: Add support for long firmware version f6cc2a774aa7 scsi: smartpqi: Add support for BMIC sense feature cmd and feature bits 7a012c23c7a7 scsi: smartpqi: Add support for RAID1 writes 6702d2c40f31 scsi: smartpqi: Add support for RAID5 and RAID6 writes 1a22bc4bee22 scsi: smartpqi: Refactor scatterlist code 281a817f232e scsi: smartpqi: Refactor aio submission code 2708a25643ab scsi: smartpqi: Add support for new product ids b622a601a13a scsi: smartpqi: Correct request leakage during reset operations c6d3ee209b9e scsi: smartpqi: Use host-wide tag space The patches they provided only apply the hunk that applies to the SmartPQI driver. This commit was a much wider commit that removes references to MODULE_SUPPORTED_DEVICE in many drivers across the kernel. 6417f03132a6 module: remove never implemented MODULE_SUPPORTED_DEVICE [Testing] On machines equipped with SmartPQI SCSI controller: 1. reboot tests 2. insmod/rmmod tests 3. fio testing: no performance regressions [Regression Risk] Patchset changes only smartpqi driver so regression is limited to systems equipped with this SCSI device. On such SmartPQI-equipped systems the patchset can cause data corruption, data loss or unavailability of SCSI storage and boot failure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933518/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932165] Re: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1
This bug was fixed in the package lttng-modules - 2.12.5-1ubuntu2~21.04.1 --- lttng-modules (2.12.5-1ubuntu2~21.04.1) hirsute; urgency=medium * Use Impish version of lttng-modules with Hirsute (LP: #1932165). lttng-modules (2.12.5-1ubuntu2) impish; urgency=medium * Cherry picks support for kernel v5.13 from upstream/stable-2.12 lttng-modules (2.12.5-1ubuntu1) impish; urgency=medium * Cherry picks support for kernel v5.12 from upstream/stable-2.12 lttng-modules (2.12.5-1) unstable; urgency=medium * [8e0b514] New upstream version 2.12.5 * [9feae13] Refreshed patches * Add support for kernel v5.11 * Add support for stable branch kernels with sublevel >=256 lttng-modules (2.12.4-1) unstable; urgency=medium * [46f9e6c] New upstream version 2.12.4 lttng-modules (2.12.3-1) unstable; urgency=medium * [5674e6f] New upstream version 2.12.3 -- Andrea Righi Tue, 13 Jul 2021 12:07:28 + ** Changed in: lttng-modules (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1932165 Title: lttng-modules/2.12.2-1ubuntu1~20.04.2 ADT test failure with linux- hwe-5.11/5.11.0-20.21~20.04.1 Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in lttng-modules package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: Invalid Status in lttng-modules source package in Focal: Fix Released Status in lttng-modules source package in Hirsute: Fix Released Bug description: [Impact] lttng-modules-dkms is reporting many build errors with linux-hwe-5.11, because of many kernel ABI changes. [Fix] Backporting the individual patches to fix all the build errors would be a lot of work and the risk to introduce regressions would be pretty high, therefore it seems safer to update to the version that is also used in impish, that works with 5.11 and it's backward compatible (so it works also with 5.4). [Test] ubuntu_lttng_smoke_test from (git://kernel.ubuntu.com/ubuntu/autotest- client-tests) [Where problems could occur] This is a major version update, so it does not contain trivial changes as backporting individual patches/fixes, so there's a risk to see regressions with lttng (however potential regressions are *only* limited to lttng). However, this way is definitely safer than backporting all the individual changes to fix the all the kernel ABI changes introduced in 5.11. [Original bug report] This is a scripted bug report about ADT failures while running lttng- modules tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/l/lttng-modules/20210611_205859_b8295@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/l/lttng-modules/20210612_123048_fc99b@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/l/lttng-modules/20210611_210510_27086@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/l/lttng-modules/20210611_210134_272f4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1932165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1940485] Re: thermald often limits CPU frequency while on AC
Try these steps. First disable thermald #systemctl disable thermald reboot Then run the script https://github.com/intel/thermal_daemon/blob/master/test/thermal-debug-dump-ubuntu.sh It will generate a tar file. Upload that. Also continue to use the system after the test and see if you see the same issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1940485 Title: thermald often limits CPU frequency while on AC Status in thermald package in Ubuntu: Incomplete Bug description: I'm not entirely sure if this is a thermald issue, but on my laptop (Dell XPS 15" 2-in-1) I find that the CPU frequency, under load on AC, is often throttled to 2.5GHz rather than the base 3.1GHz or 3.8GHz turbo frequency. Restarting thermald (with `systemctl restart thermald`) will let the system scale up to the expected ~3.8GHz boost frequency. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: thermald 2.4.6-1 ProcVersionSignature: Ubuntu 5.11.0-20.21+21.10.1-generic 5.11.21 Uname: Linux 5.11.0-20-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Aug 19 09:24:56 2021 InstallationDate: Installed on 2021-06-26 (53 days ago) InstallationMedia: Ubuntu 21.10.0 2021.05.28 amd64 "bcachefs" (20210622) SourcePackage: thermald UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1940485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
