[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0 in HP x360 machines
Thanks. Yes it sounds like you had an old proposed kernel, in between the current 'updates' and 'proposed' versions. But no matter, if the bug is fixed in "5.13.0-28-generic #31" then great! ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1806396 Title: lis3lv02d: unknown sensor type 0x0 in HP x360 machines Status in Linux: Confirmed Status in linux package in Ubuntu: Fix Released Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0 in HP x360 machines
I am on the proposed-channel. I don't know how I got that version but I switched to "normal". Output of uname -a ... 5.13.0-28-generic #31-Ubuntu SMP ... Seems to be the one you mentioned. -- 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/1806396 Title: lis3lv02d: unknown sensor type 0x0 in HP x360 machines Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960287] [NEW] Blutooth mouse loses connection with the 1022 several times after login, not with the 1005.
Public bug reported: To be more precise, after logging in I normally press a button on the mouse, then the Blutooth icon shows me the connection as active in the bar. After 5-10 seconds it is gone again. The mouse no longer reacts. It takes about 20 seconds, then I have a connection again for about 5-10 seconds. The whole thing happens 2-4 times. After that it remains stable. I will set the timeout to 0. I did not notice this under 1005 ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New -- 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/1960287 Title: Blutooth mouse loses connection with the 1022 several times after login, not with the 1005. Status in linux-oem-5.14 package in Ubuntu: New Bug description: To be more precise, after logging in I normally press a button on the mouse, then the Blutooth icon shows me the connection as active in the bar. After 5-10 seconds it is gone again. The mouse no longer reacts. It takes about 20 seconds, then I have a connection again for about 5-10 seconds. The whole thing happens 2-4 times. After that it remains stable. I will set the timeout to 0. I did not notice this under 1005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1960287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With the Nvidia driver installed there is no option to use Wayland on the login screen
** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided => Low -- 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/1946200 Title: With the Nvidia driver installed there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-495 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0 in HP x360 machines
Interesting because I thought you were using Ubuntu 21.10 but that's not a listed kernel version for 21.10: https://launchpad.net/ubuntu/impish/+source/linux If you can verify the fix is in a version that's in Ubuntu then we can mark the bug as fixed. -- 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/1806396 Title: lis3lv02d: unknown sensor type 0x0 in HP x360 machines Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960094] Re: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal
I think the strlcat thing is a red herring or an indication that the test environment is somehow in a bad shape. This could be explained if there was two versions of liblxc on the system for example. Outside of that, I'm also seeing: ``` lxc-start tmp.KEpxw2rh0e 20220205081512.354 ERRORutils - utils.c:__safe_mount_beneath_at:1106 - Function not implemented - Failed to open 30(full) ``` Which isn't a test issue but an actual failure. It could once again come from a bad test environment with mismatching library/binary somehow, but if the test environment isn't the issue, then you have a kernel regression on your hands as that's not one of those transient test failures. -- 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/1960094 Title: lxc/1:4.0.6-0ubuntu1~20.04.1 undefined symbol: strlcat in Focal Status in linux package in Ubuntu: New Status in lxc package in Ubuntu: Incomplete Status in linux source package in Focal: New Status in lxc source package in Focal: Incomplete Bug description: There are failures in ubuntu_lxc regression tests on Focal/linux/5.4.0-99.112 sru cycle 2022.01.03 with the error lxc-create: symbol lookup error: lxc-create: undefined symbol: strlcat These errors did not appear on previous kernels in the same cycle and now have a few tests failing on all architectures and systems as of Feb 4th 2022 it seems. Log with details is attached in the comments. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960094/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944018] Re: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310
Matt, double-thank you for pointing out the OEM kernel versioning system I had no idea existed. Plus, I have been testing the C kernel for two weeks now and had no issues with the WIFI waking up. (I had, though, an issue with the Bluetooth not reconnecting my devices correctly a couple of times -- a different issue that may be related to the current patch(?) -- but it can be solved with turning BT off and on again.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1944018 Title: ath11k_pci sometimes crashes on suspend/resume on Dell XPS 13 9310 Status in linux-oem-5.10 package in Ubuntu: Confirmed Bug description: Sometimes when my Dell XPS 13 9310 resumes from suspend, the display fails to show anything for a short while. When the display does show, the wireless network is no longer working. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.10.0-1045-oem 5.10.0-1045.47 ProcVersionSignature: Ubuntu 5.10.0-1045.47-oem 5.10.46 Uname: Linux 5.10.0-1045-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Sat Sep 18 12:04:49 2021 Dependencies: InstallationDate: Installed on 2021-09-13 (4 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.10/+bug/1944018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954416] Re: shutdown linux
Bug report won't expire due to bug watch. No response to comment #1 after nearly two months Looks like reporter running an EOL release Closing as "Invalid" ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954416 Title: shutdown linux Status in linux package in Ubuntu: Invalid Bug description: why when I turn off / reboot it gets stuck on the logo, please fix the kernel. my kernel version 3.13.0-22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954416/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
The following devices are breaking away after connecting the scanner (compared lsusb -v -v -v before and afterwards): Bus 002 Device 003: ID 05e3:0612 Genesys Logic, Inc. idVendor 0x05e3 Genesys Logic, Inc. Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc. idVendor 0x05e3 Genesys Logic, Inc. Bus 001 Device 003: ID 1038:1122 SteelSeries ApS idVendor 0x1038 SteelSeries ApS Bus 001 Device 009: ID 05e3:0610 Genesys Logic, Inc. 4-port hub idVendor 0x05e3 Genesys Logic, Inc. Bus 001 Device 006: ID 1a40:0101 Terminus Technology Inc. Hub idVendor 0x1a40 Terminus Technology Inc. Bus 001 Device 007: ID 0b95:6802 ASIX Electronics Corp. idVendor 0x0b95 ASIX Electronics Corp. Bus 001 Device 004: ID 1a40:0101 Terminus Technology Inc. Hub idVendor 0x1a40 Terminus Technology Inc. Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub idVendor 0x05e3 Genesys Logic, Inc. Wireless also seems to be kicked out Bus 001 Device 014: ID 2357:0009 idVendor 0x2357 bFunctionClass224 Wireless Bus 001 Device 008: ID 5986:0547 Acer, Inc seems to be the video camera idVendor 0x5986 Acer, Inc bFunctionClass 14 Video Bus 001 Device 005: ID 8087:0aa7 Intel Corp. idVendor 0x8087 Intel Corp. bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth so bluetooth is dead also. :-( I am using a LTE/WLAN router which is connected to USB, the connection is also lost of course. Keyboard on USB and Logitech, Inc. Unifying Receiver for mouse are kicked out as already written. I have to reboot after that error. -- 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: Confirmed Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
** 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: Confirmed Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
I do not actually know about Focal... but is NOT fixed in Impish, and this is the only thing assigned to a person. ** Changed in: linux (Ubuntu Impish) Status: Fix Released => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: Fix Released => Confirmed -- 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/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-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: Confirmed Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953671] Re: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion
Any news on this one? I can boot the Ubuntu Jammy desktop using acpi=force and install the desktop. However, on subsequent boots it hangs with the same error in spite of the changed grub config. Also, shutdown does not work at all. Ubuntu just hangs silently. This is on VMware Fusion (latest tech preview) on a Mac Mini 2020 M1. -- 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/1953671 Title: 5.15 and 5.16 arm64 kernels fail to boot in VMWare Fusion Status in linux package in Ubuntu: Confirmed Bug description: I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: https://blogs.vmware.com/teamfusion/2021/09/fusion-for-m1-public-tech- preview-now-available.html I am successfully using the 5.14 kernel series (currently 5.14.21-051421-generic) but note this is now EOL. However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after: EFI stub: Booting Linux Kernel... EFI stub: EFI_RNG_PROTOCOL unavailable EFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundary EFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory region EFI stub: Using DIB from configuration table EFI stub: Exiting boot services... I see the same "hang" for both 5.15.7 and 5.16-rc4. FYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: https://communities.vmware.com/t5/Fusion-for-Apple-Silicon- Tech/Anyone-have-any-luck-with-Ubuntu-5-15-kernels/m-p/2880362 Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: cat /proc/version However I attach the output from lspci. Please let me know what other information I can provide to help diagnose this issue. Thanks --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (26 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) Package: linux-image-generic 5.13.0.21.32 [origin: unknown] PackageArchitecture: arm64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash Tags: jammy uec-images third-party-packages Uname: Linux 5.14.21-051421-generic aarch64 UnreportableReason: This does not seem to be an official Ubuntu package. Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UpgradeStatus: Upgraded to jammy on 2021-11-15 (23 days ago) UserGroups: N/A _MarkForUpload: True --- ProblemType: Bug AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Dec 17 11:38 seq crw-rw+ 1 root audio 116, 33 Dec 17 11:38 timer AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.13.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu74 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/seq:myitcv 1543 F pipewire CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-12 (34 days ago) InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: VMware, Inc. VBSA Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic root=UUID=7378d8ea-883e-47b8-b5ab-a92790860f9c ro ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 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-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.202 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: jammy uec-images Uname: Linux 5.13.0-21-generic aarch64 UpgradeStatus: Upgraded to jammy on 2021-11-15 (31 days ago) UserGroups: N/A _MarkForUpload: True acpidump: dmi.bios.date: 12/31/2020 dmi.bios.release: 0.0 dmi.bios.vendor: VMware dmi.bios.version: VEFI dmi.board.name: VBSA dmi.board.vendor: VMware dmi.board.version: 1 dmi.chassis.type: 1 dmi.chassis.vendor: VMware dmi.chassis.version: VBSA dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnVMware:bvrVEFI:bd12/31/2020:br0.0:efr0.0:svnVMware,Inc.:pnVBSA:pvr1:rvnVMware:rnVBSA:rvr1:cvnVMware:ct1:cvrVBSA:sku0001:
[Kernel-packages] [Bug 1956849] Re: Almost all USB ports suddenly stopped working; unbootable
I am experiencing the same problem with a brandnew brother DS-740D scanner, when connecting the scanner to a USB3.0 port on a MSI GE63 7RD laptop with Ubuntu 18.04 LTS, mouse and keyboard connected to USB are dead afterwards. touchpad and keyboard directly on the machine are still working. On Win10 the scanner works. journalctl | grep -7 "controller not responding" Feb 07 14:02:26 machine5 kernel: xhci_hcd :00:14.0: Abort failed to stop command ring: -110 Feb 07 14:02:26 machine5 kernel: xhci_hcd :00:14.0: xHCI host controller not responding, assume dead Feb 07 14:02:26 machine5 kernel: xhci_hcd :00:14.0: HC died; cleaning up Feb 07 14:02:26 machine5 kernel: xhci_hcd :00:14.0: Timeout while waiting for setup device command Feb 07 14:02:26 machine5 kernel: usb 1-3: USB disconnect, device number 2 Feb 07 14:02:26 machine5 kernel: usb 1-3.1: USB disconnect, device number 4 Feb 07 14:02:26 machine5 kernel: usb 1-3.1.3: USB disconnect, device number 7 Feb 07 14:02:26 machine5 kernel: usb 1-3.1.3.1: USB disconnect, device number 10 No "VIA Labs, Inc" USB host devices. Linux machine5 4.15.0-167-generic #175-Ubuntu SMP Wed Jan 5 01:56:07 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux So having a brandnew scanner and not getting it to work because of Ubuntu is quite a new experience. :-/ -- 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/1956849 Title: Almost all USB ports suddenly stopped working; unbootable Status in linux package in Ubuntu: Incomplete Bug description: This package needs to be pulled NOW. It disables almost all USB-3.0 and USB-C ports completely. Even though I had automatic software updates turned OFF (or so I thought), my Mac Pro suddenly got a new kernel when I rebooted it this morning: Linux macpro-obs 5.11.0-44-generic #48~20.04.2-Ubuntu SMP Tue Dec 14 15:36:44 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux and it contains a P0 showstopper bug. Upon rebooting, I got dropped into the initrd prompt because Linux could not see the external USB drive that I'm booting from (WDBAGF5000AGY-WESN). I wasted an entire day figuring out what was wrong, and even went so far as to order a replacement SSD, planning to rebuild everything from scratch, because the drive failed to appear in every single USB port I tried. Then I discovered that a different SSD didn't work, either. At that point, I realized that something else was wrong, and I kept trying until I found one other port that worked. I was then able to boot and get dmesg and lsusb output. This kernel update broke not only the built-in ports, but also the ports on a generic USB-C PCIe card (Amazon B08PF8XR73). Mac Pro built-in USB-3.0(A) ports (2x): working Mac Pro built-in USB-C ports (4x): dead USB-C PCIe card USB-C ports (2x): dead USB-C PCIe card USB-3.0(A) ports (5x): dead All devices fail to appear in lsusb when attached to the port, including an Apple USB keyboard, an Anker USB-C Ethernet adapter, a WD SSD, and a Sandisk SSD. I'm going to roll back my kernel to a working kernel, but this package needs to be pulled NOW before it affects too many people. This is too catastrophic a bug to wait even a day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Same issue on my new HP Laptop 15s-fq2000nb (https://support.hp.com/be- fr/document/c07043807), and I confirm that the issue is still there and the PC is unusable while the Wifi is on. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-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 Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Released Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Confirmed Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960256] Re: compilation errors due to "peermem" module
** Summary changed:
- compilation due to "peermem" module
+ compilation errors due to "peermem" module
--
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/1960256
Title:
compilation errors due to "peermem" module
Status in nvidia-graphics-drivers-470 package in Ubuntu:
New
Bug description:
Installed with the following:
apt-get install --no-install-recommends nvidia-driver-470 nvidia-
modprobe libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470
libnvidia-decode-470 libnvidia-encode-470 libnvidia-extra-470
libnvidia-fbc1-470 libnvidia-gl-470 libnvidia-ifr1-470 nvidia-compute-
utils-470 nvidia-dkms-470 nvidia-driver-470 nvidia-kernel-common-470
nvidia-kernel-source-470 nvidia-utils-470 xserver-xorg-video-
nvidia-470
Seems to generate /var/crash/nvidia-dkms-470.0.crash (tail -20):
/usr/bin/ld.bfd -m elf_x86_64 -z max-page-size=0x20-r -o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-drv.o […] { echo
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o […]
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-format.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.mod
make -f ./scripts/Makefile.modpost
sed 's/ko$/o/' /var/lib/dkms/nvidia/470.103.01/build/modules.order |
scripts/mod/modpost -m -a -i ./Module.symvers -I
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -e
/usr/src/ofa_kernel/default/Module.symvers -o
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -s -T -
FATAL: parse error in symbol dump file
scripts/Makefile.modpost:93: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1675: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-97-generic'
Makefile:80: recipe for target 'modules' failed
make: *** [modules] Error 2
DKMSKernelVersion: 5.4.0-97-generic
Date: Mon Feb 7 11:32:36 2022
Package: nvidia-dkms-470 470.103.01-0ubuntu0.18.04.1
PackageVersion: 470.103.01-0ubuntu0.18.04.1
SourcePackage: nvidia-graphics-drivers-470
Title: nvidia-dkms-470 470.103.01-0ubuntu0.18.04.1: nvidia kernel module
failed to build
It is added:
# dkms status -k `uname -r`
iser, 4.7: added
kernel-mft-dkms, 4.13.0, 5.4.0-97-generic, x86_64: installed
knem, 1.1.3.90mlnx1: added
mlnx-ofed-kernel, 4.7: added
nvidia, 470.103.01: added
rshim, 1.8, 5.4.0-97-generic, x86_64: installed
srp, 4.7: added
However, doing a build gets:
dkms build nvidia/470.103.01
Kernel preparation unnecessary for this kernel. Skipping...
applying patch
disable_fstack-clash-protection_fcf-protection.patch...patching file Kbuild
Hunk #1 succeeded at 82 (offset 11 lines).
Building module:
cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1
'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.4.0-97-generic
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/5.4.0-97-generic/build LD=/usr/bin/ld.bfd
modules.(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-dkms-470.0.crash'
Error! Bad return status for module build on kernel: 5.4.0-97-generic (x86_64)
Consult /var/lib/dkms/nvidia/470.103.01/build/make.log for more information.
Which I suspect is related to the "peermem" module:
{ echo /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-drv.o [...]
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-format.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.mod
/usr/bin/ld.bfd -m elf_x86_64 -z max-page-size=0x20-r -o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem/nvidia-peermem.o
{ echo
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem/nvidia-peermem.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem.mod
make -f ./scripts/Makefile.modpost
sed 's/ko$/o/' /var/lib/dkms/nvidia/470.103.01/build/modules.order |
scripts/mod/modpost -m -a -i ./Module.symvers -I
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -e
/usr/src/ofa_kernel/default/Module.symvers -o
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -s -T -
FATAL: parse error in symbol dump file
scripts/Makefile.modpost:93: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1675: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-97-generic'
Makefile:80: recipe for target 'modules' failed
make: *** [modules]
[Kernel-packages] [Bug 1909814] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1909814 Title: Medion Notebook Keyboard not working Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] The keyboard of some medion laptops can't work under Linux. [Fix] Backport a upstream patch, after applying the patch, the keyboard will skip the irq override from the acpi resource layer, and the keyboard could work normally. [Test] Booting the patched kernel, use the keyboard to do the input. [Where problems could occur] The patch will skip the irq override based on the DMI info, so if a medion laptop which has the same DMI info and the irq 1 needs to be overriden, this patch will introduce regression on the machine, but this possibility is very low. If this happens, we will consider to add more DMI match info in the table. Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1944756] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1944756 Title: Focal update: v5.4.144 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.144 upstream stable release from git://git.kernel.org/ net: qrtr: fix another OOB Read in qrtr_endpoint_post ARC: Fix CONFIG_STACKDEPOT netfilter: conntrack: collect all entries in one cycle once: Fix panic when module unload ovl: fix uninitialized pointer read in ovl_lookup_real_one() mmc: sdhci-msm: Update the software timeout value for sdhc mm, oom: make the calculation of oom badness more accurate can: usb: esd_usb2: esd_usb2_rx_event(): fix the interchange of the CAN RX and TX error counters Revert "USB: serial: ch341: fix character loss at high transfer rates" USB: serial: option: add new VID/PID to support Fibocom FG150 usb: dwc3: gadget: Fix dwc3_calc_trbs_left() usb: dwc3: gadget: Stop EP0 transfers during pullup disable scsi: core: Fix hang of freezing queue between blocking and running device RDMA/bnxt_re: Add missing spin lock initialization IB/hfi1: Fix possible null-pointer dereference in _extend_sdma_tx_descs() e1000e: Fix the max snoop/no-snoop latency for 10M RDMA/efa: Free IRQ vectors on error flow ip_gre: add validation for csum_start xgene-v2: Fix a resource leak in the error handling path of 'xge_probe()' net: marvell: fix MVNETA_TX_IN_PRGRS bit number rtnetlink: Return correct error on changing device netns net: hns3: clear hardware resource when loading driver net: hns3: fix duplicate node in VLAN list net: hns3: fix get wrong pfc_en when query PFC configuration drm/i915: Fix syncmap memory leak usb: gadget: u_audio: fix race condition on endpoint stop perf/x86/intel/uncore: Fix integer overflow on 23 bit left shift of a u32 opp: remove WARN when no valid OPPs remain virtio: Improve vq->broken access to avoid any compiler optimization virtio_pci: Support surprise removal of virtio pci device vringh: Use wiov->used to check for read/write desc order qed: qed ll2 race condition fixes qed: Fix null-pointer dereference in qed_rdma_create_qp() drm: Copy drm_wait_vblank to user before returning drm/nouveau/disp: power down unused DP links during init net/rds: dma_map_sg is entitled to merge entries btrfs: fix race between marking inode needs to be logged and log syncing vt_kdsetmode: extend console locking bpf: Track contents of read-only maps as scalars bpf: Fix cast to pointer from integer of different size warning net: dsa: mt7530: fix VLAN traffic leaks again KVM: x86/mmu: Treat NX as used (not reserved) for all !TDP shadow MMUs arm64: dts: qcom: msm8994-angler: Fix gpio-reserved-ranges 85-88 btrfs: fix NULL pointer dereference when deleting device by invalid id Revert "floppy: reintroduce O_NDELAY fix" Revert "parisc: Add assembly implementations for memset, strlen, strcpy, strncpy and strcat" net: don't unconditionally copy_from_user a struct ifreq for socket ioctls audit: move put_tree() to avoid trim_trees refcount underflow and UAF Linux 5.4.144 UBUNTU: upstream stable to v5.4.144 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945517] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1945517 Title: Focal update: v5.4.145 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.145 upstream stable release from git://git.kernel.org/ fscrypt: add fscrypt_symlink_getattr() for computing st_size ext4: report correct st_size for encrypted symlinks f2fs: report correct st_size for encrypted symlinks ubifs: report correct st_size for encrypted symlinks kthread: Fix PF_KTHREAD vs to_kthread() race xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats reset: reset-zynqmp: Fixed the argument data type qed: Fix the VF msix vectors flow net: macb: Add a NULL check on desc_ptp qede: Fix memset corruption perf/x86/intel/pt: Fix mask of num_address_ranges perf/x86/amd/ibs: Work around erratum #1197 perf/x86/amd/power: Assign pmu.module cryptoloop: add a deprecation warning ARM: 8918/2: only build return_address() if needed ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 ALSA: pcm: fix divide error in snd_pcm_lib_ioctl ARC: wireup clone3 syscall media: stkwebcam: fix memory leak in stk_camera_probe igmp: Add ip_mc_list lock in ip_check_mc_rcu USB: serial: mos7720: improve OOM-handling in read_mos_reg() ipv4/icmp: l3mdev: Perform icmp error route lookup on source device routing table (v2) powerpc/boot: Delete unneeded .globl _zimage_start net: ll_temac: Remove left-over debug message mm/page_alloc: speed up the iteration of max_order Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" x86/events/amd/iommu: Fix invalid Perf result due to IOMMU PMC power-gating Revert "btrfs: compression: don't try to compress if we don't have enough pages" ALSA: usb-audio: Add registration quirk for JBL Quantum 800 usb: host: xhci-rcar: Don't reload firmware after the completion usb: mtu3: use @mult for HS isoc or intr usb: mtu3: fix the wrong HS mult value xhci: fix unsafe memory usage in xhci tracing x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions PCI: Call Max Payload Size-related fixup quirks early Linux 5.4.145 UBUNTU: upstream stable to v5.4.145 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946024] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1946024 Title: Focal update: v5.4.146 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.146 upstream stable release from git://git.kernel.org/ locking/mutex: Fix HANDOFF condition regmap: fix the offset of register error log crypto: mxs-dcp - Check for DMA mapping errors sched/deadline: Fix reset_on_fork reporting of DL tasks power: supply: axp288_fuel_gauge: Report register-address on readb / writeb errors crypto: omap-sham - clear dma flags only after omap_sham_update_dma_stop() sched/deadline: Fix missing clock update in migrate_task_rq_dl() rcu/tree: Handle VM stoppage in stall detection hrtimer: Avoid double reprogramming in __hrtimer_start_range_ns() hrtimer: Ensure timerfd notification for HIGHRES=n udf: Check LVID earlier udf: Fix iocharset=utf8 mount option isofs: joliet: Fix iocharset=utf8 mount option bcache: add proper error unwinding in bcache_device_init nvme-tcp: don't update queue count when failing to set io queues nvme-rdma: don't update queue count when failing to set io queues nvmet: pass back cntlid on successful completion power: supply: max17042_battery: fix typo in MAx17042_TOFF s390/cio: add dev_busid sysfs entry for each subchannel libata: fix ata_host_start() crypto: qat - do not ignore errors from enable_vf2pf_comms() crypto: qat - handle both source of interrupt in VF ISR crypto: qat - fix reuse of completion variable crypto: qat - fix naming for init/shutdown VF to PF notifications crypto: qat - do not export adf_iov_putmsg() fcntl: fix potential deadlock for _struct.fa_lock udf_get_extendedattr() had no boundary checks. s390/kasan: fix large PMD pages address alignment check s390/debug: fix debug area life cycle m68k: emu: Fix invalid free in nfeth_cleanup() sched: Fix UCLAMP_FLAG_IDLE setting spi: spi-fsl-dspi: Fix issue with uninitialized dma_slave_config spi: spi-pic32: Fix issue with uninitialized dma_slave_config genirq/timings: Fix error return code in irq_timings_test_irqs() lib/mpi: use kcalloc in mpi_resize clocksource/drivers/sh_cmt: Fix wrong setting if don't request IRQ for clock source channel crypto: qat - use proper type for vf_mask certs: Trigger creation of RSA module signing key if it's not an RSA key regulator: vctrl: Use locked regulator_get_voltage in probe path regulator: vctrl: Avoid lockdep warning in enable/disable ops spi: sprd: Fix the wrong WDG_LOAD_VAL spi: spi-zynq-qspi: use wait_for_completion_timeout to make zynq_qspi_exec_mem_op not interruptible EDAC/i10nm: Fix NVDIMM detection drm/panfrost: Fix missing clk_disable_unprepare() on error in panfrost_clk_init() media: TDA1997x: enable EDID support soc: rockchip: ROCKCHIP_GRF should not default to y, unconditionally media: cxd2880-spi: Fix an error handling path bpf: Fix a typo of reuseport map in bpf.h. bpf: Fix potential memleak and UAF in the verifier. ARM: dts: aspeed-g6: Fix HVI3C function-group in pinctrl dtsi arm64: dts: renesas: r8a77995: draak: Remove bogus adv7511w properties soc: qcom: rpmhpd: Use corner in power_off media: dvb-usb: fix uninit-value in dvb_usb_adapter_dvb_init media: dvb-usb: fix uninit-value in vp702x_read_mac_addr media: dvb-usb: Fix error handling in dvb_usb_i2c_init media: go7007: remove redundant initialization media: coda: fix frame_mem_ctrl for YUV420 and YVU420 formats Bluetooth: sco: prevent information leak in sco_conn_defer_accept() 6lowpan: iphc: Fix an off-by-one check of array index netns: protect netns ID lookups with RCU drm/amdgpu/acp: Make PM domain really work tcp: seq_file: Avoid skipping sk during tcp_seek_last_pos ARM: dts: meson8: Use a higher default GPU clock frequency ARM: dts: meson8b: odroidc1: Fix the pwm regulator supply properties ARM: dts: meson8b: mxq: Fix the pwm regulator supply properties ARM: dts: meson8b: ec100:
[Kernel-packages] [Bug 1946795] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1946795 Title: Focal update: v5.4.147 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.147 upstream stable release from git://git.kernel.org/ Note: v5.4.147 contained only reverts for commits omitted from our application of prior sets, so v5.4.147 suppplies new commits for Focal Linux 5.4.147 UBUNTU: upstream stable to v5.4.147 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1946795/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946802] [linux-iot/focal] verification still needed
The fix for this bug has been awaiting testing feedback in the -proposed repository for focal for more than 90 days. Please test this fix and update the bug appropriately with the results. In the event that the fix for this bug is still not verified 15 days from now, the package will be removed from the -proposed repository. ** Tags added: removal-candidate -- 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/1946802 Title: Focal update: v5.4.148 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.148 upstream stable release from git://git.kernel.org/ rtc: tps65910: Correct driver module alias btrfs: wake up async_delalloc_pages waiters after submit btrfs: reset replace target device to allocation state on close blk-zoned: allow zone management send operations without CAP_SYS_ADMIN blk-zoned: allow BLKREPORTZONE without CAP_SYS_ADMIN PCI/MSI: Skip masking MSI-X on Xen PV powerpc/perf/hv-gpci: Fix counter value parsing xen: fix setting of max_pfn in shared_info include/linux/list.h: add a macro to test if entry is pointing to the head 9p/xen: Fix end of loop tests for list_for_each_entry tools/thermal/tmon: Add cross compiling support pinctrl: stmfx: Fix hazardous u8[] to unsigned long cast pinctrl: ingenic: Fix incorrect pull up/down info soc: qcom: aoss: Fix the out of bound usage of cooling_devs soc: aspeed: lpc-ctrl: Fix boundary check for mmap soc: aspeed: p2a-ctrl: Fix boundary check for mmap arm64: head: avoid over-mapping in map_memory crypto: public_key: fix overflow during implicit conversion block: bfq: fix bfq_set_next_ioprio_data() power: supply: max17042: handle fails of reading status register dm crypt: Avoid percpu_counter spinlock contention in crypt_page_alloc() VMCI: fix NULL pointer dereference when unmapping queue pair media: uvc: don't do DMA on stack media: rc-loopback: return number of emitters rather than error Revert "dmaengine: imx-sdma: refine to load context only once" dmaengine: imx-sdma: remove duplicated sdma_load_context libata: add ATA_HORKAGE_NO_NCQ_TRIM for Samsung 860 and 870 SSDs ARM: 9105/1: atags_to_fdt: don't warn about stack size PCI/portdrv: Enable Bandwidth Notification only if port supports it PCI: Restrict ASMedia ASM1062 SATA Max Payload Size Supported PCI: Return ~0 data on pciconfig_read() CAP_SYS_ADMIN failure PCI: xilinx-nwl: Enable the clock through CCF PCI: aardvark: Fix checking for PIO status PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response PCI: aardvark: Fix masking and unmasking legacy INTx interrupts HID: input: do not report stylus battery state as "full" f2fs: quota: fix potential deadlock scsi: bsg: Remove support for SCSI_IOCTL_SEND_COMMAND IB/hfi1: Adjust pkey entry in index 0 RDMA/iwcm: Release resources if iw_cm module initialization fails docs: Fix infiniband uverbs minor number pinctrl: samsung: Fix pinctrl bank pin count vfio: Use config not menuconfig for VFIO_NOIOMMU powerpc/stacktrace: Include linux/delay.h RDMA/efa: Remove double QP type assignment f2fs: show f2fs instance in printk_ratelimited f2fs: reduce the scope of setting fsck tag when de->name_len is zero openrisc: don't printk() unconditionally dma-debug: fix debugfs initialization order SUNRPC: Fix potential memory corruption scsi: fdomain: Fix error return code in fdomain_probe() pinctrl: single: Fix error return code in pcs_parse_bits_in_pinctrl_entry() scsi: smartpqi: Fix an error code in pqi_get_raid_map() scsi: qedi: Fix error codes in qedi_alloc_global_queues() scsi: qedf: Fix error codes in qedf_alloc_global_queues() powerpc/config: Renable MTD_PHYSMAP_OF scsi: target: avoid per-loop XCOPY buffer allocations HID: i2c-hid: Fix Elan touchpad regression KVM: PPC: Book3S HV Nested: Reflect guest PMU in-use to L0 when guest SPRs are live platform/x86: dell-smbios-wmi: Add missing kfree in error-exit from run_smbios_call fscache: Fix cookie key hashing clk: at91: sam9x60: Don't use audio PLL clk: at91: clk-generated: pass the id of changeable parent at registration clk: at91: clk-generated: Limit the requested rate to our range KVM: PPC: Fix clearing never mapped TCEs in realmode f2fs: fix to account missing .skipped_gc_rwsem f2fs: fix
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
@sebastian-berner or @kai-szymanski - please confirm that this fixes your cifs issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ip> snd_seq_midi coretemp snd_seq_midi_event snd_rawmidi kvm_intel snd_seq kvm dell_wmi snd_seq_device rapl dell_smbios snd_timer dcdbas intel_cstate input_leds iwlwifi serio_raw snd intel_wmi_thunderbolt rtsx_pci_ms dell_wmi_descriptor wmi_bmof processor_thermal_device ucsi_acp> pinctrl_cannonlake video pinctrl_intel ---[ end trace 80828f22da45a19b ]--- RIP: 0010:__slab_free+0x199/0x360 Code: 00 48 89 c7 fa 66 0f 1f 44 00 00 f0 49 0f ba 2c 24 00 72 79 4d 3b 6c 24 20 74 11 49 0f ba 34 24 00 57 9d 0f 1f
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
This bug is awaiting verification that the linux-azure/5.4.0-1069.72 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 in Ubuntu. https://bugs.launchpad.net/bugs/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter
[Kernel-packages] [Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression
Same thing, hardware is an Intel NUC NUC10i5FNK. OS: Ubuntu Server 20.04.3 LTS. Kiosk machine, when I select 5.13.0-28 to boot, it just freezes at loading ramdisk. 5.11.0-46-generic works just fine. -- 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/1960018 Title: Boot Failure - linux-image-5.13.0-28-generic | regression Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 Installed since May 2020, now fails to boot into graphics mode after upgrade to kernel version linux-image-5.13.0-27-generic - Have tried linux-image-5.13.0-28-generic with same result, I have reverted back to 5.11.0.40 which works correctly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1890 F pulseaudio /dev/snd/controlC0: christian 1890 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (639 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta/5.13.0.30.40)
All autopkgtests for the newly accepted linux-meta (5.13.0.30.40) for impish have finished running. The following regressions have been reported in tests triggered by the package: initramfs-tools/0.140ubuntu6 (amd64) casper/1.465 (amd64) systemd/248.3-1ubuntu8.2 (armhf) libvirt/unknown (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/impish/update_excuses.html#linux-meta [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix 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: Won't Fix 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: Won't Fix 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 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
** Changed in: hwe-next Status: In Progress => Fix Released -- 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956886] Re: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new': Opera
** Information type changed from Private Security to Public -- 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/1956886 Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new': Operation not permitted Status in linux package in Ubuntu: New Bug description: have no any extra ProblemType: Package DistroRelease: Ubuntu 21.10 Package: linux-modules-5.13.0-23-generic (not installed) ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: denis 4688 F pulseaudio CasperMD5CheckResult: unknown Date: Sun Jan 9 16:33:21 2022 DuplicateSignature: package:linux-modules-5.13.0-23-generic:(not installed) Unpacking linux-modules-5.13.0-23-generic (5.13.0-23.23) ... dpkg: error processing archive /tmp/apt-dpkg-install-Rco5X1/10-linux-modules-5.13.0-23-generic_5.13.0-23.23_amd64.deb (--unpack): unable to open '/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-10 (578 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Vostro 15-3565 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-22-generic root=UUID=55598d49-73b7-48f5-bc87-11579b8af75b ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-modules-5.13.0-23-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.13.0-23-generic/kernel/zfs/zfs.ko.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.release: 0.204 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.8 dmi.board.name: Vostro 15-3565 dmi.board.vendor: Dell Inc. dmi.board.version: 1.0.8 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr1.0.8:bd06/19/2017:br0.204:svnDellInc.:pnVostro15-3565:pvrNotSpecified:rvnDellInc.:rnVostro15-3565:rvr1.0.8:cvnDellInc.:ct8:cvrNotSpecified:sku0732: dmi.product.name: Vostro 15-3565 dmi.product.sku: 0732 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960256] [NEW] compilation due to "peermem" module
Public bug reported:
Installed with the following:
apt-get install --no-install-recommends nvidia-driver-470 nvidia-
modprobe libnvidia-cfg1-470 libnvidia-common-470 libnvidia-compute-470
libnvidia-decode-470 libnvidia-encode-470 libnvidia-extra-470 libnvidia-
fbc1-470 libnvidia-gl-470 libnvidia-ifr1-470 nvidia-compute-utils-470
nvidia-dkms-470 nvidia-driver-470 nvidia-kernel-common-470 nvidia-
kernel-source-470 nvidia-utils-470 xserver-xorg-video-nvidia-470
Seems to generate /var/crash/nvidia-dkms-470.0.crash (tail -20):
/usr/bin/ld.bfd -m elf_x86_64 -z max-page-size=0x20-r -o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-drv.o […] { echo
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o […]
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-format.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.mod
make -f ./scripts/Makefile.modpost
sed 's/ko$/o/' /var/lib/dkms/nvidia/470.103.01/build/modules.order |
scripts/mod/modpost -m -a -i ./Module.symvers -I
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -e
/usr/src/ofa_kernel/default/Module.symvers -o
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -s -T -
FATAL: parse error in symbol dump file
scripts/Makefile.modpost:93: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1675: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-97-generic'
Makefile:80: recipe for target 'modules' failed
make: *** [modules] Error 2
DKMSKernelVersion: 5.4.0-97-generic
Date: Mon Feb 7 11:32:36 2022
Package: nvidia-dkms-470 470.103.01-0ubuntu0.18.04.1
PackageVersion: 470.103.01-0ubuntu0.18.04.1
SourcePackage: nvidia-graphics-drivers-470
Title: nvidia-dkms-470 470.103.01-0ubuntu0.18.04.1: nvidia kernel module failed
to build
It is added:
# dkms status -k `uname -r`
iser, 4.7: added
kernel-mft-dkms, 4.13.0, 5.4.0-97-generic, x86_64: installed
knem, 1.1.3.90mlnx1: added
mlnx-ofed-kernel, 4.7: added
nvidia, 470.103.01: added
rshim, 1.8, 5.4.0-97-generic, x86_64: installed
srp, 4.7: added
However, doing a build gets:
dkms build nvidia/470.103.01
Kernel preparation unnecessary for this kernel. Skipping...
applying patch disable_fstack-clash-protection_fcf-protection.patch...patching
file Kbuild
Hunk #1 succeeded at 82 (offset 11 lines).
Building module:
cleaning build area...
unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1
'make' -j16 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=5.4.0-97-generic
IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1
SYSSRC=/lib/modules/5.4.0-97-generic/build LD=/usr/bin/ld.bfd
modules.(bad exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists:
'/var/crash/nvidia-dkms-470.0.crash'
Error! Bad return status for module build on kernel: 5.4.0-97-generic (x86_64)
Consult /var/lib/dkms/nvidia/470.103.01/build/make.log for more information.
Which I suspect is related to the "peermem" module:
{ echo /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-drv.o [...]
/var/lib/dkms/nvidia/470.103.01/build/nvidia-drm/nvidia-drm-format.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-drm.mod
/usr/bin/ld.bfd -m elf_x86_64 -z max-page-size=0x20-r -o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem.o
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem/nvidia-peermem.o
{ echo
/var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem/nvidia-peermem.o; echo; }
> /var/lib/dkms/nvidia/470.103.01/build/nvidia-peermem.mod
make -f ./scripts/Makefile.modpost
sed 's/ko$/o/' /var/lib/dkms/nvidia/470.103.01/build/modules.order |
scripts/mod/modpost -m -a -i ./Module.symvers -I
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -e
/usr/src/ofa_kernel/default/Module.symvers -o
/var/lib/dkms/nvidia/470.103.01/build/Module.symvers -s -T -
FATAL: parse error in symbol dump file
scripts/Makefile.modpost:93: recipe for target '__modpost' failed
make[2]: *** [__modpost] Error 1
Makefile:1675: recipe for target 'modules' failed
make[1]: *** [modules] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-97-generic'
Makefile:80: recipe for target 'modules' failed
make: *** [modules] Error 2
(END)
This does not seem to be supported on (unpatched?) 5.4 kernels per this
thread I found:
https://forums.linuxmint.com/viewtopic.php?p=2106512#p2106512
Downloading and running "NVIDIA-Linux-x86_64-470.103.01.run" directly
also fails, UNLESS the following options is used:
--no-peermem
Do not install the nvidia-peermem kernel module. This kernel module
provides support for peer-to-peer memory sharing with Mellanox HCAs (Host
Channel Adapters) via GPUDirect RDMA (Remote Direct Memory Access).
BUT
[Kernel-packages] [Bug 1959752] Re: ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux 4.15.0-168.176 on s390x
All ubuntu_kernel_selftests.ftrace:ftracetest tests completed
successfully with bionic:linux 4.15.0-169.177:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220207_154815_bf623@/log.gz
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1959752
Title:
ubuntu_kernel_selftests.ftrace:ftracetest fails with bionic:linux
4.15.0-168.176 on s390x
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Bionic:
Fix Committed
Bug description:
SRU Justification
[Impact]
There seems to have been a typo in Commit 85bf17b28f97
("recordmcount.pl: look for jgnop instruction as well as bcrl on s390")
that causes errors in finding mcount locations. This seems to cause problems
with ftrace initialization leading to not being able to use ftrace
functions.
[Fix]
Fix the typo by changing it to the correct instruction.
[Test Case]
Ftrace files in /sys/kernel/debug/tracing should be able to be read
from and written to with normal functionality. Ftrace selftests should
now pass.
[Where things could go wrong]
Its a simple typo fix so none really.
---
All ftrace tests from selftests are failing with bionic:linux 4.15.0-168.176
on s390x:
https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/s390x/l/linux/20220201_190955_5689e@/log.gz
==
selftests: ftracetest
=== Ftrace unit tests ===
[1] Basic trace file check[FAIL]
[2] Basic test for tracers[FAIL]
[3] Basic trace clock test[FAIL]
[4] Basic event tracing check [FAIL]
[5] Snapshot and tracing setting [FAIL]
[6] event tracing - enable/disable with event level files [FAIL]
[7] event tracing - restricts events based on pid [FAIL]
[8] event tracing - enable/disable with subsystem level files [FAIL]
[9] event tracing - enable/disable with top level files [FAIL]
[10] ftrace - function graph filters with stack tracer[FAIL]
[11] ftrace - function graph filters [FAIL]
[12] ftrace - function pid filters[FAIL]
[13] ftrace - test for function event triggers[FAIL]
[14] ftrace - function profiler with function tracing [FAIL]
[15] ftrace - test reading of set_ftrace_filter [FAIL]
[16] ftrace - test for function traceon/off triggers [FAIL]
[17] Test creation and deletion of trace instances while setting an event
[FAIL]
[18] Test creation and deletion of trace instances[FAIL]
[19] Kprobe dynamic event - adding and removing [FAIL]
[20] Kprobe dynamic event - busy event check [FAIL]
[21] Kprobe dynamic event with arguments [FAIL]
[22] Kprobe event string type argument[FAIL]
[23] Kprobe event argument syntax [FAIL]
[24] Kprobes event arguments with types [FAIL]
[25] Kprobe event auto/manual naming [FAIL]
[26] Kprobe dynamic event with function tracer[FAIL]
[27] Kretprobe dynamic event with arguments [FAIL]
[28] Kretprobe dynamic event with maxactive [FAIL]
[29] Register/unregister many kprobe events [FAIL]
[30] event trigger - test multiple actions on hist trigger[FAIL]
[31] event trigger - test synthetic_events syntax parser [FAIL]
[32] event trigger - test event enable/disable trigger[FAIL]
[33] event trigger - test trigger filter [FAIL]
[34] event trigger - test histogram modifiers [FAIL]
[35] event trigger - test multiple histogram triggers [FAIL]
[36] event trigger - test snapshot-trigger[FAIL]
[37] event trigger - test stacktrace-trigger [FAIL]
[38] event trigger - test traceon/off trigger [FAIL]
[39] (instance) Basic test for tracers [FAIL]
[40] (instance) Basic trace clock test [FAIL]
[41] (instance) Snapshot and tracing setting [FAIL]
[42] (instance) event tracing - enable/disable with event level files
[FAIL]
[43] (instance) event tracing - restricts events based on pid[FAIL]
[44] (instance) event tracing - enable/disable with subsystem level files
[FAIL]
[45] (instance) ftrace - test for function event triggers[FAIL]
[46] (instance) ftrace - test for function traceon/off triggers [FAIL]
[47] (instance) event trigger - test event enable/disable trigger[FAIL]
[48] (instance) event trigger - test trigger filter [FAIL]
[49] (instance) event trigger - test histogram modifiers [FAIL]
[50] (instance) event trigger - test multiple histogram triggers [FAIL]
# of passed: 0
# of failed: 50
# of unresolved: 0
# of untested: 0
# of unsupported: 0
# of xfailed: 0
# of
[Kernel-packages] [Bug 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
** Package changed: linux-signed (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960213 Title: Kernel Panic on linux-image-5.15.0-18-generic Status in linux package in Ubuntu: New Bug description: Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012 On 5.13.0-29-generic boot successfully. Laptop: Lenovo Model: 20RA002SRT Stack trace in attached images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on linux-ibm-5.4/5.4.0-1014 does not apply here. However, I'm updating the tags to verification-done-bionic, just to unblock the process. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle) environments and its communication. * Errors like "usercopy: Kernel memory overwrite attempt detected to SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause failures. * This is because IUCV uses kmalloc() with __GFP_DMA because of memory address restrictions. * The solution is to mark dma-kmalloc caches as usercopy caches. [Fix] * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy: mark dma-kmalloc caches as usercopy caches" * Due to changes in the context of the upstream patch, a cherry-pick was not possible and the following backport was created: https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch [Test Case] * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka virtual machine. * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html * Set up a Linux IUCV instance: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html * Set up an IUCV direct: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html * Make use of IUCV, for example using ssh on a direct connection. * Verify if the connections is stable and watch out for messages starting with "usercopy". [Regression Potential] * Problems could occur in case the create_kmalloc_cache call is done wrong, for example with wrong index, wrong size or just wrong comma separations. * Wrong size or index will probably lead to similar instability problems that exist today. * Problems in the syntax (commas etc.) will be detected at compile time. * But it's just a single line modification in function create_kmalloc_caches of /mm/slab_common.c, * so the change is very limited and quite traceable. * And it was in depth discussed here: https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/ * a reviewed by a lot of kernel engineers (see provenance) * and it was already upstream accepted with kernel 5.8. [Other] * Since the commit is upstream accepted with 5.8, so it's already in impish and hirsute (and groovy). * Hence this kernel SRU submission is for Focal only and covers only the above single but common code commit/patch. __ When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)! Dec 14 22:02:26 ub2004img kernel: [63084.184680] WARNING: CPU: 1 PID: 697 at mm/usercopy.c:75 usercopy_warn+0xa0/0xd0 Dec 14 22:02:26 ub2004img kernel: [63084.184681] Modules linked in: tcp_diag udp_diag raw_diag inet_diag unix_diag xt_CT iptable_raw ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack nf_conntrack nf_defr ag_ipv6 nf_defrag_ipv4 iptable_filter bpfilter af_iucv nls_utf8 isofs dm_multipath scsi_dh_rdac scsi_dh_emc
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
* The s390x diagnose 318 instruction sets the control program name
code (CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.
* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
[Fix]
* In general the following 4 commits are needed:
* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
* For jammy, hirsute and impish only the first commit is needed, the
others are already in.
* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.
[Test Case]
* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
* And setup an Ubuntu KVM virtual machine on top.
* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.
* The CPNC will always be 4 (denotes Linux environment).
* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.
[Where problems could occur]
* The approach here is to provide additional debug and diagnose
information on top.
* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.
* The changes themselves are relatively discernible and mostly
introduce new structures.
* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the
verification later is targeted at.
* Since diag318 is s390x specific, all the modifications touch s390x
code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
diag.h). At least no other other architecture will be affected.
* Well, there is one tiny bit of a common code change, but it's just a
new define statement in include/uapi/linux/kvm.h ('#define
KVM_CAP_S390_DIAG318 186').
[Other]
* Request was to add the patches to focal / 20.04, but to avoid
potential regressions on upgrades, the patches need to be added to
jammy, impish and hirsute, too.
* As mentioned above, Jammy, Hirsute and Impish includes almost
everything needed, except 3fd8417f2c72 "KVM: s390: add debug statement
for diag 318 CPNC data".
* Hence the SRU is for Focal, Jammy, Hirsute and Impish, but less
invasive for Jammy, Hirsute and Impish, also because commit
3fd8417f2c72 can be cleanly cherry-picked form there.
* LP#1953338 is related to this bug and
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
This bug was for 20.04 GA kernel plain Ubuntu - hence verification on
linux-ibm-5.4/5.4.0-1014 does not apply here.
However, I'm updating the tags to verification-done-bionic, just to unblock the
process.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions on upgrades).
__
Toleration support for new IBM Z crypto hardware - Backport to focal
(20.04)
Patch from kernel 5.14:
Summary: s390/AP: support new dynamic AP bus size limit
Description: This patch provides support for new dynamic AP bus
message limit with the existing zcrypt device driver
and AP bus core code. There is support for a new
field 'ml' from the TAPQ query which indicates the
per card AP bus message size limit. This TAPQ
improvement will come with an updated firmware and
this patch exploits this new field and thus makes
it possible to send/receive AP messages greater
[Kernel-packages] [Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896420 Title: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: [Impact] Test fails to build in selftests/seccomp/seccomp_bpf.c with 'error: storage size of ‘md’ isn’t known' due to the type struct seccomp_metadata not being defined for B/5.4 kernels. [Test case] Test successfully builds and test cases pass both on Bionic/5.4 and on Focal [Fixes] Unconditionally define struct seccomp_metadata. Remove linux/ptrace.h where a definition of seccomp_metadata is already being defined in Focal. [Potential regression] There could be future build failures if glibc headers get updated to include definitions of struct seccomp_metadata or if linux/ptrace.h gets updated to include needed definitions. --- Issue found on 5.4.0-48.52~18.04.1 Test build failed with: gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘get_metadata’: seccomp_bpf.c:3028:26: error: storage size of ‘md’ isn’t known struct seccomp_metadata md; ^~ seccomp_bpf.c:3028:26: warning: unused variable ‘md’ [-Wunused-variable] Makefile:12: recipe for target 'seccomp_bpf' failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1896420/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.
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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* Hardware diagnose data (diag 318) of KVM guest kernel cannot be
handled.
* A fix is needed to enhance problem determination of guest kernel
under KVM using DIAG 0x318 instruction execution.
* The s390x diagnose 318 instruction sets the control program name
code (CPNC) and control program version code (CPVC) to provide useful
information regarding the OS during debugging.
* The CPNC is explicitly set to 4 to indicate a Linux/KVM environment.
[Fix]
* In general the following 4 commits are needed:
* 3fd8417f2c728d810a3b26d7e2008012ffb7fd01 3fd8417f2c72 "KVM: s390: add debug
statement for diag 318 CPNC data"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545726/+files/0004-KVM-s390-add-debug-statement-for-diag-318-CPNC-data.patch
* 6cbf1e960fa52e4c63a6dfa4cda8736375b34ccc 6cbf1e960fa5 "KVM: s390: remove
diag318 reset code"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545725/+files/0003-KVM-s390-remove-diag318-reset-code.patch
* 23a60f834406c8e3805328b630d09d5546b460c1 23a60f834406 "s390/kvm: diagnose
0x318 sync and reset"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545724/+files/0002-s390-kvm-diagnose-0x318-sync-and-reset.patch
* a23816f3cdcbffe5dc6e8c331914b3f51b87c2f3 a23816f3cdcb "s390/setup: diag
318: refactor struct"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953334/+attachment/5545723/+files/0001-s390-setup-diag-318-refactor-struct.patch
* For jammy, hirsute and impish only the first commit is needed, the
others are already in.
* For focal all 4 commits are needed, but since they do not apply
cleanly on focal, the attached backports need to be used instead.
[Test Case]
* Setup an IBM Z or LinuxONE LPAR with Ubuntu Server as KVM host.
* And setup an Ubuntu KVM virtual machine on top.
* It can then be observed if the CPNC (diag318 data) has been
successfully set by looking at the s390dbf messages for the KVM guest.
* The CPNC will always be 4 (denotes Linux environment).
* Another way to test this is by running the sync_regs_test under
tools/testing/selftests/kvm/s390x/sync_regs_test. Just running the
kernel self test suite can trigger this.
[Where problems could occur]
* The approach here is to provide additional debug and diagnose
information on top.
* Hence even if the diag318 changes are broken, the existing
functionality shouldn't be harmed.
* The changes themselves are relatively discernible and mostly
introduce new structures.
* However, with the functional changes broken code could be introduced
(e.g. due to erroneous pointer arithmetic for example) that does not
compile or causes crashes. But this is what the test builds are for
(https://launchpad.net/~fheimes/+archive/ubuntu/lp1953334).
* On top the diag318 diagnose data might not properly provided - maybe
empty or wrong. Again that is what the test builds and the
verification later is targeted at.
* Since diag318 is s390x specific, all the modifications touch s390x
code only. (in arch/s390/kvm/ kvm-s390.c and vsie.c,
arch/s390/kernel/setup.c, arch/s390/include/asm/ kvm_host.h, kvm.h and
diag.h). At least no other other architecture will be affected.
* Well, there is one tiny bit of a common code change, but it's just a
new define statement in include/uapi/linux/kvm.h ('#define
KVM_CAP_S390_DIAG318 186').
[Other]
* Request was to add the patches to focal / 20.04, but to avoid
potential regressions on upgrades, the patches need to be added to
jammy, impish and hirsute, too.
* As
[Kernel-packages] [Bug 1938964] Re: icmp_redirect from selftests fails on F/kvm (unary operator expected)
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1938964 Title: icmp_redirect from selftests fails on F/kvm (unary operator expected) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Bug description: [Impact] If any sub-test in this icmp_redirect.sh is failing but not expected to fail. The script will complain: ./icmp_redirect.sh: line 72: [: 1: unary operator expected This is because when the sub-test is not expected to fail, we won't pass any value for the xfail local variable in log_test() and thus it's empty. Fix this by passing 0 as the 4th variable to log_test() for non-xfail cases. This issue can be found on our KVM kernel with SRU tests, they're failing because of missing some kernel configs. [Fix] * 39d8622c72 "selftests: icmp_redirect: pass xfail=0 to log_test()" This patch can be cherry-picked into all of the affected kernels. [Test Plan] Run the patched icmp_redirect.sh script with a KVM kernel (e.g. F/kvm), and this "unary operator expected" error message should no longer exist. [Where problems could occur] Change limited to test script, it won't have any impact to real kernel function. And this issue is most likely specific to KVM kernels. == Original Bug Report == icmp_redirect from selftect is failing on F/kvm 5.4.0-1045.47 # selftests: net: icmp_redirect.sh # # ### # Legacy routing # ### # # TEST: IPv4: redirect exception [ OK ] # TEST: IPv6: redirect exception [ OK ] # TEST: IPv4: redirect exception plus mtu [ OK ] # TEST: IPv6: redirect exception plus mtu [ OK ] # TEST: IPv4: routing reset [ OK ] # TEST: IPv6: routing reset [ OK ] # TEST: IPv4: mtu exception [ OK ] # TEST: IPv6: mtu exception [ OK ] # TEST: IPv4: mtu exception plus redirect [ OK ] # TEST: IPv6: mtu exception plus redirect [XFAIL] # # ### # Legacy routing with VRF # ### # # Error: Unknown device type. # Cannot find device "red" # Error: argument "red" is wrong: Invalid VRF # # Error: argument "red" is wrong: Invalid VRF # # Cannot find device "red" # Cannot find device "red" # Error: argument "red" is wrong: Not a valid VRF name # # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator expected # TEST: IPv4: redirect exception plus mtu [FAIL] # Error: argument "red" is wrong: Invalid VRF # # TEST: IPv6: redirect exception plus mtu [XFAIL] # Error: argument "red" is wrong: Invalid VRF # # ./icmp_redirect.sh: line 71: [: 1: unary operator
[Kernel-packages] [Bug 1947206] Re: Updates to ib_peer_memory requested by Nvidia
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] Nvidia notified me via private email that they'd discovered some issues with the ib_peer_memory patch we are carrying in hirsute/impish and sent me a patch intended to resolve them. My knowledge of these changes is limited to what is mentioned in the commit message: - Allow clients to opt out of unmap during invalidation - Fix some bugs in the sequencing of mlx5 MRs - Enable ATS for peer memory [Test Case] ib_write_bw from the perftest package, rebuilt with CUDA support, can be used as a smoke test of this feature. I'll attach a sample test script here. I've verified this test passes with the kernels in the archive, and continues to pass with the provided patch applied. [Fix] Nvidia has emailed me fixes for both trees. They are not currently available in a public tree elsewhere, though I'm told at some point they should end up in a branch here: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/ [What could go wrong] The only known use case for ib_peer_memory are Nvidia GPU users making use of the GPU PeerDirect feature where GPUs can share memory with one another over an Infiniband network. Bugs here could cause problems (hangs, crashes, corruption) with such workloads. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1913442] Re: [Ubuntu 20.04] Problem leading IUCV service down (on s390x)
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1913442 Title: [Ubuntu 20.04] Problem leading IUCV service down (on s390x) Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: SRU Justification: == [Impact] * Problems occur in IBM z/VM's IUCV (Inter User Communication Vehicle) environments and its communication. * Errors like "usercopy: Kernel memory overwrite attempt detected to SLUB object 'dma-kmalloc-1 k' (offset 0, size 11)!" pop up and cause failures. * This is because IUCV uses kmalloc() with __GFP_DMA because of memory address restrictions. * The solution is to mark dma-kmalloc caches as usercopy caches. [Fix] * 49f2d2419d60a103752e5fbaf158cf8d07c0d884 49f2d2419d60 "usercopy: mark dma-kmalloc caches as usercopy caches" * Due to changes in the context of the upstream patch, a cherry-pick was not possible and the following backport was created: https://bugs.launchpad.net/bugs/1913442/+attachment/5457885/+files/commit_49f2d2419d60_backport.patch [Test Case] * Setup Ubuntu Server 20.04 on s390x system as IBM z/VM guest aka virtual machine. * Setup IUCV on z/VM: Setting up the (IUCV TCPIP) service machine: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_tcpservice.html * Set up a Linux IUCV instance: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_t_iucv_scen1_guest.html * Set up an IUCV direct: https://www.ibm.com/support/knowledgecenter/linuxonibm/com.ibm.linux.z.ljdd/ljdd_c_iucv_connect.html * Make use of IUCV, for example using ssh on a direct connection. * Verify if the connections is stable and watch out for messages starting with "usercopy". [Regression Potential] * Problems could occur in case the create_kmalloc_cache call is done wrong, for example with wrong index, wrong size or just wrong comma separations. * Wrong size or index will probably lead to similar instability problems that exist today. * Problems in the syntax (commas etc.) will be detected at compile time. * But it's just a single line modification in function create_kmalloc_caches of /mm/slab_common.c, * so the change is very limited and quite traceable. * And it was in depth discussed here: https://lore.kernel.org/kernel-hardening/1515636190-24061-2-git-send-email-keesc...@chromium.org/ * a reviewed by a lot of kernel engineers (see provenance) * and it was already upstream accepted with kernel 5.8. [Other] * Since the commit is upstream accepted with 5.8, so it's already in impish and hirsute (and groovy). * Hence this kernel SRU submission is for Focal only and covers only the above single but common code commit/patch. __ When I deployed a Ubuntu20.04 instance with kernel version of 5.4.0-58-generic under z/VM, I saw below messages from kernel and the iucvserv program malfunctioned. Hence it caused some devices like network device configuration failure and deployment failure. Dec 14 22:02:26 ub2004img iucvserv: Receive OPNCLD4 0.0.0.1 pwd sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: /etc/iucv_authorized_userid exists, check authorization. Dec 14 22:02:26 ub2004img iucvserv: senduserid=OPNCLD4, authuserid=OPNCLD4, len=7 Dec 14 22:02:26 ub2004img iucvserv: Current version is 0.0.0.1, upgraded version is 0.0.0.1 Dec 14 22:02:26 ub2004img iucvserv: Will execute the linux command pwd 2>&1; echo iucvcmdrc=$? sent from IUCV client. Dec 14 22:02:26 ub2004img iucvserv: result length=14, send message length=14,#012 /#012iucvcmdrc=0 Dec 14 22:02:26 ub2004img kernel: [63084.184649] [ cut here ] Dec 14 22:02:26 ub2004img kernel: [63084.184654] Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'dma-kmalloc-1k' (offset 0, size 20)! Dec 14 22:02:26 ub2004img kernel: [63084.184680]
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
This bug is awaiting verification that the linux-
ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to
'verification-done-bionic'. If the problem still exists, change the tag
'verification-needed-bionic' to 'verification-failed-bionic'.
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-bionic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Released
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification:
==
[Impact]
* CEX8 hardware CryptoExpress adapter shall support quantum-safe crypto
and therefore require nowadays message sizes > 12kB.
* This change here is mainly required to support EP11 responses to admin
requests at zNext
which due to QS certificates can grow larger than 12kB.
* It's to cover a minimal patch to provide toleration support for this
feature
which shall be back-ported to all distribution releases in service at zNext
* This SRU requests belongs to the hardware enablement case.
[Fix]
* bd39654a2282 bd39654a2282c1a51c044575a6bc00d641d5dfd1 "s390/AP:
support new dynamic AP bus size limit"
[Test Plan]
* An Ubuntu 20.04 (respectively 21.04) LPAR or z/VM guest is needed
that has access to at least one online crypto domain.
* Ideally using a CEX8 adapter (but can be too early to get one).
* Then get the patched kernel installed (see PPA below).
* And look for the /sys/devices/ap/cardxx/max_msg_size sysfs
attributes.
* On top IBM has some more in-depth zcrypt tests (see also
LP#1933805).
[Where problems could occur]
* First of all the modification are limited to:
the zcrypt driver ("/drivers/s390/crypto/ap_*.*" and
"/drivers/s390/crypto/zcrypt_*.*")
hence are s390x platform specific and crypto specific and
should even affect CEX8 cards only.
So in case anything fails, it's limited to s390x cryptography,
which usually allows sw fall-backs.
* The function signature of ap_queue_info and ap_test_queue got modified,
which may lead to issues if called with the old signatures,
but that would be identified by the test compile already.
* Some minor new structures like 'info', 'ml' got introduced,
but are properly declared and initialized.
* The way ap_queue_info and ap_card_create get filled and used was changed,
therefore in some code areas slightly different data might be expected,
if not properly adapted to the new way.
But a verification test will prove this.
* The actual msg length is now handled based on bufsize rather than len
and with that zq is calculated in a different way (using
zcrypt_queue_alloc)
which may cause some side effects if not properly (alloc)
or not thoroughly done.
* in _zcrypt_send_cprb and _zcrypt_send_ep11_cprb some additional
calculations
and checks (if-stmts) were introduced, but they look sane.
* New code to identify older cards got added, since message sizes > 12kB
are supported by CEX8 and higher only.
The dispatcher responsible for choosing the right card and queue is aware
of the individual card AP bus message limit.
But already at the user space tools it should be ensured that the right
card is used.
* Nevertheless, the patch is not small, hence s390x hardware crypto
zcrypt driver needs to be properly re-tested.
[Other Info]
* The above commit/patch is upstream accepted with 5.14.
* Impish's Kernel 5.13 was already patched, based on LP#1933805.
* With that there is already a certain level of testing that was done
based on Impish (since the zcrypt driver is largely the same now with
these cherry-picks).
* Hence the SRU is only needed for Focal
and Hirsute (just to avoid regressions on upgrades).
__
Toleration support for new IBM Z crypto hardware - Backport to focal
(20.04)
Patch from kernel 5.14:
Summary: s390/AP: support new dynamic AP bus size limit
Description: This patch provides support for new dynamic AP bus
message limit with the existing zcrypt device driver
[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released 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 1950666] Re: system crash when removing ipmi_msghandler module
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1950666 Title: system crash when removing ipmi_msghandler module Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Released Status in linux source package in Jammy: In Progress Bug description: [IMPACT] Commit 3b9a907223d7 (ipmi: fix sleep-in-atomic in free_user at cleanup SRCU user->release_barrier) pushes the removal of an ipmi_user into the system's workqueue. Whenever an ipmi_user struct is about to be removed it is scheduled as a work on the system's workqueue to guarantee the free operation won't be executed in atomic context. When the work is executed the free_user_work() function is invoked which frees the ipmi_user. When ipmi_msghandler module is removed in cleanup_ipmi() function, there is no check if there are any pending works to be executed. Therefore, there is a potential race condition : An ipmi_user is scheduled for removal and shortly after to remove the ipmi_msghandler module. If the scheduled work delays execution for any reason and the module is removed first, then when the work is executed the pages of free_user_work() are gone and the system crashes with the following : BUG: unable to handle page fault for address: c05c3450 #PF: supervisor instruction fetch in kernel mode #PF: error_code(0x0010) - not-present page PGD 635420e067 P4D 635420e067 PUD 6354210067 PMD 4711e51067 PTE 0 Oops: 0010 [#1] SMP PTI CPU: 19 PID: 29646 Comm: kworker/19:1 Kdump: loaded Not tainted 5.4.0-77-generic #86~18.04.1-Ubuntu Hardware name: Ciara Technologies ORION RS610-G4-DTH4S/MR91-FS1-Y9, BIOS F29 05/23/2019 Workqueue: events 0xc05c3450 RIP: 0010:0xc05c3450 Code: Bad RIP value. RSP: 0018:b721333c3e88 EFLAGS: 00010286 RAX: c05c3450 RBX: 92a95f56a740 RCX: b7221cfd14e8 RDX: 0001 RSI: 92616040d4b0 RDI: b7221cf404e0 RBP: b721333c3ec0 R08: 73746e657665 R09: 8080808080808080 R10: b721333c3de0 R11: fefefefefefefeff R12: 92a95f570700 R13: 92a0a40ece40 R14: b7221cf404e0 R15: 092a95f57070 FS: () GS:92a95f54() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: c05c3426 CR3: 0081e9bfc005 CR4: 007606e0 DR0: DR1: DR2: DR3: DR6: fffe0ff0 DR7: 0400 PKRU: 5554 Call Trace: ? process_one_work+0x20f/0x400 worker_thread+0x34/0x410 kthread+0x121/0x140 ? process_one_work+0x400/0x400 ? kthread_park+0x90/0x90 ret_from_fork+0x35/0x40 Modules linked in: xt_REDIRECT xt_owner ipt_rpfilter xt_CT xt_multiport xt_set ip_set_hash_ip veth xt_statistic ipt_REJECT ... megaraid_sas ahci libahci wmi [last unloaded: ipmi_msghandler] CR2: c05c3450 [TEST CASE] The user who reported the issue can reproduce reliably by stopping the ipmi related services and then removing the ipmi modules. I could reproduce the issue only when turning the normal 'work' to delayed work. [WHERE PROBLEMS COULD OCCUR] The fixing patch creates a dedicated workqueue for the remove_work struct of ipmi_user when loading the ipmi_msghandler modules and destroys the workqueue when removing the module. Therefore any potential problems would occur during these two operations or when scheduling works on the dedicated workqueue. [OTHER] Upstream patches : 1d49eb91e86e (ipmi: Move remove_work to dedicated workqueue) 5a3ba99b62d8 (ipmi: msghandler: Make symbol 'remove_work_wq' static) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950666/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954926] Re: Focal: CIFS stable updates
This bug is awaiting verification that the linux- ibm-5.4/5.4.0-1014.15~18.04.1 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-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. 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-bionic -- 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/1954926 Title: Focal: CIFS stable updates Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Bug description: SRU Justification [Impact] Backport several stable updates to v5.4 Azure [Test Case] Microsoft tested [Where things could go wrong] Samba connections could fail [Other Info] SF: #00324495 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1946200] Re: With the Nvidia driver installed there is no option to use Wayland on the login screen
/etc/default/grub and adding GRUB_CMDLINE_LINUX="nvidia-drm.modeset=1" sudo upgrade-grub Thank you! Finally that worked ! (also with nvidia-driver-470) -- 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/1946200 Title: With the Nvidia driver installed there is no option to use Wayland on the login screen Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-495 package in Ubuntu: Triaged Bug description: Starting in impish with nvidia-470 and the latest gdm3 and xwayland packages, Wayland is fully supported in theory but you never get any option to select Wayland on the login screen. There is no session menu and you always get Xorg instead. WORKAROUND: Edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvidia-drm.modeset=1" and then: sudo update-grub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946200/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960242] [NEW] kernel fault on monitor wakeup, only reboot recovers.
Public bug reported: After a normal day's operations, the monitors switch off after an hour or so. Every morning since Impish, upon waking up and unlocking the system: 2 of the monitors wake, the rest remain in sleep mode. The only recourse is to do a graceful poweroff and cold boot. There is a kernel fault, as follows and in the attached file. It is 100% repeatable. [121665.686476] ceph: mds0 caps renewed [126829.470180] [ cut here ] [126829.470183] WARNING: CPU: 6 PID: 4368 at drivers/gpu/drm/ttm/ttm_bo.c:437 ttm_bo_release+0x2de/0x330 [ttm] [126829.470191] Modules linked in: ceph libceph fscache netfs xt_CHECKSUM ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_conntrack xt_MASQUERADE nf_conntrack_netlink nft_chain_nat nf_nat xfrm_user nf_conntrack xfrm_algo nf_defrag_ipv6 nf_defrag_ipv4 xt_addrtype nft_compat nft_counter br_netfilter nf_tables nfnetlink vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bridge stp llc overlay lz4 lz4_compress zram snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel snd_intel_dspcfg intel_rapl_msr snd_intel_sdw_acpi intel_rapl_common snd_hda_codec sch_fq_codel snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm snd_seq_midi edac_mce_amd snd_seq_midi_event snd_rawmidi uvcvideo msr videobuf2_vmalloc parport_pc videobuf2_memops kvm_amd videobuf2_v4l2 videobuf2_common ppdev snd_seq videodev kvm snd_seq_device lp snd_timer rapl parport eeepc_wmi wmi_bmof joydev input_leds mc k10temp ccp snd soundcore mac_hid sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor [126829.470220] zstd_compress raid6_pq libcrc32c hid_generic uas usbhid usb_storage hid amdgpu iommu_v2 gpu_sched nouveau radeon mxm_wmi i2c_algo_bit drm_ttm_helper ttm drm_kms_helper syscopyarea sysfillrect crct10dif_pclmul sysimgblt fb_sys_fops crc32_pclmul cec ghash_clmulni_intel rc_core mfd_aaeon aesni_intel asus_wmi crypto_simd sparse_keymap nvme video xhci_pci r8169 gpio_amdpt ahci drm cryptd realtek i2c_piix4 libahci xhci_pci_renesas nvme_core wmi gpio_generic [126829.470239] CPU: 6 PID: 4368 Comm: kwin_x11:cs0 Tainted: G OE 5.13.0-28-generic #31-Ubuntu [126829.470241] Hardware name: System manufacturer System Product Name/PRIME B450-PLUS, BIOS 3211 08/10/2021 [126829.470242] RIP: 0010:ttm_bo_release+0x2de/0x330 [ttm] [126829.470246] Code: e8 17 27 3f f0 e9 ac fd ff ff 49 8b 7e 98 b9 4c 1d 00 00 31 d2 be 01 00 00 00 e8 4d 4a 3f f0 49 8b 46 e8 eb 9d 4c 89 e0 eb 98 <0f> 0b 41 c7 86 84 00 00 00 00 00 00 00 49 8d 76 08 31 d2 4c 89 ef [126829.470247] RSP: 0018:b0df43547d28 EFLAGS: 00010202 [126829.470248] RAX: 0002 RBX: 0002 RCX: [126829.470249] RDX: 0001 RSI: 0246 RDI: 89e51b945ac0 [126829.470250] RBP: b0df43547d50 R08: 89e4529488e8 R09: 0002 [126829.470251] R10: 89e894fe4d38 R11: 89e51c2ffce8 R12: 89e51b9452b0 [126829.470251] R13: 89e8aa050c58 R14: 89e8aa050db8 R15: 89eb3bb8c480 [126829.470252] FS: 7f21ee182640() GS:89ec1e30() knlGS: [126829.470253] CS: 0010 DS: ES: CR0: 80050033 [126829.470254] CR2: 7fbf8805e7e8 CR3: 00045811c000 CR4: 00350ee0 [126829.470255] Call Trace: [126829.470256] [126829.470258] ttm_bo_put+0x30/0x50 [ttm] [126829.470262] amdgpu_bo_unref+0x1e/0x30 [amdgpu] [126829.470365] amdgpu_gem_object_free+0x34/0x50 [amdgpu] [126829.470454] drm_gem_object_free+0x1d/0x30 [drm] [126829.470470] drm_gem_dmabuf_release+0x40/0x60 [drm] [126829.470486] dma_buf_release+0x46/0xa0 [126829.470488] __dentry_kill+0x10e/0x190 [126829.470490] dentry_kill+0x52/0x1c0 [126829.470491] dput+0x12f/0x180 [126829.470492] __fput+0xf0/0x250 [126829.470494] fput+0xe/0x10 [126829.470495] task_work_run+0x6d/0xa0 [126829.470497] exit_to_user_mode_loop+0x150/0x160 [126829.470499] exit_to_user_mode_prepare+0x9f/0xb0 [126829.470500] syscall_exit_to_user_mode+0x27/0x50 [126829.470503] do_syscall_64+0x6e/0xb0 [126829.470504] ? do_syscall_64+0x6e/0xb0 [126829.470506] ? asm_sysvec_apic_timer_interrupt+0xa/0x20 [126829.470507] entry_SYSCALL_64_after_hwframe+0x44/0xae [126829.470509] RIP: 0033:0x7f21fb43e9cb [126829.470510] Code: ff ff ff 85 c0 79 8b 49 c7 c4 ff ff ff ff 5b 5d 4c 89 e0 41 5c c3 66 0f 1f 84 00 00 00 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 35 a4 0f 00 f7 d8 64 89 01 48 [126829.470511] RSP: 002b:7f21ee181738 EFLAGS: 0246 ORIG_RAX: 0010 [126829.470513] RAX: RBX: 7f21ee181770 RCX: 7f21fb43e9cb [126829.470513] RDX: 7f21ee181770 RSI: 40086409 RDI: 000d [126829.470514] RBP: 40086409 R08: 55849cb1c370 R09: [126829.470515] R10: R11: 0246 R12: 55849c056508 [126829.470515] R13: 000d R14: 55849c057434 R15: 7f21ee1817a0
[Kernel-packages] [Bug 1956461] Re: Creative HD720p webcam doesn't work
I've just tried 5.4.0-99.112 it still doesn't work (I mean the camera [lsusb: Bus 002 Device 005: ID 041e:4095 Creative Technology, Ltd Live! Cam Sync HD [VF0770]). I will not report the bug again. Nothing happens. I roll back to 5.4.0-91 I can't find any hardware problem so the onlu solution is to roll back and then buy another webcam. I'm not a programmer and I can't fix it by myself. -- 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/1956461 Title: Creative HD720p webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806396] Re: lis3lv02d: unknown sensor type 0x0 in HP x360 machines
Maybe it has already been fixed in 5.13.0-28.31 but I'm currently at 5.13.0-28.38 -- 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/1806396 Title: lis3lv02d: unknown sensor type 0x0 in HP x360 machines Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Hello, dmesg: [ 15.684425] lis3lv02d: unknown sensor type 0x0 Best regards, -- Cristian Aravena Romero (caravena) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2647 F pulseaudio /dev/snd/pcmC0D0p: caravena 2647 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 3 10:22:33 2018 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.18.0-11-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2018-12-02 (0 days ago) dmi.bios.date: 06/14/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.13:bd06/14/2018:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.19:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1806396/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960034] Re: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32
This bug is awaiting verification that the linux/5.13.0-30.33 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-impish' to 'verification-done-impish'. If the problem still exists, change the tag 'verification-needed-impish' to 'verification-failed-impish'. 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-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/1960034 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32 Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Status in systemd source package in Impish: Invalid Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-29.32 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413664] Re: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files
** Description changed: There is a new more efficient debug format enabled via CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need packaging in the .ddeb before we can enable this. Evaluate whether the other tooling we have will handle it before doing so. -- * all tooling supports split debug files these days + * ... apart from pahole which then fails to generate BTF info -- 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/1413664 Title: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files Status in linux package in Ubuntu: Confirmed Bug description: There is a new more efficient debug format enabled via CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need packaging in the .ddeb before we can enable this. Evaluate whether the other tooling we have will handle it before doing so. -- * all tooling supports split debug files these days * ... apart from pahole which then fails to generate BTF info To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958155] Re: Pod traffic not taking advantage of interfaces with multiple tx queues
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1958155
Title:
Pod traffic not taking advantage of interfaces with multiple tx queues
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.11 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Bug description:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx
queue hint in veth_xmit")
This patch is already scheduled for release in these stable kernel
versions:
linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record
rx queue hint in veth_xmit
linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record
rx queue hint in veth_xmit
linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record
rx queue hint in veth_xmit
linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record
rx queue hint in veth_xmit
[Test Plan]
Upstream tested
[Where things could go wrong]
Transmit performance could be impacted in other ways.
[Other Info]
SF: #00326544
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958155/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958494] Re: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking
Problem can be reproduced with 5.13.0-28.31~20.04.1 as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958494 Title: After upgrade to linux-image-5.13.0-27-generic, screen doesn't recover from blanking Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After screen was blanked (meta-L; lid closed) it wakes up with an erratic pattern, it can't recover from (except power off, power on). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 20 07:41:10 2022 InstallationDate: Installed on 2021-09-29 (112 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1959494] Re: touchpad stopped working hp envy dv6 laptop
Hi, The reason I raised it as a security issue is because the issue came up after I connected to public wifi. It resolves itself sometimes but when I connect to wifi again the cursor freezes up and I have to use a mouse. The touchpad issue might not be a security risk but I believe it is a symptom of a breach. Please look into this. Thanks for the support On Fri, Feb 4, 2022 at 10:00 PM Paulo Flabiano Smorigo < 1959...@bugs.launchpad.net> wrote: > Thanks for taking the time to report this bug and helping to make Ubuntu > better. We appreciate the difficulties you are facing, but this appears > to be a "regular" (non-security) bug. I have unmarked it as a security > issue since this bug does not show evidence of allowing attackers to > cross privilege boundaries nor directly cause loss of data/privacy. > Please feel free to report any other bugs you may find. > > ** Information type changed from Private Security to Public > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1959494 > > Title: > touchpad stopped working hp envy dv6 laptop > > Status in linux-signed-hwe-5.13 package in Ubuntu: > New > > Bug description: > I was using the laptop then all of a sudden it started hanging and the > touchpad stopped working. I was connected to a public wi-fi. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 > ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 > Uname: Linux 5.13.0-27-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.20.11-0ubuntu27.21 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat Jan 29 22:44:08 2022 > SourcePackage: linux-signed-hwe-5.13 > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959494/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1959494 Title: touchpad stopped working hp envy dv6 laptop Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: I was using the laptop then all of a sudden it started hanging and the touchpad stopped working. I was connected to a public wi-fi. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 22:44:08 2022 SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1959494/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1413664] Re: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files
** Description changed: There is a new more efficient debug format enabled via CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need packaging in the .ddeb before we can enable this. Evaluate whether the other tooling we have will handle it before doing so. + + -- + + * all tooling supports split debug files these days -- 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/1413664 Title: 15.04: consider enabling CONFIG_DEBUG_INFO_SPLIT and package the .dwo files Status in linux package in Ubuntu: Confirmed Bug description: There is a new more efficient debug format enabled via CONFIG_DEBUG_INFO_SPLIT, this spits out new .dwo files which need packaging in the .ddeb before we can enable this. Evaluate whether the other tooling we have will handle it before doing so. -- * all tooling supports split debug files these days To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960213] Re: Kernel Panic on linux-image-5.15.0-18-generic
** Package changed: ubuntu => linux-signed (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1960213 Title: Kernel Panic on linux-image-5.15.0-18-generic Status in linux-signed package in Ubuntu: New Bug description: Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012 On 5.13.0-29-generic boot successfully. Laptop: Lenovo Model: 20RA002SRT Stack trace in attached images. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1960213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960213] [NEW] Kernel Panic on linux-image-5.15.0-18-generic
You have been subscribed to a public bug: Hello. Get a Kernel Panic on linux-image-5.15.0-18-generic The same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957012 On 5.13.0-29-generic boot successfully. Laptop: Lenovo Model: 20RA002SRT Stack trace in attached images. ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Kernel Panic on linux-image-5.15.0-18-generic https://bugs.launchpad.net/bugs/1960213 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed 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 1956461] Re: Creative HD720p webcam doesn't work
@bonej079 I've tried every kernel from the 5.4 line and can confirm that Creative Live! Cam Sync HD (VF0770) doesn't work on any of them after 5.4.0-91. Once I run the system using 5.4.0-91 it works like a charm so no hardware failure for sure. -- 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/1956461 Title: Creative HD720p webcam doesn't work Status in linux package in Ubuntu: Confirmed Bug description: After installing kernel 5.4.0-92 the webcam Creative HD720p stop to be seen by the system. There is no /dev/vl4/ folder --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: piotr 3094 F pulseaudio /dev/snd/controlC0: piotr 3094 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.2 InstallationDate: Installed on 2020-06-07 (578 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: Gigabyte Technology Co., Ltd. H67MA-USB3-B3 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-92-generic root=UUID=3bdaa7b0-765c-41ce-b67a-deeeabde9c42 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 RelatedPackageVersions: linux-restricted-modules-5.4.0-92-generic N/A linux-backports-modules-5.4.0-92-generic N/A linux-firmware1.187.24 RfKill: Tags: uma Uname: Linux 5.4.0-92-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 10/27/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F4 dmi.board.name: H67MA-USB3-B3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd10/27/2011:svnGigabyteTechnologyCo.,Ltd.:pnH67MA-USB3-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH67MA-USB3-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H67MA-USB3-B3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959665] Re: linux-image-5.4.0-97.110 freezes by accessing cifs shares
This bug was fixed in the package linux - 5.4.0-99.112 --- linux (5.4.0-99.112) focal; urgency=medium * focal/linux: 5.4.0-99.112 -proposed tracker (LP: #1959817) * linux-image-5.4.0-97.110 freezes by accessing cifs shares (LP: #1959665) - Revert "cifs: To match file servers, make sure the server hostname matches" - Revert "cifs: set a minimum of 120s for next dns resolution" - Revert "cifs: use the expiry output of dns_query to schedule next resolution" -- Stefan Bader Wed, 02 Feb 2022 17:21:18 +0100 ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1959665 Title: linux-image-5.4.0-97.110 freezes by accessing cifs shares Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Bug description: Ubuntu 20.04 with kernel image 5.4.0-97.110 randomly freezes when we access cifs shares. The system needs a hard reset after the freeze. The previous kernel image (5.4.0-96.109) does not show this behavior. Multiple Ubuntu 20.04 systems running on kernel image 9.4.0-97.110 are affected on our sites. The cifs shares are accessed via autofs using Kerberos authentication. The following info is the only error message we could actively catch on a different system before the system was frozen: general protection fault: [#3] SMP PTI CPU: 0 PID: 21294 Comm: automount Tainted: G DOE 5.4.0-97-generic #110-Ubuntu Hardware name: Dell Inc. Precision 7530/03RV2M, BIOS 1.14.4 10/21/2020 RIP: 0010:kmem_cache_alloc_trace+0x8c/0x240 Code: 08 65 4c 03 05 1d e8 f7 6e 49 83 78 10 00 4d 8b 38 0f 84 92 01 00 00 4d 85 ff 0f 84 89 01 00 00 41 8b 41 20 49 8b 39 4c 01 f8 <48> 8b 18 48 89 c1 49 33 99 70 01 00 00 4c 89 f8 48 0f c9 48 31 cb RSP: 0018:a6ca860f7ba0 EFLAGS: 00010286 RAX: fdd44d7c219190e1 RBX: RCX: RDX: d558 RSI: 0cc0 RDI: 00035060 RBP: a6ca860f7bd0 R08: 99233c035060 R09: 992338c079c0 R10: 0001 R11: 0004 R12: 0cc0 R13: 000b R14: 992338c079c0 R15: fdd44d7c219190e1 FS: 7fdc24e29700() GS:99233c00() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 7f15a80ee010 CR3: 0007e36b2006 CR4: 003606f0 Call Trace: ? proc_self_get_link+0x70/0xd0 proc_self_get_link+0x70/0xd0 link_path_walk.part.0+0x478/0x550 ? trailing_symlink+0x1d1/0x280 path_openat+0xb7/0x290 do_filp_open+0x91/0x100 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 ? unuse_pde+0x30/0x30 do_sys_open+0x17e/0x290 __x64_sys_openat+0x20/0x30 __orig_openat+0x71/0xc0 [eset_rtp] ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __x64_sys_futex+0x13f/0x170 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 ? __switch_to_asm+0x34/0x70 ? __switch_to_asm+0x40/0x70 __x64_sys_ertp_openat+0x29/0x60 [eset_rtp] do_syscall_64+0x57/0x190 entry_SYSCALL_64_after_hwframe+0x44/0xa9 RIP: 0033:0x7fdc28a41f24 Code: 24 20 eb 8f 66 90 44 89 54 24 0c e8 56 68 f8 ff 44 8b 54 24 0c 44 89 e2 48 89 ee 41 89 c0 bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 77 32 44 89 c7 89 44 24 0c e8 88 68 f8 ff 8b 44 RSP: 002b:7fdc24e25980 EFLAGS: 0293 ORIG_RAX: 0101 RAX: ffda RBX: 7fdc040008d0 RCX: 7fdc28a41f24 RDX: 0008 RSI: 564d4410a8c8 RDI: ff9c RBP: 564d4410a8c8 R08: R09: 0001 R10: R11: 0293 R12: 0008 R13: 564d4410e28a R14: 7fdc24e25b40 R15: 7fdc24e28fc0 Modules linked in: cmac nls_utf8 cifs fscache libdes ccm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) eset_rtp(OE) xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
[Kernel-packages] [Bug 1958228] Re: aufs build is broken on 5.11 kernels
Only a few 5.11 kernels have AUFS config enabled and focal:linux- hwe-5.11 is not one of them, so the fix cannot be verified with this kernel. However, this fix has been cherry-picked by focal:linux- oracle-5.11 and focal:linux-riscv-5.11 by versions which were already promoted to -updates: https://launchpad.net/ubuntu/+source/linux-oracle-5.11/5.11.0-1028.31~20.04.1 https://launchpad.net/ubuntu/+source/linux-riscv-5.11/5.11.0-1029.32~20.04.1 Therefore I will mark this bug as verified in Focal. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1958228 Title: aufs build is broken on 5.11 kernels Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux-hwe-5.11 source package in Hirsute: Fix Committed Bug description: [ Impact ] Commit 35e8d405b009 "fs: export an inode_update_time helper" (upstream commit e60feb445fce9e51c1558a6aa7faf9dd5ded533b), applied to hirsure:linux via upstream stable broke the build of aufs. The function 'update_time()' is used by aufs and was exported before by a SAUCE patch (0d3312035010 "UBUNTU: SAUCE: Import aufs driver"). [ Fix ] The proposed fix is to patch aufs to use the new function name. There is no functional change. [ Test ] Build a 5.11 kernel with AUFS enabled. [ Where problems could occur ] By keeping the new function name, if any other internal or external module is using 'update_time()' their build will also fail. This will need to be addressed case-by-case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958153] Re: [SRU][F] Add firmware of MT7922
** Tags added: verification-done-focal -- 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/1958153 Title: [SRU][F] Add firmware of MT7922 Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Committed Bug description: [Impact] No driver is loaded for MT7922, and fw is missing too. [Fix] Add firmware of MT7922 wifi and bluetooth. [Test] Verified on RZ616, it works fine, suspend OK. iperf test result looks fine. Bluetooth works fine. [Where problems could occur] These firmware is specific for MT7922, it should be low risk. The firmware is already in impish and jammy, only SRU fw for focal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1958153/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922
** Tags removed: verification-needed-impish ** Tags added: verification-done-impish -- 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/1958151 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922 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: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] No driver is loaded for MT7922, and fw is missing too. [Fix] Add basic support of MT7922, and add ID of AMD RZ616/RZ608. Enable 160Mhz channel. [Test] Verified on RZ616, it works fine, suspend OK. iperf test result looks fine. Bluetooth works fine. [Where problems could occur] It may break MT7921 wifi support which shares mt7921e driver. Almost the code is specific for MT7922, checking security fw is based on MT7922 fw. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958228] Re: aufs build is broken on 5.11 kernels
Changing nomination from hirsute/linux to focal/linux-hwe-5.11 as Hirsute has reached EOL. ** Also affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-5.11 (Ubuntu Hirsute) Status: New => Fix Committed ** Changed in: linux (Ubuntu Hirsute) Status: Fix Committed => Won't 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/1958228 Title: aufs build is broken on 5.11 kernels Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux source package in Hirsute: Won't Fix Status in linux-hwe-5.11 source package in Hirsute: Fix Committed Bug description: [ Impact ] Commit 35e8d405b009 "fs: export an inode_update_time helper" (upstream commit e60feb445fce9e51c1558a6aa7faf9dd5ded533b), applied to hirsure:linux via upstream stable broke the build of aufs. The function 'update_time()' is used by aufs and was exported before by a SAUCE patch (0d3312035010 "UBUNTU: SAUCE: Import aufs driver"). [ Fix ] The proposed fix is to patch aufs to use the new function name. There is no functional change. [ Test ] Build a 5.11 kernel with AUFS enabled. [ Where problems could occur ] By keeping the new function name, if any other internal or external module is using 'update_time()' their build will also fail. This will need to be addressed case-by-case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960219] Re: TPLink (UB500) usb bluetooth adapter support in Ubuntu 21.10
** Description changed: Currently there is no support for TPLink (UB500) nano usb bluetooth - adapter in Ubuntu 21.10. While checking it was found that + adapter in Ubuntu 21.10. While checking it was found that adding + https://github.com/torvalds/linux/commit/4fd6d490796171bf786090fee782e252186632e4 + to btusb.c and creating new btusb.ko manually could solve the issue.So i + was hoping the above patch can be added to the Ubuntu kernel (linux + 5.13.0.28) as default. -- 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/1960219 Title: TPLink (UB500) usb bluetooth adapter support in Ubuntu 21.10 Status in linux package in Ubuntu: New Bug description: Currently there is no support for TPLink (UB500) nano usb bluetooth adapter in Ubuntu 21.10. While checking it was found that adding https://github.com/torvalds/linux/commit/4fd6d490796171bf786090fee782e252186632e4 to btusb.c and creating new btusb.ko manually could solve the issue.So i was hoping the above patch can be added to the Ubuntu kernel (linux 5.13.0.28) as default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958777] Re: Noise before login screen with 5.13 kernel on kUbuntu
*** This bug is a duplicate of bug 1958283 *** https://bugs.launchpad.net/bugs/1958283 ** This bug has been marked a duplicate of bug 1958283 linux-firmware missing renoir_ta -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958777 Title: Noise before login screen with 5.13 kernel on kUbuntu Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After updating kernel to 5.13, when I boot my laptop (Lenovo Ideapad Gaming 3 with AMD Ryzen 7 4th. gen), I see only noise before the login screen. If I choose 5.11 kernel everything works fine. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960219] [NEW] TPLink (UB500) usb bluetooth adapter support in Ubuntu 21.10
Public bug reported: Currently there is no support for TPLink (UB500) nano usb bluetooth adapter in Ubuntu 21.10. While checking it was found that ** 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/1960219 Title: TPLink (UB500) usb bluetooth adapter support in Ubuntu 21.10 Status in linux package in Ubuntu: New Bug description: Currently there is no support for TPLink (UB500) nano usb bluetooth adapter in Ubuntu 21.10. While checking it was found that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958777] Re: Noise before login screen with 5.13 kernel on kUbuntu
@juergh, thank you very much! Now, with this version of the firmware everything works fine! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958777 Title: Noise before login screen with 5.13 kernel on kUbuntu Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After updating kernel to 5.13, when I boot my laptop (Lenovo Ideapad Gaming 3 with AMD Ryzen 7 4th. gen), I see only noise before the login screen. If I choose 5.11 kernel everything works fine. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1938531] Re: support signed v4l2loopback dkms build
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1938531 Title: support signed v4l2loopback dkms build Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] v4l2loopback is used as a critical role on Intel IPU6 camera platforms, which takes userspace middleware involvements to correctly configure hardware sensors. While all the legacy camera applications are not yet learned how to support libcamera, v4l2loopback and a v4l2-relayd step in as a video streaming proxy for backward compatibility. To preinstall v4l2loopback kernel module on secureboot systems, signed modules should be used. [Fix] All Ubuntu specific changes to enable signed v4l2loopback dkms builds. [Test Case] Install signed modules package and check `modinfo v4l2loopback`. [Where problems could occur] N/A. [Other Info] This adds current revision of v4l2loopback in the ubuntu archive. While some other fixes are also needed for v4l2loopback/focal, expects version bumps recently. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1938531/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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 OEM Priority Project: New Status in linux package in Ubuntu: Fix Released 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: Fix Released 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 1955443] Re: Fix USB3 detection on HP dock
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1955443 Title: Fix USB3 detection on HP dock Status in HWE Next: New Status in linux package in Ubuntu: Fix Released 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: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Hotplug a USB3 device to HP dock can go undetected. [Fix] Add a delay for USB3 hub resume routine so the link has enough time to transit to U0. [Test] After the patch is applied, the dock can always detect USB3 devices. [Where problems could occur] A non-noticeable delay was added, so no basically no impact. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956720] Re: Focal update: upstream stable patchset 2022-01-07
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956720 Title: Focal update: upstream stable patchset 2022-01-07 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-07 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956373] Re: Fix for rare (~1%) s0ix failures o AMD systems
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956373 Title: Fix for rare (~1%) s0ix failures o AMD systems Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: [Impact] A rare (~1%) failure has been reported in the community for a period of time on Renoir platforms with s0ix. This failure was also corroborated once by a Cezanne user. [Fix] In the s0ix entry need retain gfx in the gfxoff state, so skipping setting gfx cgpg in the S0ix suspend-resume process. The fix was cherry-picked from 5.16-rc8. [Test] This is requested by AMD. [Where problems could occur] Low risk. This only affects AMD systems that support s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1955790] Re: Got black screen when resume from s2idle with AMD dGPU
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1955790 Title: Got black screen when resume from s2idle with AMD dGPU Status in HWE Next: New Status in linux package in Ubuntu: Fix Released 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 Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] On Dell AIO with AMD dGPU platforms, it looks like AMD dGPU can't be waken up after s2idle and got black screen. [Fix] AMD provides us 2 commits to fix this issue. https://patchwork.freedesktop.org/patch/463002/ https://patchwork.freedesktop.org/series/98338/ [Test] Verified by AMD. [Where problems could occur] It should be fine to reset the asic and set to the proper state while entering suspended. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1955790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956443] Re: Fix spurious wakeup caused by Intel 7560 WWAN
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956443 Title: Fix spurious wakeup caused by Intel 7560 WWAN 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: Fix Released Bug description: [Impact] Spurious wakeup from s2idle caused by Intel 7560 WWAN device. [Fix] Keep the device at D0 to prevent the unwanted wakeup. Since PCIe ASPM is enabled, the power consumption impact is minimal. [Test] No more spurious wakeup on s2idle. [Where problems could occur] If the device somehow requires to be power-cycled via D3, this may break the assumption. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956443/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958151] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1958151 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922 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: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] No driver is loaded for MT7922, and fw is missing too. [Fix] Add basic support of MT7922, and add ID of AMD RZ616/RZ608. Enable 160Mhz channel. [Test] Verified on RZ616, it works fine, suspend OK. iperf test result looks fine. Bluetooth works fine. [Where problems could occur] It may break MT7921 wifi support which shares mt7921e driver. Almost the code is specific for MT7922, checking security fw is based on MT7922 fw. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956985] Re: Focal update: v5.14.21 upstream stable release
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956985 Title: Focal update: v5.14.21 upstream stable release Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.14.21 upstream stable release from git://git.kernel.org/ Linux 5.14.21 Revert "ACPI: scan: Release PM resources blocked by unused objects" thermal: Fix NULL pointer dereferences in of_thermal_ functions perf/core: Avoid put_page() when GUP fails PCI: Add MSI masking quirk for Nvidia ION AHCI PCI/MSI: Deal with devices lying about their MSI mask capability PCI/MSI: Destroy sysfs before freeing entries parisc/entry: fix trace test in syscall exit path Bluetooth: btusb: Add support for TP-Link UB500 Adapter bootconfig: init: Fix memblock leak in xbc_make_cmdline() loop: Use blk_validate_block_size() to validate block size block: Add a helper to validate the block size fortify: Explicitly disable Clang support KVM: Fix steal time asm constraints Revert "drm: fb_helper: fix CONFIG_FB dependency" Revert "drm: fb_helper: improve CONFIG_FB dependency" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1956985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956407] Re: Add missing BT ID for Qualcomm WCN6856
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956407 Title: Add missing BT ID for Qualcomm WCN6856 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 source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.13 source package in Jammy: Invalid Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] WCN6856 Bluetooth doesn't work. [Fix] Add one more ID for BT. [Test] Verified by our engineers and Dell on some Dell platforms with WCN6856 card. [Where problems could occur] Adding ID doesn't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958371] Re: Focal update: upstream stable patchset 2022-01-19
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1958371 Title: Focal update: upstream stable patchset 2022-01-19 Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-01-19 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.14/+bug/1958371/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1956454] Re: Enable audio mute LED and mic mute LED on a new HP laptop
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1956454 Title: Enable audio mute LED and mic mute LED on a new HP laptop 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: Fix Released Status in linux source package in Jammy: Confirmed Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] Audio mute LED and mic mute LED are not working on a new HP laptop. [Fix] Use another audio quirk to enable the feature. [Test] With the patch applied, both LEDs start working. [Where problems could occur] This fix is limit to one device, so other devices are totally unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1956454/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959061] Re: The display output on type-c hub doesn't work on ADL platform
This bug was fixed in the package linux-oem-5.14 - 5.14.0-1022.24 --- linux-oem-5.14 (5.14.0-1022.24) focal; urgency=medium * focal/linux-oem-5.14: 5.14.0-1022.24 -proposed tracker (LP: #1959585) * Got black screen when resume from s2idle with AMD dGPU (LP: #1955790) - drm/amdgpu: don't do resets on APUs which don't support it * CVE-2022-0330 - drm/i915: Flush TLBs before releasing backing store * CVE-2022-22942 - SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy * CVE-2022-23222 - bpf: Don't promote bogus looking registers after null check. - bpf, selftests: Add verifier test for mem_or_null register with offset. * CVE-2022-24122 - ucount: Make get_ucount a safe get_user replacement * The display output on type-c hub doesn't work on ADL platform (LP: #1959061) - SAUCE: drm/i915/adlp: Fix TypeC PHY-ready status readout -- Timo Aaltonen Mon, 31 Jan 2022 17:45:20 +0200 ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-0330 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-22942 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-23222 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-24122 -- 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/1959061 Title: The display output on type-c hub doesn't work on ADL platform Status in HWE Next: New Status in linux package in Ubuntu: In Progress 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 Released Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] The display output(DP/HDMI) on the USB type-c hub doesn't work. No display output device could be found after the monitor is plugged into the hub. [Fix] Intel provide a new patch to fix this issue on ADL platforms. [Test] Verified on ADL platform with different type-c hubs, the display output works. [Where problems could occur] The TCSS_DDI_STATUS register is indexed by tc_port not by the FIA port index. So, this patch is more like a fix and only affect ADL platforms. And as the commit log describes, the value is wrong on TC#3/4 ports, so it won't affect the origin working ports. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1959061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960129] Re: kernelpanic on shutdown
The output was " no additional information collected" -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960129 Title: kernelpanic on shutdown Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: I'm using an acer Aspire v nitro. Since the kernel upgrade to 13.0-27, shutting down the computer leads to a kernel panic. kernel 11 still works fine. The problem first appeared around 3 weeks ago. As far as we could tell, something's up with the sound driver, snd_hda_intel. I've been having problems with my sound driver/ sound card for a year now, It doesn't recognize the internal speaker (with no other hardware connected, the only option is dummy audio output) and microphones. my workaround is bluetooth speakers or headsets/ microphones that come with their own soundcard. 3484.141442 Kernel panic -not syncing:Attempted to kill init! exitcode=OxO009 3484.142908 Kernel Offset:Ox13a0 from Ox8100 (relocation range: 0oxao00-0xbff t 3484.167173] ---t end Kernel panic not syncing:Attempted to kill init! exitcode=0x0009 1-- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 5 12:18:04 2022 InstallationDate: Installed on 2021-12-04 (63 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958724] Re: System Shutdown and resume hangs since Kernel linux-image-5.13.0-23-generic
Same here, cleared with 5.13.0-28 update. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958724 Title: System Shutdown and resume hangs since Kernel linux- image-5.13.0-23-generic Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: Hi, on my Medion E14304 Ubuntu was working fine until Kernel 5.13.0.21. Since Version 5.13.0.23 System Shutdown and resume hangs. The System does not stop also after a long time. The last messages in recovery mode on the root console are: Reached target Power-off ... systemd-udevd[295]: ... Worker [311] processing SEQNUM=3047 is taking time Waiting for process systemd-udevd, systemd-udevd Perhaps my attached dmesg and lsmod helps. All messages are in one file. Thank you very much. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 22 16:59:05 2022 InstallationDate: Installed on 2021-12-25 (27 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958724/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959921] Re: linux-image-5.13.0-28 makes computer freeze
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1959921 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** 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/1959921 Title: linux-image-5.13.0-28 makes computer freeze Status in linux package in Ubuntu: Incomplete Bug description: AMD Ryzen 3200G processor Asus mainboard System freezez after short tme of using happens only with linux-image-5.13.0-28, all other kernels work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1959921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960129] Re: kernelpanic on shutdown
Please run 'apport-collect 1960129'. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960129 Title: kernelpanic on shutdown Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: I'm using an acer Aspire v nitro. Since the kernel upgrade to 13.0-27, shutting down the computer leads to a kernel panic. kernel 11 still works fine. The problem first appeared around 3 weeks ago. As far as we could tell, something's up with the sound driver, snd_hda_intel. I've been having problems with my sound driver/ sound card for a year now, It doesn't recognize the internal speaker (with no other hardware connected, the only option is dummy audio output) and microphones. my workaround is bluetooth speakers or headsets/ microphones that come with their own soundcard. 3484.141442 Kernel panic -not syncing:Attempted to kill init! exitcode=OxO009 3484.142908 Kernel Offset:Ox13a0 from Ox8100 (relocation range: 0oxao00-0xbff t 3484.167173] ---t end Kernel panic not syncing:Attempted to kill init! exitcode=0x0009 1-- ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.13.0-27-generic 5.13.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Feb 5 12:18:04 2022 InstallationDate: Installed on 2021-12-04 (63 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.13 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960129/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960018] Re: Boot Failure - linux-image-5.13.0-28-generic | regression
** Package changed: linux (Ubuntu) => linux-hwe-5.13 (Ubuntu) -- 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/1960018 Title: Boot Failure - linux-image-5.13.0-28-generic | regression Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.3 Installed since May 2020, now fails to boot into graphics mode after upgrade to kernel version linux-image-5.13.0-27-generic - Have tried linux-image-5.13.0-28-generic with same result, I have reverted back to 5.11.0.40 which works correctly. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christian 1890 F pulseaudio /dev/snd/controlC0: christian 1890 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-06 (639 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81MT Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-40-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-40.44~20.04.2-generic 5.11.22 RelatedPackageVersions: linux-restricted-modules-5.11.0-40-generic N/A linux-backports-modules-5.11.0-40-generic N/A linux-firmware 1.187.25 Tags: focal Uname: Linux 5.11.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/09/2019 dmi.bios.release: 2.23 dmi.bios.vendor: LENOVO dmi.bios.version: 8ZCN23WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo V145-15AST dmi.ec.firmware.release: 2.23 dmi.modalias: dmi:bvnLENOVO:bvr8ZCN23WW(V2.02):bd05/09/2019:br2.23:efr2.23:svnLENOVO:pn81MT:pvrLenovoV145-15AST:skuLENOVO_MT_81MT_BU_idea_FM_V145-15AST:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoV145-15AST: dmi.product.family: V145-15AST dmi.product.name: 81MT dmi.product.sku: LENOVO_MT_81MT_BU_idea_FM_V145-15AST dmi.product.version: Lenovo V145-15AST dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960018/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960159] Re: 5.13 amdgpu, random pixel screen
Can you try linux-firmware 1.187.26 from focal proposed? https://launchpad.net/ubuntu/+archive/primary/+files/linux- firmware_1.187.26_all.deb ** Package changed: linux (Ubuntu) => linux-hwe-5.13 (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/1960159 Title: 5.13 amdgpu, random pixel screen Status in linux-hwe-5.13 package in Ubuntu: New Bug description: Hi, I have a Laptop with a Ryzen 5500U, running Linux Mint 20.3. To make use of the graphics driver, I update the kernel from 5.4 to 5.13. The computer is booting up, the LM splash screen apprears and then the screen gets funky with a random assignment of pixels. It seems each pixel gets a random assigned color (white, red, blue, green?, black). The pixels change color roughly every 200-500 ms. This happens with 5.13.0-28 and 5.13.0-23. The laptop is not responding to anything. Using 5.11.22 works without any flaws. AMD gpu drivers are installed correctly. Mandatory information 1st: This one is running: Ubuntu 5.11.0-43.47~20.04.2-generic 5.11.22 Description: Linux Mint 20.3 Release: 20.3 description: Notebook product: 82LM (LENOVO_MT_82LM_BU_idea_FM_IdeaPad 5 14ALC05) vendor: LENOVO version: IdeaPad 5 14ALC05 serial: MP1X width: 64 bits To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1960159/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958777] Re: Noise before login screen with 5.13 kernel on kUbuntu
Can you try linux-firmware 1.187.26 from focal proposed? https://launchpad.net/ubuntu/+archive/primary/+files/linux- firmware_1.187.26_all.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958777 Title: Noise before login screen with 5.13 kernel on kUbuntu Status in linux-signed-hwe-5.13 package in Ubuntu: Confirmed Bug description: After updating kernel to 5.13, when I boot my laptop (Lenovo Ideapad Gaming 3 with AMD Ryzen 7 4th. gen), I see only noise before the login screen. If I choose 5.11 kernel everything works fine. lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1958777/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960011] Re: Laptop internal display random noise, external monitor works. Rolling back to 5.11.0-46-generic works, kernels 5.13.0-27-generic and linux-image-5.13.0-28-generic d
Can you try linux-firmware 1.187.26 from focal proposed? https://launchpad.net/ubuntu/+archive/primary/+files/linux- firmware_1.187.26_all.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1960011 Title: Laptop internal display random noise, external monitor works. Rolling back to 5.11.0-46-generic works, kernels 5.13.0-27-generic and linux- image-5.13.0-28-generic does not work Status in linux-signed-hwe-5.13 package in Ubuntu: New Bug description: Issue: Laptop internal display random noise, external monitor works. Rolling back to 5.11.0-46-generic works Both kernels below causes he same issue 5.13.0-27-generic 5.13.0-28-generic First i thought it was due to installing CUDA. But removing CUDA and NVIDIA drivers didn't work. Only switching kernels did. I used the "ubuntu-bug linux" command to report this so i assume all necessary files are included automatically ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-46-generic 5.11.0-46.51~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-46.51~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Feb 4 11:38:31 2022 InstallationDate: Installed on 2021-07-22 (196 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1960011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
