[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Confirmed Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733&action=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. SRU justification: == [Impact] The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. [Fix] Ignore the buggy data reported by Elan TP firmware, make the TP usable. [Test] Tested on ThinkPad AMD X13 and users confirm on other platforms. [Where problems could occur] It's limited to specific Elan device, it may break the Elan Trackpoint. Jammy already got this commit in Ubuntu-5.15.0-12.12 Phoenix Huang (1): Input: elantench - fix misreporting trackpoint coordinates drivers/input/mouse/elantech.c | 13 + 1 file changed, 13 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953136] [NEW] HWE kernel is missing i915 firmwares
Public bug reported: This is a report that the same bug being tracked in 1889137 (https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1889137) against bionic is also occurring in focal against the 5.11.0-41-generic kernel: phocking ~ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 phocking ~ uname -a Linux phocking-ws 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux phocking ~ dpkg -l | grep linux-firmware ii linux-firmware 1.187.20 all Firmware for Linux kernel drivers phocking ~ sudo apt install --reinstall linux-firmware Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 13 not upgraded. Need to get 0 B/111 MB of archives. After this operation, 0 B of additional disk space will be used. (Reading database ... 424752 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.187.20_all.deb ... Unpacking linux-firmware (1.187.20) over (1.187.20) ... Setting up linux-firmware (1.187.20) ... update-initramfs: Generating /boot/initrd.img-5.11.0-41-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 update-initramfs: Generating /boot/initrd.img-5.11.0-40-generic W: Possible missing firmware /lib/firmware/i915/skl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/cml_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/ehl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module i915 W: Possible missing firmware /lib/firmware/i915/tgl_guc_49.0.1.bin for module i915 W: Possible missing firmware /lib/firmware/i915/dg1_dmc_ver2_02.bin for module i915 phocking ~ ** 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/1953136 Title: HWE kernel is missing i915 firmwares Status in linux-firmware package in Ubuntu: New Bug description: This is a report that the same bug being tracked in 1889137 (https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/1889137) against bionic is also occurring in focal against the 5.11.0-41-generic kernel: phocking ~ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 phocking ~ uname -a Linux phocking-ws 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux phocking ~ dpkg -l | grep linux-firmware ii linux-firmware 1.187.20 all Firmware for Linux kernel drivers phocking ~ sudo apt install --reinstall linux-firmware Reading package lists... Done Building d
[Kernel-packages] [Bug 1951868] Re: [amdgpu] USB4 support for DP tunneling
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1951868 Title: [amdgpu] USB4 support for DP tunneling Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Bug description: [Impact] DP tunneling over USB4 requires additional work in the AMD GPU driver that isn't present in 5.14 or 5.15. The code is included in 5.16 kernel and will need to be backported into 5.14 OEM kernel (and jammy/5.15) to support any programs that need it. [Fix] Cherry-pick/backport 30 commits from 5.16 to 5.15. OEM-5.14 needs a few additional ones from 5.15. [Test case] WIP [Where things could go wrong] WIP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1951868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951767] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks
** Changed in: linux-oem-5.14 (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.14 in Ubuntu. https://bugs.launchpad.net/bugs/1951767 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add MAC passthrough support for more Lenovo docks Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: [Impact] MAC pass through is not working on new TBT and USB-C docks. [Fix] Enable MAC pass through based on Lenovo USB hub. [Test] Tested on Lenovo TBT4 and TBT3 dock, MAC pass through works well. [Where problems could occur] The Realtek USB ethernet in Lenovo USB hub will mess the MAC address. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1951767/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1936295] Re: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate
** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux-oem-5.13 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-oem-5.14 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1936295 Title: Faulty Elantech Trackpoint firmware unusable as it causes sudden cursor jump to an edge/corner on Lenovo Thinkpad X13, T14s, A475 --> Apply kernel patch to mitigate the FW bug Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: Confirmed Bug description: *Problem description:* On Lenovo Thinkpad T14s, X13, A475 (and probably more models) the Elantech Trackpoint firmware is defective. The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. Currently, the Trackpoint is barely usable and it's impossible to productively work using it. For a long while, Elantech has not yet put forward (nor confirmed) a firmware update. However, there is a Linux kernel patch mitigating the firmware bug. The kernel bugfix discards the wrongly reported packages by the Elantech hardware. This solves the problem for the user. *Solution:* Please apply existing kernel patch here. https://bugzilla.kernel.org/show_bug.cgi?id=209167 Bug entry in the Linux Kernel.org Bugzilla https://bugzilla.kernel.org/attachment.cgi?id=295733&action=diff Diff of bugfix *T14s and X13 are Ubuntu certified:* The Lenovo Thinkpad T14s and X13 are Ubuntu certified, but apparently this hardware issue has slipped the Ubuntu certification process! https://ubuntu.com/certified/202006-27978 and https://ubuntu.com/certified/202006-27979 *Further information:* https://forums.lenovo.com/t5/Fedora/T14s-AMD-Trackpoint-almost-unusable/m-p/5064952?page=1 Discussion on the bug in the Lenovo forum. E.g. see comment 18 by Lenovo employee MarkRHPearson *My System:* Lenovo Thinkpad T14s (AMD) 20ujs00k00 Ubuntu 21.04 and 20.04 see entries in kernel.org bugzilla for logs. SRU justification: == [Impact] The trackpoint cursor often suddenly jumps to an edge/corner, because the hardware/firmware sometimes reports wrong coordinates / loses sync. [Fix] Ignore the buggy data reported by Elan TP firmware, make the TP usable. [Test] Tested on ThinkPad AMD X13 and users confirm on other platforms. [Where problems could occur] It's limited to specific Elan device, it may break the Elan Trackpoint. Jammy already got this commit in Ubuntu-5.15.0-12.12 Phoenix Huang (1): Input: elantench - fix misreporting trackpoint coordinates drivers/input/mouse/elantech.c | 13 + 1 file changed, 13 insertions(+) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1936295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1943353] Re: kernel hang at resuming from s2idle on AMD Barcelo platform with SATA attached
what's the status of this bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1943353 Title: kernel hang at resuming from s2idle on AMD Barcelo platform with SATA attached Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Incomplete Bug description: On AMD Barcelo CRB platform, BIOS RLD-1005B_AB 06/30/2021, starting from v5.14-rc1 kernel that put system to deep sleep than v5.13, cannot wake from s2idle, fan spinning, debug LED EEFC0300, BLK LED blinking. This, as long as one sata device is attached, no matter it was boot from sata or nvme root partition, it will all be affected. Public bug filed at https://bugzilla.kernel.org/show_bug.cgi?id=214365 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1410 F pulseaudio /dev/snd/controlC2: ubuntu 1410 F pulseaudio /dev/snd/controlC0: ubuntu 1410 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (2 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 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: AMD Celadon-CZN Package: linux (not installed) ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9002-oem root=UUID=bac31a43-d46f-43f7-8eb0-87b96dbf0a61 ro automatic-oem-config quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.14.0-9002.2+staging.19-oem 5.14.0 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.14.0-9002-oem N/A linux-backports-modules-5.14.0-9002-oem N/A linux-firmware 1.187.16+staging.16 RfKill: Tags: focal Uname: Linux 5.14.0-9002-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:sku123456789:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943353/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1932539] Re: Support thunderbolt on Intel Alder Lake P
assuming this works by now ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1932539 Title: Support thunderbolt on Intel Alder Lake P Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Invalid Bug description: Thunderbolt device probe failure on ADL: thunderbolt: probe of :00:0d.2 failed with error -110 thunderbolt: probe of :00:0d.3 failed with error -110 00:0d.2 USB controller [0c03]: Intel Corporation Device [8086:463e] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] 00:0d.3 USB controller [0c03]: Intel Corporation Device [8086:466d] (prog-if 40) Subsystem: Intel Corporation Device [8086:7270] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-09 (39 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IwConfig: lono wireless extensions. enx00e04c6801fa no wireless extensions. MachineType: Intel Corporation Alder Lake Client Platform Package: linux (not installed) ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-1004-oem root=UUID=fc4454dd-6eb1-4b3c-ae7f-c0b5ede8f9f7 ro module_blacklist=btintel,btusb,iwlwifi,e1000e i915.force_probe=46a0 ProcVersionSignature: Ubuntu 5.13.0-1004.4-oem 5.13.0-rc6 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-1004-oem N/A linux-backports-modules-5.13.0-1004-oem N/A linux-firmware 1.187.15 RfKill: Tags: focal Uname: Linux 5.13.0-1004-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/26/2021 dmi.bios.vendor: Intel Corporation dmi.bios.version: ADLPFWI1.R00.2127.A00.2103261115 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: AlderLake-P DDR5 RVP dmi.board.vendor: Intel Corporation dmi.board.version: 1 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2127.A00.2103261115:bd03/26/2021:efr1.31:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:sku0012:rvnIntelCorporation:rnAlderLake-PDDR5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1: dmi.product.family: Alder Lake Client System dmi.product.name: Alder Lake Client Platform dmi.product.sku: 0012 dmi.product.version: 0.1 dmi.sys.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1932539/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950974] Re: Improve USB Type-C support
we need to land this in jammy too, eventually -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1950974 Title: Improve USB Type-C support Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Error message "ucsi_acpi USBC000:00: GET_CONEECTOR_STATUS failed (-110)" can be found on many systems. [Fix] The main issue is that the PD firmware is unreliable, so use more deterministic methods to make it reliable [Test] The error message is gone. Also tried to plug/unplug USB Type-C power cord, and the status are always reported correctly. [Where problems could occur] This is quite a huge refactor, so regression can be expected. Only target to unstable and latest OEM kernel to reduce risk we are taking. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1950974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen
On my system I found that the left-edge cursor malfunction began in Linux Mint 19.3. The malfunction was unchanged when I tested with live- boot thumbsticks for Ubuntu, MX, and Manjaro. With the live-boot thumbstick for EndeavourOS, the left-edge problem was absent, but the cursor showed extreme flickering and multiple copies of itself. I also noted that at the moment when the mouse cursor started flickering, the left-edge cursor malfunction ceased entirely. Computer: Gigabyte Brix GB-BACE-3160 Processor: Intel Celeron Braswell J3160 @ 1.60GHz × 4 System: Linux Mint 20.2 Cinnamon 5.0.7 Kernel: 5.13.0.21 generic x86_64 (64 bit) Graphics: Intel Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller pilotbob42's suggested command (Thank you) fixes the left-edge cursor malfunction xrandr --output HDMI-3 --transform 1,0,-1,0,1,0,0,0,1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767654 Title: [Intel Braswell] Cursor gets stuck on left side of the screen Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: When moving the cursor to the left side of the screen, it stops close to the edge. The cursor still moves over in the area but invisible until I move it out of the area. When it doesn't do this, glitching occurs on the screen where the cursor is until I log out. And on screen cast it shows the cursor going to the side of the screen and moving. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 09:49:51 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060] InstallationDate: Installed on 2018-04-27 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 initrd=boot\initrd.img-4.15.0-20-generic SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/08/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-408 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1767654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877533] Re: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted
@cascardo 'ppa:cascardo/kdump2' was okay for me, when I tried it last time - however, not sure if s/o from IBM tried it, too. I think that the approach that you've described is totally valid and fine. And the debdiff looks reasonable and incl. the 2G-4G case). Since situations where dumps are needed are rare anyway, and people are usually careful and mostly follow manual steps any, I do not see an issue at all with a few prompts with questions on zipl.conf. So definitely a +1 from me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1877533 Title: [20.10 FEAT] Increase the crashkernel setting if the root volume is luks2-encrypted Status in Ubuntu on IBM z Systems: In Progress Status in kdump-tools package in Ubuntu: Invalid Status in makedumpfile package in Ubuntu: Invalid Status in kdump-tools source package in Focal: Invalid Status in makedumpfile source package in Focal: In Progress Status in kdump-tools source package in Groovy: Invalid Status in makedumpfile source package in Groovy: In Progress Bug description: Description: In case the volume containing the root filesystem is encrypted using LUKS2 the memory used while unlocking the volume may exceed the size allocated to the kdump kernel. This will lead to a failure while processing kdump and the dump file will not be stored. Unfortunately, this condition may not be detected by a client before a problem occurs. The request is to have the kdump package installation script check for LUKS2 encryption (more precisely for Argon2i PBKDF, which is the root cause of the high memory usage). If the condition is met, the installation procedure should increase the crashkernel parameter to a higher value (>=512M)or issue a warning, if the system memory is insufficient to reserve enough crashkernel memory. Business Case: Pervasive Encryption and Secure Execution require encryption of the filesystems in order to keep customer data secure at all times. With the increasing usage of these technologies, the number of kdump will rise too, typically at inconvenient times, when the kdump is triggered due to a real customer issue. With the suggested change, the number of customer complaints and effort to handle them will be reduced. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877533/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Comment bridged from LTC Bugzilla
--- Comment From pa...@de.ibm.com 2021-12-03 08:37 EDT--- (In reply to comment #12) > This bug is awaiting verification that the linux/5.4.0-92.103 kernel in > -proposed solves the problem. Please test the kernel and update this bug > with the results. If the problem is solved, change the tag > 'verification-needed-focal' to 'verification-done-focal'. If the problem > still exists, change the tag 'verification-needed-focal' to > 'verification-failed-focal'. > > If verification is not done by 5 working days from today, this fix will be > dropped from the source code, and this bug will be closed. > > See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to > enable and use -proposed. Thank you! The newest kernel I see in proposed is 5.4.0.92.96 root@ubuntu20:~# apt-get install linux-generic/focal-proposed Reading package lists... Done Building dependency tree Reading state information... Done linux-generic is already the newest version (5.4.0.92.96). Selected version '5.4.0.92.96' (Ubuntu:20.04/focal-proposed [s390x]) for 'linux-generic' The following packages were automatically installed and are no longer required: linux-headers-5.4.0-18 linux-headers-5.4.0-18-generic linux-image-5.4.0-18-generic linux-modules-5.4.0-18-generic Did I mess something up? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian
[Kernel-packages] [Bug 1953166] [NEW] Kernel bugs out with packet writing on DVD RW, system remains unable to shutdown cleanly and needs power cycling
Public bug reported: Hi, trying to use packet writing on a DVD RW media with ubuntu 20.04 I see a kernel bug. This is what I am doing: 1) Preparing a dvdrw with the udf filesystem with mkudffs --media- type=dvdrw --spartable=2 /dev/pktcdvd/pktcdvd0 after having erased it with growisofs -Z /dev/sr0=/dev/zero. 2) Mouting the filesystem 3) Trying to write some files on it I see the writeback cache getting dirty and then staying dirty forever, while the kernel says [ cut here ] [ 1738.892880] kernel BUG at drivers/block/pktcdvd.c:2411! [ 1738.892894] invalid opcode: [#1] SMP NOPTI [ 1738.892902] CPU: 0 PID: 8493 Comm: kworker/u16:5 Tainted: G OE 5.11.0-41-generic #45~20.04.1-Ubuntu [ 1738.892909] Hardware name: SCHENKER SCHENKER_SLIM14_SSL14L19/N141CU , BIOS 1.07.04RTR1 10/02/2019 [ 1738.892913] Workqueue: writeback wb_workfn (flush-252:0) [ 1738.892927] RIP: 0010:pkt_submit_bio+0x39d/0x4b0 [pktcdvd] [ 1738.892939] Code: 41 3b 45 40 7c 0b 41 83 7d 44 01 0f 84 cd 00 00 00 4c 89 ff c6 07 00 0f 1f 40 00 4c 89 e7 c6 07 00 0f 1f 40 00 e9 08 ff ff ff <0f> 0b 0f 0b 4c 89 c8 31 c9 e9 96 fe ff ff 48 c7 c2 e0 17 44 c1 be [ 1738.892945] RSP: 0018:b84c43bd3728 EFLAGS: 00010283 [ 1738.892950] RAX: 17a8 RBX: 97508f66f800 RCX: 17a7 [ 1738.892955] RDX: 1980 RSI: 17c0 RDI: 0040 [ 1738.892958] RBP: b84c43bd37a0 R08: 0200 R09: ffc0 [ 1738.892962] R10: 1780 R11: R12: 974fd2412800 [ 1738.892966] R13: R14: 97513f5f2800 R15: 9751584f9f50 [ 1738.892970] FS: () GS:97533060() knlGS: [ 1738.892975] CS: 0010 DS: ES: CR0: 80050033 [ 1738.892979] CR2: 039f9000 CR3: 0003dfe10005 CR4: 003726f0 [ 1738.892984] Call Trace: [ 1738.892987] ? ktime_get+0x3e/0xa0 [ 1738.892997] ? blk_queue_enter+0x18d/0x240 [ 1738.893005] ? submit_bio_checks+0x1d0/0x5d0 [ 1738.893011] ? mempool_alloc_slab+0x17/0x20 [ 1738.893017] ? mempool_alloc+0x64/0x180 [ 1738.893023] submit_bio_noacct+0x112/0x4f0 [ 1738.893030] submit_bio+0x51/0x1a0 [ 1738.893036] ? bio_add_page+0x3b/0x90 [ 1738.893045] __mpage_writepage+0x7fe/0x8f0 [ 1738.893052] ? find_get_pages_range_tag+0x26c/0x300 [ 1738.893057] ? __mod_memcg_lruvec_state+0x25/0xe0 [ 1738.893063] ? clear_page_dirty_for_io+0xdb/0x1b0 [ 1738.893071] write_cache_pages+0x190/0x430 [ 1738.893078] ? clean_buffers+0x70/0x70 [ 1738.893085] ? udf_block_map+0xf0/0xf0 [udf] [ 1738.893099] mpage_writepages+0x77/0x100 [ 1738.893104] ? udf_block_map+0xf0/0xf0 [udf] [ 1738.893114] ? udf_time_to_disk_stamp+0x52/0x140 [udf] [ 1738.893129] udf_writepages+0x15/0x20 [udf] [ 1738.893140] do_writepages+0x43/0xd0 [ 1738.893147] ? udf_update_inode+0x36f/0x830 [udf] [ 1738.893158] __writeback_single_inode+0x44/0x2b0 [ 1738.893165] writeback_sb_inodes+0x22d/0x4c0 [ 1738.893173] __writeback_inodes_wb+0x56/0xf0 [ 1738.893179] wb_writeback+0x1ea/0x2a0 [ 1738.893186] wb_workfn+0x31b/0x490 [ 1738.893193] ? __update_idle_core+0x9b/0xb0 [ 1738.893201] process_one_work+0x220/0x3c0 [ 1738.893207] worker_thread+0x4d/0x3f0 [ 1738.893212] ? process_one_work+0x3c0/0x3c0 [ 1738.893217] kthread+0x12b/0x150 [ 1738.893224] ? set_kthread_struct+0x40/0x40 [ 1738.893231] ret_from_fork+0x1f/0x30 [ 1738.893242] Modules linked in: udf crc_itu_t pktcdvd usb_storage hid_generic hidp hid ccm vhost_vsock vmw_vsock_virtio_transport_common vhost vhost_iotlb vsock rfcomm cmac algif_hash algif_skcipher af_alg vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep binfmt_misc snd_hda_codec_hdmi snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_hda_codec_realtek snd_sof_intel_byt snd_sof_intel_ipc snd_hda_codec_generic snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi ledtrig_audio snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence snd_hda_codec snd_hda_core snd_hwdep soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_msr mei_hdcp snd_rawmidi nls_iso8859_1 intel_rapl_common x86_pkg_temp_thermal intel_powerclamp iwlmvm coretemp snd_seq snd_seq_device uvcvideo kvm_intel mac80211 videobuf2_vmalloc btusb videobuf2_memops kvm btrtl btbcm [ 1738.893354] videobuf2_v4l2 btintel libarc4 snd_timer videobuf2_common rapl intel_cstate bluetooth input_leds videodev snd joydev iwlwifi serio_raw mc efi_pstore cfg80211 intel_wmi_thunderbolt ecdh_generic ecc soundcore mei_me intel_pch_thermal mei intel_hid sparse_keymap acpi_pad mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_comment xt_recent xt_multiport xt_limit xt_addrtype xt_tcpudp xt_conntrack sch_fq_codel nf_conntrack nf_defrag_ipv6 nf_defr
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
Hi, no you didn't messed it up - the version number causes some confusion from time to time. The last digit can be ignored (it's just the build number). If the first 4 digits are the same, you have the right kernel (in other words: content-wise 5.4.0.92.9 is equal to 5.4.0-92.103 - the difference is just that the first one if the source and the second one the binary version). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still
[Kernel-packages] [Bug 1953147] [NEW] This is an update issue: Msg reads; Dependency issues when updating linux-modules-nvidia-470-5.13.0-21-generic
You have been subscribed to a public bug: When trying to update I get the error message: ## Update Issue Dependency resolution failed: The following packages have unmet dependencies: linux-modules- nvidia-470-5.13.0-21-generic: Depends: nvidia-kernel-common-470 (<= 470.82.00-1) but 470.86-0ubuntu0.21.10.1 is to be installed Please report this issue to the packagers of your distribution. ## Kubuntu, 21.10 Plasma 5.22.5 KDE Frameworks 5.86.0 Qt 5.15.2 Kernel 5.13.0-21-generic (64-bit) X11 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- This is an update issue: Msg reads; Dependency issues when updating linux-modules-nvidia-470-5.13.0-21-generic https://bugs.launchpad.net/bugs/1953147 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 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 1953147] Re: This is an update issue: Msg reads; Dependency issues when updating linux-modules-nvidia-470-5.13.0-21-generic
** Package changed: ubuntu => nvidia-graphics-drivers-470 (Ubuntu) ** Tags added: impish -- 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/1953147 Title: This is an update issue: Msg reads; Dependency issues when updating linux-modules-nvidia-470-5.13.0-21-generic Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: When trying to update I get the error message: ## Update Issue Dependency resolution failed: The following packages have unmet dependencies: linux-modules- nvidia-470-5.13.0-21-generic: Depends: nvidia-kernel-common-470 (<= 470.82.00-1) but 470.86-0ubuntu0.21.10.1 is to be installed Please report this issue to the packagers of your distribution. ## Kubuntu, 21.10 Plasma 5.22.5 KDE Frameworks 5.86.0 Qt 5.15.2 Kernel 5.13.0-21-generic (64-bit) X11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1953147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze
I also get this error with Ubuntu Budgie 21.10, may try going to 21.04 and see if it changes. I think this is occurring due to the "ntfsresize tainted" error in the log - I do have Windows on half the partition and had used "MiniTool Partition Wizard to clear half the drive first. Might be a path to replicating the error. Step 1) Install Windows on half the drive. Step 2) Install Windows on the other half Step 3) Use MiniTool Partition Wizard and clear half the drive. Step 4) Attempt to install Ubuntu - If you get past the "Updates and other software" screen then go the recommended route and then click the go back button instead of confirming that you want to go forward. Step 5) Watch as every subsequent install fails. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: Incomplete Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952669] Re: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- 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/1952669 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: I was upgrading some packages with Synaptic and the aforementioned one failed claiming that it had some dependency issues. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-470 470.86-0ubuntu0.20.04.1 Uname: Linux 5.15.2-051502-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Nov 29 17:43:14 2021 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-11-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.86-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1952669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950515] Re: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others
I still have no Wi-Fi nor Bluetooth with 5.13.0-22 on an XPS. 5.13.0-20 works OK. Enable/disabling via BIOS, poweroff, power cycling, etc do not fix 5.13.0-22. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950515 Title: WiFi Killer AX500s DBS stopped working in kernel 5.13.0-21-generic on Dell XPS 13 9310 and others Status in linux package in Ubuntu: Fix Released Bug description: In the 5.13.0-21 kernel, the device fails: $ lshw -c network *-network description: Network controller product: QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] vendor: Qualcomm physical id: 0 bus info: pci@:72:00.0 version: 01 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list configuration: driver=ath11k_pci latency=0 resources: irq:182 memory:a250-a25f $ lspci | grep Qualcomm 72:00.0 Network controller: Qualcomm QCA6390 Wireless Network Adapter [AX500-DBS (2x2)] (rev 01) $ sudo modprobe ath11k_pci $ sudo dmesg | grep ath [4.611544] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [4.611573] ath11k_pci :72:00.0: enabling device ( -> 0002) [4.612103] ath11k_pci :72:00.0: qca6390 hw2.0 [ 10.337672] ath11k_pci :72:00.0: failed to register fw indication: -110 [ 10.337692] ath11k_pci :72:00.0: failed to send qmi firmware indication: -110 [ 39.931711] ath11k_pci :72:00.0: link down error during global reset [ 45.574642] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 45.575668] ath11k_pci :72:00.0: qca6390 hw2.0 [ 45.630047] ath11k_pci :72:00.0: failed to set pcie link register 0x01e0c0ac: 0x != 0x0010 [ 45.630054] ath11k_pci :72:00.0: failed to set sysclk: -110 [ 45.650253] ath11k_pci :72:00.0: link down error during global reset $ rfkill list all 0: hci0: Bluetooth Soft blocked: no Hard blocked: no In the 5.13.0-20 kernel, the device works: $ sudo dmesg | grep ath [ 4.804410] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 4.804440] ath11k_pci :72:00.0: enabling device ( -> 0002) [ 4.808036] ath11k_pci :72:00.0: qca6390 hw2.0 [ 5.085678] ath11k_pci :72:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0x [ 5.085684] ath11k_pci :72:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id [ 5.258202] ath11k_pci :72:00.0 wlp114s0: renamed from wlan0 [ 351.080712] ath11k_pci :72:00.0: link down error during global reset [ 356.511270] ath11k_pci :72:00.0: BAR 0: assigned [mem 0xa250-0xa25f 64bit] [ 356.512356] ath11k_pci :72:00.0: qca6390 hw2.0 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Nov 10 15:23:07 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2021-05-04 (190 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9310 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.13.0-21-generic root=UUID=676fbdd4-8566-4457-8530-0f412d28b48f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-19 (22 days ago) dmi.bios.date: 09/30/2021 dmi.bios.release: 3.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 3.2.0 dmi.board.name: 0MRT12 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr3.2.0:bd09/30/2021:br3.2:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MRT12:rvrA00:cvnDellInc.:ct10:cvr:sku0991: dmi.product.family: XPS dmi.product.name: XPS 13 9310 dmi.product.sku: 0991 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950515/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-pack
[Kernel-packages] [Bug 1946507] Re: Ubuntu Install Setup Freeze
Confirmed - this bug impacts the 21.10 installer of Ubuntu Budgie and appears like it is an upstream issue as well given I found this. This bug does not impact 20.04 installers. (could not find 21.04 installer, so not tested) Also I know initially I did not have this issue before I repartitioned with Minitool - I felt it was safer to repartition and move things around how I wanted from that tool first before proceeding and then the installer broke after after that. I ran diskcheck repairs from Windows and never found an issue either, so no idea what happened - but I am guessing some code change causes it to get hung up on something NTFS related when it shouldn't be. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946507 Title: Ubuntu Install Setup Freeze Status in linux package in Ubuntu: Incomplete Bug description: Hello, While trying to Install Ubuntu 21.10 , the setup freeze after clicking continue on Step 4 where it asks if you wish to install Updates , and i have selected Normal Installation when i click continue then setup freeze so im not able to click any other button just QUIT button is working , other buttons are grayed out and not clickable , i have tried many methods since 2 days been trying nomodeset acpi=off and other but nothing works for me , i need help . Thanks ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubiquity 21.10.6 [modified: lib/partman/automatically_partition/question] ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13 Uname: Linux 5.13.0-16-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu69 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.465 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 8 15:56:06 2021 InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz nomodeset file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash --- LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211006) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubiquity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946507/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946055] Re: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop!
We're seeing this on a laptop at work (TigerLake Oryx Pro from System76) on 20.04 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1946055 Title: Ubuntu 21.04 drivers/drm/i915 crashes on my laptop! Status in linux package in Ubuntu: Confirmed Bug description: [2.515353] Missing case (val == 65535) [2.515366] WARNING: CPU: 3 PID: 478 at drivers/gpu/drm/i915/intel_dram.c:96 skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515433] Modules linked in: snd_hda_core kvm_intel snd_hwdep nvidia(PO+) libarc4 kvm joydev soundwire_bus nls_iso8859_1 mei_hdcp intel_rapl_msr i915(+) fjes(-) iwlwifi crct10dif_pclmul ghash_clmulni_intel snd_soc_core drm_kms_helper aesni_intel processor_thermal_device snd_compress cec processor_thermal_rfim ac97_bus crypto_simd snd_pcm_dmaengine rc_core i2c_algo_bit cryptd processor_thermal_mbox fb_sys_fops input_leds mei_me thinkpad_acpi glue_helper syscopyarea intel_cstate nvram efi_pstore sysfillrect snd_seq_midi serio_raw wmi_bmof cfg80211 ee1004 ledtrig_audio snd_pcm processor_thermal_rapl ucsi_acpi(+) sysimgblt snd_seq_midi_event mei intel_rapl_common typec_ucsi intel_soc_dts_iosf snd_rawmidi typec snd_seq snd_seq_device snd_timer snd int3403_thermal soundcore int340x_thermal_zone mac_hid intel_hid int3400_thermal sparse_keymap acpi_thermal_rel acpi_pad acpi_tad sch_fq_codel stp llc ip_vs_wrr ip_vs_sh ip_vs_rr ip_vs nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c msr [2.515472] parport_pc ppdev lp drm parport ip_tables x_tables autofs4 crc32_pclmul sdhci_pci psmouse cqhci i2c_i801 i2c_smbus sdhci igc nvme thunderbolt xhci_pci nvme_core xhci_pci_renesas wmi video pinctrl_tigerlake [2.515484] CPU: 3 PID: 478 Comm: systemd-udevd Tainted: P O 5.11.0-37-generic #41-Ubuntu [2.515486] Hardware name: LENOVO 20YUCTO1WW/20YUCTO1WW, BIOS N37ET34W (1.15 ) 09/01/2021 [2.515487] RIP: 0010:skl_dram_get_dimm_info+0x79/0x1b0 [i915] [2.515534] Code: 0f 84 34 01 00 00 41 f7 c0 00 01 00 00 0f 84 27 01 00 00 41 0f b7 d0 48 c7 c6 b1 6b fd c0 48 c7 c7 b5 6b fd c0 e8 07 1e 7c e1 <0f> 0b 44 0f b7 0b b9 01 00 00 00 31 c0 31 f6 88 43 02 41 c1 ff 09 [2.515535] RSP: 0018:be36011b7980 EFLAGS: 00010282 [2.515537] RAX: RBX: be36011b79ec RCX: 9b27574d8ac8 [2.515538] RDX: ffd8 RSI: 0027 RDI: 9b27574d8ac0 [2.515539] RBP: be36011b79a8 R08: R09: be36011b7760 [2.515540] R10: be36011b7758 R11: a37535e8 R12: [2.515541] R13: 004c R14: 9b164558 R15: [2.515542] FS: 7fb8218a08c0() GS:9b27574c() knlGS: [2.515544] CS: 0010 DS: ES: CR0: 80050033 [2.515545] CR2: 7fb8213ae4e0 CR3: 000108a5e006 CR4: 00770ee0 [2.515546] PKRU: 5554 [2.515546] Call Trace: [2.515549] skl_dram_get_channel_info+0x2e/0x150 [i915] [2.515592] skl_dram_get_channels_info+0x6e/0x190 [i915] [2.515634] skl_get_dram_info+0x6e/0x100 [i915] [2.515667] intel_dram_detect+0x3e/0xd0 [i915] [2.515711] i915_driver_hw_probe+0x1cc/0x210 [i915] [2.515748] i915_driver_probe+0xe5/0x2f0 [i915] [2.515781] ? mutex_lock+0x13/0x40 [2.515785] ? acpi_dev_found+0x66/0x70 [2.515788] i915_pci_probe+0x58/0x140 [i915] [2.515822] local_pci_probe+0x48/0x80 [2.515824] pci_call_probe+0x53/0xf0 [2.515826] pci_device_probe+0xad/0xf0 [2.515827] really_probe+0x23a/0x4a0 [2.515830] driver_probe_device+0xe9/0x160 [2.515832] device_driver_attach+0xab/0xb0 [2.515833] __driver_attach+0x8f/0x150 [2.515835] ? device_driver_attach+0xb0/0xb0 [2.515836] bus_for_each_dev+0x7e/0xc0 [2.515837] driver_attach+0x1e/0x20 [2.515839] bus_add_driver+0x135/0x1f0 [2.515840] driver_register+0x95/0xf0 [2.515842] __pci_register_driver+0x54/0x60 [2.515843] i915_init+0x66/0x86 [i915] [2.515877] ? 0xc0c7 [2.515878] do_one_initcall+0x48/0x1d0 [2.515881] ? kmem_cache_alloc_trace+0xf6/0x200 [2.515883] ? do_init_module+0x28/0x290 [2.515886] do_init_module+0x62/0x290 [2.515887] load_module+0x6fd/0x780 [2.515888] __do_sys_finit_module+0xc2/0x120 [2.515890] __x64_sys_finit_module+0x1a/0x20 [2.515891] do_syscall_64+0x38/0x90 [2.515893] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [2.515894] RIP: 0033:0x7fb821d58f6d [2.515896] Code: 28 0d 00 0f 05 eb a9 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d cb de 0c 00 f7 d8 64 89 01 48 [2.515897] RSP: 002b:7ffdf53714c8 EFLAGS: 0246 ORIG_RA
[Kernel-packages] [Bug 1953175] [NEW] package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess
You have been subscribed to a public bug: I'm trying to install NVidia driver 460 on Lenovo Legion 5 Pro 16ach6, but not able to install any available driver ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 Uname: Linux 5.12.4-051204-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 3 16:31:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-12-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-460-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check third-party-packages -- package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 https://bugs.launchpad.net/bugs/1953175 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server 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 1953175] Re: package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess r
** Package changed: ubuntu => nvidia-graphics-drivers-460-server (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460-server in Ubuntu. https://bugs.launchpad.net/bugs/1953175 Title: package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post- installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-460-server package in Ubuntu: New Bug description: I'm trying to install NVidia driver 460 on Lenovo Legion 5 Pro 16ach6, but not able to install any available driver ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 Uname: Linux 5.12.4-051204-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Dec 3 16:31:02 2021 ErrorMessage: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-12-03 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: nvidia-graphics-drivers-460-server Title: package nvidia-dkms-460-server 460.106.00-0ubuntu0.20.04.1 failed to install/upgrade: installed nvidia-dkms-460-server package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-460-server/+bug/1953175/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950144] Comment bridged from LTC Bugzilla
Hi, no you didn't messed it up - the version number causes some confusion from time to time. If the first 4 digits are the same, you have the right kernel (in other words: content-wise 5.4.0.92.9 is equal to 5.4.0-92.103 - the difference is just that the first one if the source and the second one the binary version). --- Comment From pa...@de.ibm.com 2021-12-03 11:13 EDT--- (In reply to comment #17) > Hi, no you didn't messed it up - the version number causes some confusion > from time to time. > The last digit can be ignored (it's just the build number). > If the first 4 digits are the same, you have the right kernel (in other > words: content-wise 5.4.0.92.9 is equal to 5.4.0-92.103 - the difference is > just that the first one if the source and the second one the binary version). Thank you! I've verified the fix! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on u
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
Believed to be fixed in the kernel by two commits. See: https://bugzilla.kernel.org/show_bug.cgi?id=177311#c65 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in Linux: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
1) firmware-sof is good; note that breaks/replaces versions will need to be adjusted to the correct versions for every series upon every upload of this change, if it is SRUed. 2) the matching linux-firmware changes are good as well. -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Triaged Status in firmware-sof source package in Jammy: Triaged Status in linux-firmware source package in Jammy: Triaged Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files a
[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface
** Changed in: linux (Ubuntu Focal) Assignee: dann frazier (dannf) => (unassigned) -- You 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 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
Ah, many thx - I'm adjusting the tags accordingly ... ** Tags removed: verification-needed-focal verification-needed-hirsute verification-needed-impish ** Tags added: verification-done-focal verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VE
[Kernel-packages] [Bug 1950144] Re: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm)
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin2004 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950144 Title: [UBUNTU 20.04] kernel: unable to read partitions on virtio-block dasd (kvm) Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Released Bug description: SRU Justification: == [Impact] * The kernel is unable to read partitions on virtio-block DASD (on KVM). That's a severe situation, since it prevents Ubuntu from starting, if installed on a DASD. This issue can either occur after a fresh installation or after an upgrade. * The virtio specification virtio-v1.1-cs01 states: "Transitional devices MUST detect Legacy drivers by detecting that VIRTIO_F_VERSION_1 has not been acknowledged by the driver." And this is what QEMU as of 6.1 has done relying solely on VIRTIO_F_VERSION_1 for detecting that. * But the specification also says: "... the driver MAY read (but MUST NOT write) the device-specific configuration fields to check that it can support the device ..." before setting FEATURES_OK. * In this case, any transitional device relying solely on VIRTIO_F_VERSION_1 for detecting legacy drivers will return data in legacy format. In particular, this implies that it's in big endian format for big endian guests. This naturally confuses the driver that expects little endian in the modern mode. * VIRTIO_F_VERSION_1 can only be relied on after the feature negotiation is done. * 'verify' is called before virtio_finalize_features(), so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. * For QEMU, we can work around the issue by writing out the feature bits with VIRTIO_F_VERSION_1 bit set. We (ab)use the finalize_features config op for this. This isn't enough to address all vhost devices since these do not get the features until FEATURES_OK, however it looks like the affected devices actually never handled the endianness for legacy mode correctly, so at least that's not a regression. [Fix] * 2f9a174f918e29608564c7a4e8329893ab604fb4 2f9a174f918e "virtio: write back F_VERSION_1 before validate" [Test Case] * Setup an IBM Z or LinuxONE LPAR with Ubuntu Server 20.04 as KVM host. * This Ubuntu KVM host can either be installed on FCP or DASD storage, but at least one DASD disk need to be reserved for a KVM guest. * Now hand over the reserved DASD disk (low-level formatted using dasdfmt and partitioned using fdasd) using 'virtio-block' to a KVM virtual machine (e.g. using a virsh VM config). * Try to install an Ubuntu KVM virtual machine using this DASD disk, that includes the check and read of the partition table. [Where problems could occur] * First of all requested commit contains one additional if statement; and is due tothat relatively traceable. * But the change is in /drivers/virtio/virtio.c, means in common code! * This issue obviously affects big endian systems only. * But if done wrong, it may effect in worst-case little endian systems, too! * But the if statement explicitly checks for '!virtio_legacy_is_little_endian()'. * Only virtio net and virtio blk devices seem to be affected. * And the commit/solutions was in-depth discussed upstream here: https://lore.kernel.org/all/20211011053921.1198936-1-pa...@linux.ibm.com/t/#u [Other] * Patches are upstream accepted with since 5.15-rc6 and tagged for upstream stable #v4.11. Hence jammy is not affected. * Request was to add the patches to focal / 20.04, but to avoid potential regressions on upgrades, the patches need to be added to impish and hirsute, too. * Fortunately cherry-picking the commit works cleanly from all the affected Ubuntu releases. __ Description: kernel: unable to read partitions on virtio-block dasd (kvm) Symptom: unable to read partitions on virtio-block dasd (kvm) Problem: verify is called before virtio_finalize_features() , so a transitional s390 virtio device still serves native endian (i.e. big endian) config space, while the driver knows that it is going to accept VERSION_1, so when reading the config space, it assumes it got little endian, and byteswaps. Solution: For QEMU, we can work around the issue by
[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
= hirsute verification =
ubuntu@blanka:~/nvidia-dgx-2/tests$ cat /proc/version
Linux version 5.11.0-42-generic (buildd@lgw01-amd64-041) (gcc (Ubuntu
10.3.0-1ubuntu1) 10.3.0, GNU ld (GNU Binutils for Ubuntu) 2.36.1) #46-Ubuntu
SMP Fri Nov 26 12:04:17 UTC 2021
ubuntu@blanka:~/nvidia-dgx-2/tests$ ./nvidia-peermem-test.sh
+ export DEBCONF_FRONTEND=noninteractive
+ DEBCONF_FRONTEND=noninteractive
+ export DEBIAN_PRIORITY=critical
+ DEBIAN_PRIORITY=critical
+ SERVER_IFACE=enp148s0
+ SERVER_IP=192.168.5.1/24
+ SERVER_IB_BDF=:4b:00.0
+ CLIENT_IFACE=enp18s0
+ CLIENT_IP=192.168.5.2/24
+ CLIENT_IB_BDF=:ba:00.0
+ trap cleanup EXIT
+ sudo service unattended-upgrades stop
+ install_cuda_perftest
+ local release
+ local components
+ dpkg-query -W -f '${Version}' perftest
+ grep -q '+cuda.1$'
+ return
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_0
dirname
../../devices/pci:00/:00:01.1/:01:00.0/:02:04.0/:0a:00.0/:0b:00.0/:0c:00.0/infiniband/mlx5_0
+++ dirname
../../devices/pci:00/:00:01.1/:01:00.0/:02:04.0/:0a:00.0/:0b:00.0/:0c:00.0/infiniband
++ basename
../../devices/pci:00/:00:01.1/:01:00.0/:02:04.0/:0a:00.0/:0b:00.0/:0c:00.0
+ bdf=:0c:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_1
dirname
../../devices/pci:00/:00:01.1/:01:00.0/:02:08.0/:10:00.0/:11:10.0/:12:00.0/infiniband/mlx5_1
+++ dirname
../../devices/pci:00/:00:01.1/:01:00.0/:02:08.0/:10:00.0/:11:10.0/:12:00.0/infiniband
++ basename
../../devices/pci:00/:00:01.1/:01:00.0/:02:08.0/:10:00.0/:11:10.0/:12:00.0
+ bdf=:12:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_2
dirname
../../devices/pci:40/:40:01.1/:41:00.0/:42:04.0/:49:00.0/:4a:00.0/:4b:00.0/infiniband/mlx5_2
+++ dirname
../../devices/pci:40/:40:01.1/:41:00.0/:42:04.0/:49:00.0/:4a:00.0/:4b:00.0/infiniband
++ basename
../../devices/pci:40/:40:01.1/:41:00.0/:42:04.0/:49:00.0/:4a:00.0/:4b:00.0
+ bdf=:4b:00.0
+ case "$bdf" in
++ basename /sys/class/infiniband/mlx5_2
+ server_ib_dev=mlx5_2
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_3
dirname
../../devices/pci:40/:40:01.1/:41:00.0/:42:08.0/:50:00.0/:51:10.0/:54:00.0/infiniband/mlx5_3
+++ dirname
../../devices/pci:40/:40:01.1/:41:00.0/:42:08.0/:50:00.0/:51:10.0/:54:00.0/infiniband
++ basename
../../devices/pci:40/:40:01.1/:41:00.0/:42:08.0/:50:00.0/:51:10.0/:54:00.0
+ bdf=:54:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_4
dirname
../../devices/pci:80/:80:01.1/:81:00.0/:82:04.0/:8b:00.0/:8c:00.0/:8d:00.0/infiniband/mlx5_4
+++ dirname
../../devices/pci:80/:80:01.1/:81:00.0/:82:04.0/:8b:00.0/:8c:00.0/:8d:00.0/infiniband
++ basename
../../devices/pci:80/:80:01.1/:81:00.0/:82:04.0/:8b:00.0/:8c:00.0/:8d:00.0
+ bdf=:8d:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_5
dirname
../../devices/pci:80/:80:01.1/:81:00.0/:82:08.0/:92:00.0/:93:10.0/:94:00.0/infiniband/mlx5_5
+++ dirname
../../devices/pci:80/:80:01.1/:81:00.0/:82:08.0/:92:00.0/:93:10.0/:94:00.0/infiniband
++ basename
../../devices/pci:80/:80:01.1/:81:00.0/:82:08.0/:92:00.0/:93:10.0/:94:00.0
+ bdf=:94:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_6
dirname
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:04.0/:b8:00.0/:b9:00.0/:ba:00.0/infiniband/mlx5_6
+++ dirname
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:04.0/:b8:00.0/:b9:00.0/:ba:00.0/infiniband
++ basename
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:04.0/:b8:00.0/:b9:00.0/:ba:00.0
+ bdf=:ba:00.0
+ case "$bdf" in
++ basename /sys/class/infiniband/mlx5_6
+ client_ib_dev=mlx5_6
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_7
dirname
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:08.0/:be:00.0/:bf:10.0/:cc:00.0/infiniband/mlx5_7
+++ dirname
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:08.0/:be:00.0/:bf:10.0/:cc:00.0/infiniband
++ basename
../../devices/pci:b0/:b0:01.1/:b1:00.0/:b2:08.0/:be:00.0/:bf:10.0/:cc:00.0
+ bdf=:cc:00.0
+ case "$bdf" in
+ for ibdev in /sys/class/infiniband/*
+ readlink /sys/class/infiniband/mlx5_8
[Kernel-packages] [Bug 1952385] Re: Fix missing external headset after resume problem for Cirrus CS8409 sound driver
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952385 Title: Fix missing external headset after resume problem for Cirrus CS8409 sound driver Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Triaged Status in linux-oem-5.13 source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, the external headset will fail to be detected after system resume. [Fix] Cirrus released a fix and send it upstream for approval. It's trying to schedule a harmless delayed work to do jack detection to reflect the real power state after resume. [Test] Plug-in an external headset in front headset port, suspend/resume the system then check whether the headset function works as expected. [Where problem could occur] Low. It only affect the platforms with Cirrus codec CS8409 which used to have problem. == Original Bug Description == [Summary] System can't detect external headset after suspend [Steps to reproduce] 1. install manifest and boot into OS 2. plug-in an external headset in front headset port 3. un-plug external headset 4. suspend system 5. resume system from suspend 6. plug-in an external headset [Expected result] System could detect external headset after suspend [Actual result] System can't detect external headset after suspend [Failure rate] 3/3 [Additional information] CID: 202110-29567 SKU: DLPV-SFF-DVT-C1 Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152 system-manufacturer: Dell Inc. system-product-name: Vostro 3710 bios-version: 0.13.73 CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x) GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4680] (rev 0c) kernel-version: 5.13.0-1019-oem [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
This bug is awaiting verification that the linux-oem-5.13/5.13.0-1021.25 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Committed Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Impish: In Progress Bug description: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946672] Re: Enable multicast in the "kvm" kernels
This bug is awaiting verification that the linux-kvm/5.4.0-1051.53 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1946672 Title: Enable multicast in the "kvm" kernels Status in cloud-images: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Focal: Fix Committed Bug description: I work in the OpenStack Neutron project and recently I wanted to optimize our CI scenario jobs by using Ubuntu minimal image as guest image for some tests (see patch https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/813195) Unfortunately it seems that there is problem with one multicast scenario test while using ubuntu-minimal image (https://cloud-images.ubuntu.com/minimal/releases/focal/release/ubuntu-20.04-minimal-cloudimg-amd64.img). The problem is that VM booted from that image don't subscribes properly to the IGMP multicast group thus test is failing. All works fine when image https://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64.img is used in the same test. The problem is that in the minimal image kernel linux-image-kvm (vs. linux-image-generic in the "regular" cloud image) and that "-kvm" image has disabled MULTICAST: # CONFIG_IP_MULTICAST is not set Would it be maybe possible to enable this option in the kernel used in the "minimal" cloud images? To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1946672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952621] Re: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24
This bug is awaiting verification that the linux-azure/5.4.0-1065.68 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-focal -- 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/1952621 Title: Bionic/linux-azure: Call trace on Ubuntu 18.04 VM with Standard NV24 Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-5.4 package in Ubuntu: New Status in linux-azure source package in Bionic: Invalid Status in linux-azure-5.4 source package in Bionic: Fix Committed Status in linux-azure source package in Focal: Fix Committed Status in linux-azure-5.4 source package in Focal: Invalid Bug description: SRU Justification [Impact] During large scale deployment testing, we found below call trace when provisioning Ubuntu 18.04 VM with size Standard_NV24. Engineer deployed instance 10 times and encountered once. It looks like a race condition when probe device, but finally all devices can be probed. [ 4.938162] sysfs: cannot create duplicate filename '/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/device:07/VMBUS:01/47505500-0003--3130-444531334632/pci0003:00/0003:00:00.0/config' [ 4.944816] sr 5:0:0:0: [sr0] scsi3-mmc drive: 0x/0x tray [ 4.951818] CPU: 0 PID: 135 Comm: kworker/0:2 Not tainted 5.4.0-1061-azure #64~18.04.1-Ubuntu [ 4.951820] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 4.958943] cdrom: Uniform CD-ROM driver Revision: 3.20 [ 4.955812] Workqueue: hv_pri_chan vmbus_add_channel_work [ 4.955812] Call Trace: [ 4.955812] dump_stack+0x57/0x6d [ 4.955812] sysfs_warn_dup+0x5b/0x70 [ 4.955812] sysfs_add_file_mode_ns+0x158/0x180 [ 4.955812] sysfs_create_bin_file+0x64/0x90 [ 4.955812] pci_create_sysfs_dev_files+0x72/0x270 [ 4.955812] pci_bus_add_device+0x30/0x80 [ 4.955812] pci_bus_add_devices+0x31/0x70 [ 4.955812] hv_pci_probe+0x48c/0x650 [ 4.955812] vmbus_probe+0x3e/0x90 [ 4.955812] really_probe+0xf5/0x440 [ 4.955812] driver_probe_device+0x11b/0x130 [ 4.955812] __device_attach_driver+0x7b/0xe0 [ 4.955812] ? driver_allows_async_probing+0x60/0x60 [ 4.955812] bus_for_each_drv+0x6e/0xb0 [ 4.955812] __device_attach+0xe4/0x160 [ 4.955812] device_initial_probe+0x13/0x20 [ 4.955812] bus_probe_device+0x92/0xa0 [ 4.955812] device_add+0x402/0x690 [ 4.955812] device_register+0x1a/0x20 [ 4.955812] vmbus_device_register+0x5e/0xf0 [ 4.955812] vmbus_add_channel_work+0x2c4/0x640 [ 4.955812] process_one_work+0x209/0x400 [ 4.955812] worker_thread+0x34/0x400 [ 4.955812] kthread+0x121/0x140 [ 4.955812] ? process_one_work+0x400/0x400 [ 4.955812] ? kthread_park+0x90/0x90 [ 4.955812] ret_from_fork+0x35/0x40 [ 5.043612] hv_pci 47505500-0004-0001-3130-444531334632: PCI VMBus probing: Using version 0x10002 [ 5.260563] hv_pci 47505500-0004-0001-3130-444531334632: PCI host bridge to bus 0004:00 Dexuan did some research and it looks like this is a longstanding race condition bug in the generic PCI subsystem (due to the timing, there can be more than 1 place where the PCI code tries to create the same ‘config’ sysfs file): https://patchwork.kernel.org/project/linux-pci/patch/20200716110423.xtfyb3n6tn5ixedh@pali/#23669641 The bug was reported on 7/16/2020, and the last reply was on 6/25/2021. It looks like this has not been fixed after 1+ year… Business Impact [Test Case] Repeated deployment on a Standard_NV24 instance. MS reported the reproduction rate is 3/551 before the patch, and 0/838 with the patch. [Where things could go wrong] Deployments could fail for other reasons. [Other info] SF: #00321027 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952234] Re: linux-azure: add Icelake servers support in no-HWP mode to cpufreq/intel_pstate driver
This bug is awaiting verification that the linux-azure/5.4.0-1065.68
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-focal' to 'verification-done-focal'. If the
problem still exists, change the tag 'verification-needed-focal' to
'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure-4.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1952234
Title:
linux-azure: add Icelake servers support in no-HWP mode to
cpufreq/intel_pstate driver
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Status in linux-azure source package in Hirsute:
Fix Committed
Status in linux-azure-4.15 source package in Hirsute:
Invalid
Status in linux-azure source package in Impish:
Fix Committed
Status in linux-azure-4.15 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting with the AH2020 Azure host build, Hyper-V is virtualizing
some registers that provide information about the CPU frequency. The
registers are read-only in a guest VM, so the guest can see the
frequency, but cannot make any modifications.
This feature also requires that the VM Configuration Version be 9.2 or
later, which means it needs to be a new VM type, such as the just
introduced Dv5/Ev5 series, and the new M832v2 VMs.
Within the Linux VM, the presence of the feature is indicated by the
“aperfmperf” flag in the “lscpu” flags output (or in the flags field
in /proc/cpuinfo).
It turns out there is a Linux kernel limitation when running on the
new Intel IceLake processors used for the Dv5/Ev5 series. Upstream
commit fbdc21e9b038 was added to provide IceLake support in the 5.14
kernel.
Microsoft has asked to backport fbdc21e9b038 commit to all supported
kernels.
[Test Plan]
Run Intel IceLake based VM and check the "aperfmperf" flag in the
"lscpu" flags output.
Without the patch the intel_pstate directory is missing from
/sys/devices/system/cpu/ and /sys/devices/system/cpu/cpufreq/ is
empty.
[Where problems could occur]
* intel_pstate driver is always used on Intel IceLake based VMs
without checking for presence of "aperfmperf" CPU flag.
* In earlier (5.4 and 4.15) linux-azure kernels when intel_pstate
driver is used it is in "active" mode instead of "passive" one (as
reported by "cat /sys/devices/system/cpu/intel_pstate/status", also
"cat /sys/devices/system/cpu/cpufreq/policy0/scaling_driver" returns
"intel_pstate" instead of "intel_cpufreq" which is the expected
behavior when in "active" mode).
If a consistent behavior across all kernel versions is desired commit
33aa46f252c7 ("cpufreq: intel_pstate: Use passive mode by default
without HWP") from the upstream should probably also be backported.
* /sys/devices/system/cpu/cpufreq/policy*/scaling_{min,max}_freq files
can be modified and the values reported by kernel will no longer match
the values used by hardware.
[Other Info]
None.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1952234/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938104] Re: shiftfs module is not built because CONFIG_SHIFT_FS is not set
Why is this invalid? I presume because there's the idmapped mounts feature. The problem is that this doesn't work in 5.13 when BTRFS is the underlying filesystem. So shiftfs is still useful. Its turned on in master build[1], why not for OEM, which is the only 5.13 available for focal? Here's a discussion suggesting that idmapped mounts for BTRFS won't be available till 5.15[2] [1] https://git.launchpad.net/~canonical-kernel/ubuntu/+source/linux-oem/+git/focal/commit/?h=oem-5.13&id=c79066e1cb62dee340b050e98284939bcdabef0f [2] https://discuss.linuxcontainers.org/t/are-there-plans-to-map-shiftfs-config-option-to-new-5-12-kernel-id-mapping/11704/5?u=crass -- 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/1938104 Title: shiftfs module is not built because CONFIG_SHIFT_FS is not set Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: New Bug description: Shiftfs is built and included in all other ubuntu kernels that I know of and if I'm not mistaken is sponsored by ubuntu mostly for use with LXD containers, which is my use case. It also included in the linux- oem-5.10. Is there a reason shiftfs is not included in the 5.13 oem release? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1938104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953192] [NEW] Enable Landlock by default
Public bug reported: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953192 Title: Enable Landlock by default Status in linux package in Ubuntu: New Bug description: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953192] 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 1953192 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/1953192 Title: Enable Landlock by default Status in linux package in Ubuntu: Incomplete Bug description: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
He is using the intel_pstate CPU frequency scaling driver. Now by default processors without HWP will boot into the intel_pstate driver in passive mode (A.K.A. intel_cpufreq). -- 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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional
[Kernel-packages] [Bug 1953192] Re: Enable Landlock by default
** Changed in: linux (Ubuntu) Status: Incomplete => 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/1953192 Title: Enable Landlock by default Status in linux package in Ubuntu: New Bug description: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953192] 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 1953192 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/1953192 Title: Enable Landlock by default Status in linux package in Ubuntu: Incomplete Bug description: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930868] Re: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in packag
** Changed in: linux-firmware (Ubuntu Jammy) Status: Triaged => Fix Committed -- 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/1930868 Title: [SRU][Jammy]Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof- apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Committed Status in firmware-sof source package in Jammy: Triaged Status in linux-firmware source package in Jammy: Fix Committed Bug description: SRU template for firmware-sof-signed: [Impact] We put the Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be downloaded and unpacked first, this will introduce below errors: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] Need to put Replaces: linux-firmware (<= 1.203) in the debian/control, and the sof-tplg is a symbol link in the firmware-sof-signed, when it replaces the sof-tplg folder in the linux-firmware of old version, it will generate an empty sof-tplg folder, there are no any topology files in the folder and the symbol link is not generated. To solve it, modify the debian/rules to change symbol link to a copy of folder. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. SRU template for linux-firmware: [Impact] In the past we put the sof-firmware files into the linux-firmware, and about half year ago, the sof-firmware has its own debian package, it is firmware-sof-signed, here we remove the sof-firmware files from linux-firmware and replace them with the package firmware-sof-signed. Here put Recommends: firmware-sof-signed (>= 1.9-1) in the linux-firmware/debian/control, when upgrading the linux-firmware, the firmware-sof-signed will be unpacked first, it will have conflicts because this package update the same files in the linux-firmware of old version, so apart of this pull-request to linux-firmware, also need to do some change on firmware-sof-signed. Please see the debdiff for firmware-sof-signed in the launchpad. This is the error log when unpacking the firmware-sof-signed: Unpacking firmware-sof-signed (1.9-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-bdw.ri', which is also in package linux-firmware 1.202 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Preparing to unpack .../linux-firmware_1.202+staging.1_all.deb ... Unpacking linux-firmware (1.202+staging.1) over (1.202) ... Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.9-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) [Fix] remove the sof-firmware files from linux-firmware, and replace them with a debian package firmware-sof-signed. [Test] put the updated firmware-sof-signed and linux-firmware to my ppa, and run sudo apt install linux-firmware, then the two packages are upgraded and installed, reboot all audio function work as well as before. [Where problems could occur] The firmware-sof-signed doesn't contain all files that we plan to remove from linux-firmware, but there is no evidence that those files are used by any platforms, If some platforms fail to load the sof-firmware or topology files and audio function fail to work, it is possibily this SRU introduce the regression. (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1
[Kernel-packages] [Bug 1953199] [NEW] 0-byte files created in overlay filesystem
Public bug reported: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable. [0] https://github.com/docker/for-linux/issues/1015 [1] https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569 [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2 [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668 --- I reproduced this bug in Ubuntu 18.04: ``` # bash test.sh Sending build context to Docker daemon 43.05kB Step 1/2 : FROM debian:10.8-slim ---> 115566c891d1 Step 2/2 : RUN apt update && apt install -y gcc strace ---> Using cache ---> 0dfb7ffcd427 Successfully built 0dfb7ffcd427 Successfully tagged strace:latest Local: OK Docker - mounted: Copy failed Docker - copied: OK ``` ``` root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd Description:Ubuntu 18.04.6 LTS Release:18.04 root@stanhu-ubuntu-18:/home/stanhu# uname -r 5.4.0-1057-gcp ``` Per [the latest update on the kernel stable mailing list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the kernel backport fix for 5.10 has been queued for review and should land in the [`stable-5.10.y` branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) soon. To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now, unless you backport the two patches below: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 1. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc I've confirmed that 5.5.19 does NOT have this bug, and it was introduced in 5.6.0 via https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2. ** Affects: linux-base (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-base (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/1953199 Title: 0-byte files created in overlay filesystem Status in linux-base package in Ubuntu: New Bug description: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable.
[Kernel-packages] [Bug 1953199] Re: 0-byte files created in overlay filesystem
* Ubuntu 18.04.6 LTS appears affected. * Ubuntu 20.04.3 LTS does NOT appear affected with the Linux 5.11 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1953199 Title: 0-byte files created in overlay filesystem Status in linux-base package in Ubuntu: New Bug description: Copied from https://lore.kernel.org/stable/CAMBWrQ=1mkxnmt_6jnqp_xxr7psvywpbjc6p1qcy9eny8rf...@mail.gmail.com/: A number of users have reported that under certain conditions using the overlay filesystem, copy_file_range() can unexpectedly create a 0-byte file. [0] This bug can cause significant problems because applications that copy files expect the target file to match the source immediately after the copy. After upgrading from Linux 5.4 to Linux 5.10, our Docker-based CI tests started failing due to this bug, since Ruby's IO.copy_stream uses this system call. We have worked around the problem by touching the target file before using it, but this shouldn't be necessary. Other projects, such as Rust, have added similar workarounds. [1] As discussed in the linux-fsdevel mailing list [2], the bug appears to be present in Linux 5.6 to 5.10, but not in Linux 5.11. We should be able to cherry-pick the following upstream patches to fix this. Could you cherry-pick them to 5.10.x stable? I've confirmed that these patches, applied from top to bottom to that branch, pass the reproduction test [3]: 82a763e61e2b601309d696d4fa514c77d64ee1be 9b91b6b019fda817eb52f728eb9c79b3579760bc The diffstat: fs/overlayfs/file.c | 59 +++ 1 file changed, 31 insertions(+), 28 deletions(-) Note that these patches do not pick cleanly into 5.6.x - 5.9.x stable. [0] https://github.com/docker/for-linux/issues/1015 [1] https://github.com/rust-lang/rust/blob/342db70ae4ecc3cd17e4fa6497f0a8d9534ccfeb/library/std/src/sys/unix/kernel_copy.rs#L565-L569 [2] https://marc.info/?l=linux-fsdevel&m=163847383311699&w=2 [3] https://github.com/docker/for-linux/issues/1015#issuecomment-841915668 --- I reproduced this bug in Ubuntu 18.04: ``` # bash test.sh Sending build context to Docker daemon 43.05kB Step 1/2 : FROM debian:10.8-slim ---> 115566c891d1 Step 2/2 : RUN apt update && apt install -y gcc strace ---> Using cache ---> 0dfb7ffcd427 Successfully built 0dfb7ffcd427 Successfully tagged strace:latest Local: OK Docker - mounted: Copy failed Docker - copied: OK ``` ``` root@stanhu-ubuntu-18:/home/stanhu# lsb_release -rd Description: Ubuntu 18.04.6 LTS Release: 18.04 root@stanhu-ubuntu-18:/home/stanhu# uname -r 5.4.0-1057-gcp ``` Per [the latest update on the kernel stable mailing list](https://lore.kernel.org/stable/yanx6kobwiqob...@kroah.com), the kernel backport fix for 5.10 has been queued for review and should land in the [`stable-5.10.y` branch](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=linux-5.10.y) soon. To avoid this bug, I'd suggest avoid Linux v5.6.0 - v5.10.83 for now, unless you backport the two patches below: 1. https://github.com/torvalds/linux/commit/@82a763e61e2b601309d696d4fa514c77d64ee1be 1. https://github.com/torvalds/linux/commit/@9b91b6b019fda817eb52f728eb9c79b3579760bc I've confirmed that 5.5.19 does NOT have this bug, and it was introduced in 5.6.0 via https://github.com/torvalds/linux/commit/1a980b8cbf0059a5308eea61522f232fd03002e2. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1953199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-dell300x/4.15.0.1032.34)
All autopkgtests for the newly accepted linux-meta-dell300x (4.15.0.1032.34) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64) 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/bionic/update_excuses.html#linux-meta-dell300x [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 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1051.50)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1051.50) for focal have finished running. The following regressions have been reported in tests triggered by the package: oss4/4.2-build2010-5ubuntu6~20.04.3 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.3 (amd64) lttng-modules/2.12.5-1ubuntu2~20.04.1 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) evdi/1.9.1-1ubuntu4~20.04.1 (amd64) virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.4 (amd64) 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/focal/update_excuses.html#linux-meta-kvm [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 1953202] [NEW] Bionic update: upstream stable patchset 2021-12-03
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-12-03 Ported from the following upstream stable releases: v4.14.254, v4.19.215 v4.19.216 v4.14.255, v4.19.217 from git://git.kernel.org/ ARM: 9133/1: mm: proc-macros: ensure *_tlb_fns are 4B aligned ARM: 9134/1: remove duplicate memcpy() definition ARM: 9139/1: kprobes: fix arch_init_kprobes() prototype ARM: 8819/1: Remove '-p' from LDFLAGS usbnet: sanity check for maxpacket usbnet: fix error return code in usbnet_probe() ata: sata_mv: Fix the error handling of mv_chip_id() nfc: port100: fix using -ERRNO as command type mask ipv4: use siphash instead of Jenkins in fnhe_hashfun() mmc: vub300: fix control-message timeouts mmc: dw_mmc: exynos: fix the finding clock sample value mmc: sdhci: Map more voltage level to SDHCI_POWER_330 mmc: sdhci-esdhc-imx: clear the buffer_read_ready to reset standard tuning circuit net: lan78xx: fix division by zero in send path regmap: Fix possible double-free in regcache_rbtree_exit() net: batman-adv: fix error handling nios2: Make NIOS2_DTB_SOURCE_BOOL depend on !COMPILE_TEST net: nxp: lpc_eth.c: avoid hang when bringing interface down sctp: use init_tag from inithdr for ABORT chunk sctp: fix the processing for COOKIE_ECHO chunk sctp: add vtag check in sctp_sf_violation sctp: add vtag check in sctp_sf_do_8_5_1_E_sa sctp: add vtag check in sctp_sf_ootb ARM: 9141/1: only warn about XIP address when not compile testing arm64: Avoid premature usercopy failure ipv6: use siphash in rt6_exception_hash() ipv6: make exception cache less predictible arm64: dts: allwinner: h5: NanoPI Neo 2: Fix ethernet node UBUNTU: upstream stable to v4.14.254, v4.19.215 scsi: core: Put LLD module refcnt after SCSI device is released media: firewire: firedtv-avc: fix a buffer overflow in avc_ca_pmt() sfc: Fix reading non-legacy supported link modes ARM: 9120/1: Revert "amba: make use of -1 IRQs warn" UBUNTU: upstream stable to v4.19.216 mm/zsmalloc: Prepare to variable MAX_PHYSMEM_BITS arch: pgtable: define MAX_POSSIBLE_PHYSMEM_BITS where needed block: introduce multi-page bvec helpers Revert "x86/kvm: fix vcpu-id indexed array sizes" usb: gadget: Mark USB_FSL_QE broken on 64-bit usb: musb: Balance list entry in musb_gadget_queue usb-storage: Add compatibility quirk flags for iODD 2531/2541 printk/console: Allow to disable console output by using console="" or console=null isofs: Fix out of bound access for corrupted isofs image comedi: dt9812: fix DMA buffers on stack comedi: ni_usb6501: fix NULL-deref in command paths comedi: vmk80xx: fix transfer-buffer overflows comedi: vmk80xx: fix bulk-buffer overflow comedi: vmk80xx: fix bulk and interrupt message timeouts staging: r8712u: fix control-message timeout staging: rtl8192u: fix control-message timeouts rsi: fix control-message timeout usb: ehci: handshake CMD_RUN instead of STS_HALT UBUNTU: upstream stable to v4.14.255, v4.19.217 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** 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 Lin
[Kernel-packages] [Bug 1953192] Re: Enable Landlock by default
See patch: https://lore.kernel.org/all/20211203185226.1957311-2-...@digikod.net/ ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953192 Title: Enable Landlock by default Status in linux package in Ubuntu: Confirmed Bug description: Hi, The Landlock security feature is built in Ubuntu kernel since 5.13 which is great! However, it is not enough to enable the CONFIG_SECURITY_LANDLOCK option as described in the related help. The CONFIG_LSM option needs to be prepended by "landlock," to make Landlock system calls available without modifying the kernel boot arguments. Could you please update the CONFIG_LSM variable accordingly? Regards, Mickaël To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953208] [NEW] Fix bogus HDMI audio interface
Public bug reported: [Impact] Bogus HDMI audio can be selected as output, without any HDMI monitor connected. [Fix] Consider 0 SAD as invalid ELD - no SAD means no audio. [Test] With the patch applied, no bogus HDMI audio can be found in GNOME's setting app. [Where problems could occur] Basically none. No SAD means no PCM - so it has never worked before. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Tags: oem-priority originate-from-1950580 somerville ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Low ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low ** Tags added: oem-priority originate-from-1950580 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953208 Title: Fix bogus HDMI audio interface Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Confirmed Bug description: [Impact] Bogus HDMI audio can be selected as output, without any HDMI monitor connected. [Fix] Consider 0 SAD as invalid ELD - no SAD means no audio. [Test] With the patch applied, no bogus HDMI audio can be found in GNOME's setting app. [Where problems could occur] Basically none. No SAD means no PCM - so it has never worked before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1953208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-azure/5.4.0.1065.63)
All autopkgtests for the newly accepted linux-meta-azure (5.4.0.1065.63) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.3 (amd64) 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/focal/update_excuses.html#linux-meta-azure [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 1786013] Autopkgtest regression report (linux-meta-hwe-5.4/5.4.0.92.103~18.04.82)
All autopkgtests for the newly accepted linux-meta-hwe-5.4 (5.4.0.92.103~18.04.82) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxc/3.0.3-0ubuntu1~18.04.1 (ppc64el, s390x, amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) asic0x/1.0.1-1 (s390x) v4l2loopback/0.10.0-1ubuntu1.2 (s390x) acpi-call/1.1.0-4 (ppc64el, s390x) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) 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/bionic/update_excuses.html#linux-meta-hwe-5.4 [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 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
Yes I can get it to boot into active mode thanks to Doug, but after several minutes the cpu drops to 798-800mhz and won't increase no matter if I try and change it. I did notice that the scaling_governor always boots to powersave mode. When I change it to performance after several minutes the cpu drops to 798-800mhz again. I did find a similar problem "Linux kernel 5.8 defaults to passive mode for intel_pstate driver for cpu before skylake" but it always boots to the powersave governor and changing it doesn't fix the issue. https://www.reddit.com/r/linux/comments/ihdozd/linux_kernel_58_defaults_to_passive_mode_for/ -- 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/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds:
[Kernel-packages] [Bug 1931001]
This bug is believed to be fixed in kernel v5.16 by the following 2 commits: commit 03a976c9afb5e3c4f8260c6c08a27d723b279c92 Author: Jarkko Nikula Date: Wed Nov 17 11:45:09 2021 +0200 i2c: i801: Fix interrupt storm from SMB_ALERT signal commit 9b5bf5878138293fb5b14a48a7a17b6ede6bea25 Author: Jean Delvare Date: Tue Nov 9 16:02:57 2021 +0100 i2c: i801: Restore INTREN on unload -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
** Changed in: linux Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in Linux: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in Fedora: Confirmed Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1931001/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
