[Kernel-packages] [Bug 1954676] Re: jammy 5.15 soft lockup when zfs.ko is loaded on s390x
New debdiff in attach, that also includes the fix for a potential data corruption with zfs-2.1.1 (https://github.com/openzfs/zfs/issues/12762). ** Bug watch added: github.com/openzfs/zfs/issues #12762 https://github.com/openzfs/zfs/issues/12762 ** Patch added: "zfs-update-to-2.1.1-v2.debdiff" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+attachment/5547945/+files/zfs-update-to-2.1.1-v2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1954676 Title: jammy 5.15 soft lockup when zfs.ko is loaded on s390x Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Jammy: New Bug description: [Impact] Installing zfs-dkms seems to trigger a soft lockup issue as soon as zfs.ko is loaded. When the soft lockup happens the system isn't reachable anymore via ssh and on the console we can see some exlicit rcu stall warnings. [Test case] On s390x install the latest 5.15 Jammy kernel and run: apt install zfs-dkms [Fix] Moving to zfs 2.1.1 (from Debian) seems to fix the problem. [Regression potential] It is a major zfs update so we may introduce zfs regressions, but it seems sane to be aligned with the upstream zfs version. Also the zfs smoke tests passed across all architectures, so moving to this new version seems the right thing to do. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1954676/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950644] Re: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels
Issue spotted on T-azure-4.15 4.15.0-1129.142~14.04.1 Running tests... tst_test.c:1313: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:115: TPASS: TestName: invalid-fd: EBADF (9) finit_module02.c:115: TPASS: TestName: zero-fd: EINVAL (22) finit_module02.c:115: TPASS: TestName: null-param: EFAULT (14) finit_module02.c:115: TPASS: TestName: invalid-param: EINVAL (22) finit_module02.c:115: TPASS: TestName: invalid-flags: EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:115: TPASS: TestName: no-perm: EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:115: TPASS: TestName: module-exists: EEXIST (17) finit_module02.c:115: TFAIL: TestName: file-not-readable expected ETXTBSY: EBADF (9) finit_module02.c:115: TPASS: TestName: directory: EINVAL (22) Summary: passed 8 failed 1 broken 0 skipped 0 warnings 0 -- 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/1950644 Title: ubuntu_ltp_syscalls / finit_module02 fails on v4.15 and other kernels Status in ubuntu-kernel-tests: New 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 Bionic: Fix Committed Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux-oem-5.14 source package in Bionic: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid 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: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid 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] Some uses of kernel_read_file_from_fd may lead to a WARN when the file is not opened for reading. The WARNING, however, is not present on earlier kernels, which will return a different error code. The fix, however, has been applied to upstream stable and may be worth so tests can PASS without much change. [Fix/Backport] The fix is trivial, but the backport for Focal and Bionic was picked up from 5.4.y upstream stable tree, because the function was moved to a different file. [Test case] The finit_module02 test case from LTP covers this. [Potential regression] kernel_read_file_from_fd is used for module loading and kexec, so there is where regressions might show up. = ubuntu_ltp / finit_module02 fails on Bionic Azure FIPS (4.15.0-2039.43), Bionic Azure (4.15.0-1127.140), Focal Azure (5.4.0-1064.67): tst_test.c:1363: TINFO: Timeout per run is 0h 05m 00s finit_module02.c:119: TPASS: TestName: invalid-fd : EBADF (9) finit_module02.c:119: TPASS: TestName: zero-fd : EINVAL (22) finit_module02.c:119: TPASS: TestName: null-param : EFAULT (14) finit_module02.c:119: TPASS: TestName: invalid-param : EINVAL (22) finit_module02.c:119: TPASS: TestName: invalid-flags : EINVAL (22) tst_capability.c:29: TINFO: Dropping CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: no-perm : EPERM (1) tst_capability.c:41: TINFO: Permitting CAP_SYS_MODULE(16) finit_module02.c:119: TPASS: TestName: module-exists : EEXIST (17) finit_module02.c:119: TFAIL: TestName: file-not-readable expected EBADF: ETXTBSY (26) finit_module02.c:119: TPASS: TestName: directory : EINVAL (22) HINT: You _MAY_ be missing kernel fixes, see: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=032146cda855 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1950644/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954998] Re: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp
Jammy has already the fixes at least since Ubuntu-5.15.0-14.14. ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954998 Title: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp 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: New Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: On some designs that have sensor-fusion-hub (SFH) they need to have MP2 going into proper state for suspend/resume to work properly. This requires backporting some code into amd-sfh driver from upstream. The following 4 commits from 5.15 will enable this: 3978f54817559b28535c58a00d3d31bbd5d0b65a 173709f50e98df4c49c2776834605a2f7ed3e681 ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 0873d1afacd2167e717ea751fe7274011cb4c26a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954998] [NEW] Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp
Public bug reported: On some designs that have sensor-fusion-hub (SFH) they need to have MP2 going into proper state for suspend/resume to work properly. This requires backporting some code into amd-sfh driver from upstream. The following 4 commits from 5.15 will enable this: 3978f54817559b28535c58a00d3d31bbd5d0b65a 173709f50e98df4c49c2776834605a2f7ed3e681 ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 0873d1afacd2167e717ea751fe7274011cb4c26a ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Fix Released ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1950810 ** Tags added: amd oem-priority originate-from-1950810 ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Description changed: - TBD. + On some designs that have sensor-fusion-hub (SFH) they need to have MP2 + going into proper state for suspend/resume to work properly. + + This requires backporting some code into amd-sfh driver from upstream. + The following 4 commits from 5.15 will enable this: + + 3978f54817559b28535c58a00d3d31bbd5d0b65a + 173709f50e98df4c49c2776834605a2f7ed3e681 + ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 + 0873d1afacd2167e717ea751fe7274011cb4c26a -- 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/1954998 Title: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp 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: New Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: On some designs that have sensor-fusion-hub (SFH) they need to have MP2 going into proper state for suspend/resume to work properly. This requires backporting some code into amd-sfh driver from upstream. The following 4 commits from 5.15 will enable this: 3978f54817559b28535c58a00d3d31bbd5d0b65a 173709f50e98df4c49c2776834605a2f7ed3e681 ac15e9196f35d88b4d94bbcf3a5294ebb5622eb0 0873d1afacd2167e717ea751fe7274011cb4c26a To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954998/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
Upload log for #2. ** Attachment added: "fifo-pipe-underrun.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954728/+attachment/5547936/+files/fifo-pipe-underrun.log -- 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/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
Hi Jeff, Product Name: QLogic 2x25GE QL41262HMKR CNA has been used for FCoE connections. -- 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/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Incomplete Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581761 Title: Kernel panic - not syncing - Attempted to kill init Status in linux package in Ubuntu: Expired Status in lvm package in Ubuntu: Expired Bug description: Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to kill init'. I tried to use previous kernel, then reinstall kernels but all that didn't help me. I have luks encrypted partition which contains multiple lvm with ext4 volumes. This was working since 14.04 was released so this not standard configuration should not cause this issue. I am able to run live cd, then decrypt luks partition and mount volumes and chroot. All seems to be ok. I fsck lvm and all is ok. I found similar issue https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping for 5 secs" message on the stacktrace in the middle) but this didn't solve the issue. Maybe I enter this hack too early in the script? No more idea... so mayday, mayday... I attached photo of the stacktrace and report of 'apport-cli linux-generic'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
[Expired for lvm (Ubuntu) because there has been no activity for 60 days.] ** Changed in: lvm (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1581761 Title: Kernel panic - not syncing - Attempted to kill init Status in linux package in Ubuntu: Expired Status in lvm package in Ubuntu: Expired Bug description: Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to kill init'. I tried to use previous kernel, then reinstall kernels but all that didn't help me. I have luks encrypted partition which contains multiple lvm with ext4 volumes. This was working since 14.04 was released so this not standard configuration should not cause this issue. I am able to run live cd, then decrypt luks partition and mount volumes and chroot. All seems to be ok. I fsck lvm and all is ok. I found similar issue https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping for 5 secs" message on the stacktrace in the middle) but this didn't solve the issue. Maybe I enter this hack too early in the script? No more idea... so mayday, mayday... I attached photo of the stacktrace and report of 'apport-cli linux-generic'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947464] Re: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947464 Title: Touchpad of Logitech K400 Plus Wireless Touch Keyboard is wrongly recognized as a mouse Status in linux package in Ubuntu: Expired Bug description: Hi The following problem has existed for years on Linux or Ubuntu. As the title of the bug report suggests, the touchpad of a Logitech K400 Plus Wireless Touch Keyboard [1] is wrongly recognized as a mouse. Touchpad features like scrolling, tapping, etc. do not work at all. As requested in the DebuggingTouchpadDetection [2] guidelines, I have gathered and attached the required hardware information. I hope this helps to fix this annoying problem that has been going on for years. Best regards, Ettore Atalan [1] Logitech product page: https://www.logitech.com/en-us/products/keyboards/k400-plus-touchpad-keyboard.920-007119.html [2] https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947464/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1947472] Re: Medion Akoya S15449: Touchpad key missing
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947472 Title: Medion Akoya S15449: Touchpad key missing Status in linux package in Ubuntu: Expired Bug description: Hardware: Medion Akoya S15449 Ubuntu Budgie 21.10 budgie-desktop 10.5.3 Kernel: 5.13.0-19-generic The right "mouse button" of the touchpad is not working. It works in Windows. It works with the same Ubuntu Budgie version running in a VirtualBox. It works with an external mouse connected via USB. But it does not work on a stand-alone Ubuntu Budgie 21.10 with the built-in touchpad. I suspect this bug is related to a known kernel bug: https://bugzilla.kernel.org/show_bug.cgi?id=213031 because with previous kernel versions both touchpad and keykoard didn't work at all with any Linux on the Medion Akoya S15449. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: buth 1014 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME DistroRelease: Ubuntu 21.10 InstallationDate: Installed on 2021-10-16 (0 days ago) InstallationMedia: Ubuntu-Budgie 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: MEDION S15449 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-19-generic root=UUID=5dbb10f5-fce0-4cd7-a1f9-b6d787b5fe9b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 Tags: impish Uname: Linux 5.13.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 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:pnS15449:pvrDefaultstring:skuML-23000830030870:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15449 dmi.product.sku: ML-230008 30030870 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/1947472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954728] Re: Fix No Screen after login to Desktop on sku with 3840x2400 panel
I test the test kernel built by Koba, https://drive.google.com/drive/folders/10ns_2dnmPRf091L3LABpIh680kStvTk4?usp=sharing sku: FPA-DVT2-C6 BIOS: 0.0.26 It still have the error in kernel, but the screen can show successfully. I tried pure 5.14.0-1011-oem, the issue is still reproduced. Therefore, I think the patch set indeed fix something, but it won't get rid off "kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder," however, my local build drmtip [1] can eliminate the error message. [1] https://drive.google.com/drive/folders/1nS8Vm1SFLCvPPQJiQdFzthsia_FG6yFC?usp=sharing @koba Would you please check if it includes all required patch? Currently, we have some problem on other platform STRADL-DVT2-C4/C5B, it will cause it failed to suspend/resume. -- 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/1954728 Title: Fix No Screen after login to Desktop on sku with 3840x2400 panel Status in HWE Next: New Status in OEM Priority Project: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: New Bug description: [Impact] Got kernel report CPU pipe A FIFO underrun: soft,transcoder kernel: i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun: soft,transcoder, [Fix] Fix has been landed on linux-next, 4fe7907f3775(drm/i915/display/adlp: Disable underrun recovery). Defeature the underrun feature for intel display gen13+. [Test Case] 1. change resolution to 3840x2400 2. monitor works well and doesn't black out. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876684] Re: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed
** Tags added: sru-20211129 ** Also affects: linux (Ubuntu Xenial) 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/1876684 Title: fanotify09 case 3 (Events on files and dirs with both inode and mount marks) from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux source package in Bionic: New Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: This is a new test case added 7 days ago [1] Test failed on Focal 5.4.0-29.33 with: fanotify09.c:150: FAIL: group 1 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint fanotify09.c:150: FAIL: group 2 got event: mask 10 pid=41059 fd=24 path=/tmp/ltp-sL4wPwoPJ3/AuNN9M/mntpoint [1] https://github.com/linux-test-project/ltp/commit/70ca1e8806d227d47c6801262d3f7983652159a4#diff-234c27c769cf07468a81748a0e7330dd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1876684/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed on T-aws-4.4
** Summary changed: - fanotify06 from ubuntu_ltp_syscalls failed + fanotify06 from ubuntu_ltp_syscalls failed on T-aws-4.4 ** Tags added: sru-20211129 -- 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/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed on T-aws-4.4 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Mon Jun 17 04:40:18 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial
[Kernel-packages] [Bug 1954956] Re: [amdgpu] System crash
Thanks for the bug report. It looks like the amdgpu kernel driver is crashing and experiencing other problems. Can you please try: * The official Ubuntu kernel * https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ** Summary changed: - Xorg crash + [amdgpu] System crash ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: amdgpu -- 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/1954956 Title: [amdgpu] System crash Status in linux package in Ubuntu: Incomplete Bug description: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954956/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954911] Re: Xorg freeze
Thanks for the bug report. Please: 1. Reboot, plug in the monitor and reproduce the bug again; a failed boot or system freeze. 2. Wait 10 seconds while it is frozen. 3. Power off the machine. 4. Unplug the monitor. 5. Boot the machine normally. 6. Run this command: journalctl -b-1 > prevboot.txt 7. Attach the resulting text file here. ** Summary changed: - Xorg freeze + [i915] [penyrn] System freeze when HDMI is plugged in ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - [i915] [penyrn] System freeze when HDMI is plugged in + [i915] [penryn] System freeze when HDMI is plugged in -- 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/1954911 Title: [i915] [penryn] System freeze when HDMI is plugged in Status in linux package in Ubuntu: Confirmed Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954911] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954911 Title: [i915] [penryn] System freeze when HDMI is plugged in Status in linux package in Ubuntu: Confirmed Bug description: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954956] [NEW] [amdgpu] System crash
You have been subscribed to a public bug: System crashes about 3 times a day; no appearant relation to application or process or triggering situation. Happens constantly. Random time between incidents normally several hours. This is a problem for month now. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 Uname: Linux 5.14.0-051400drmtip20210904-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Wed Dec 15 23:01:59 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: vhba, 20211023, 5.11.0-42-generic, x86_64: installed vhba, 20211023, 5.11.0-44-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c8) (prog-if 00 [VGA controller]) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] InstallationDate: Installed on 2020-12-16 (364 days ago) InstallationMedia: Ubuntu 16.04.7 LTS "Xenial Xerus" - Release amd64 (20200806) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: LANGUAGE=de_DE TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.14.0-051400drmtip20210904-generic root=UUID=54c9f67c-180d-4545-8531-aef138dc5e0a ro SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) XorgConf: Section "InputClass" Identifier "middle button emulation class" MatchIsPointer "on" Option "Emulate3Buttons" "on" EndSection dmi.bios.date: 06/18/2020 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P4.20 dmi.board.name: B450 Pro4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP4.20:bd06/18/2020:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:rvnASRock:rnB450Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. mtime.conffile..etc.apport.crashdb.conf: 2021-08-13T12:52:00.669929 version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4 version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 xserver.bootTime: Wed Dec 15 15:19:50 2021 xserver.configfile: /etc/X11/xorg.conf xserver.errors: AMDGPU(0): Failed to make import prime FD as pixmap: 22 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.11-1ubuntu1.2 xserver.video_driver: amdgpu ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug crash hirsute third-party-packages ubuntu -- [amdgpu] System crash https://bugs.launchpad.net/bugs/1954956 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954911] [NEW] [i915] [penyrn] System freeze when HDMI is plugged in
You have been subscribed to a public bug: When I try to hookup my laptop to a smart TV using an HDMI it will not boot up at all. With my laptop running after booting normally and I plugin the HDMI cable it freeze up and the only way to unfreeze it is to hold the power down until it shuts off. I've done this at least twice maybe three times. Its like there is not an HDMI driver installed. I have been a computer tech since 1984 but as you know learning a new operating system is very time consuming. I started with Dr. DOS 6.0 and it was a great OP System but than of course MicroShaft but them out of business then I finally had to go to MS DOS 4.0 and its been down hill ever since. I'm 64 and working my way into Linux. Any ideas would be great ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 Uname: Linux 5.4.0-66-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_5_4_0_66_74_generic_81 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 05:09:06 2021 DistUpgraded: 2020-12-17 01:37:02,155 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes GpuHangFrequency: This is the first time GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] Subsystem: Sony Corporation Mobile 4 Series Chipset Integrated Graphics Controller [104d:9035] MachineType: Sony Corporation VGN-FW351J ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-12-17 (363 days ago) dmi.bios.date: 11/07/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R2050Y0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR2050Y0:bd11/07/2008:svnSonyCorporation:pnVGN-FW351J:pvrC60184W1:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.family: N/A dmi.product.name: VGN-FW351J dmi.product.sku: N/A dmi.product.version: C60184W1 dmi.sys.vendor: Sony Corporation version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze ubuntu -- [i915] [penyrn] System freeze when HDMI is plugged in https://bugs.launchpad.net/bugs/1954911 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953223] Re: USB device is not detected during boot, again
Try kernel parameter "nomodeset". -- 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/1953223 Title: USB device is not detected during boot, again Status in linux package in Ubuntu: Confirmed Bug description: I have an ethernet adapter (ASIX Electronics Corp. AX88179 Gigabit Ethernet) attached to a USB-C port of my laptop. After update to kernel 5.4.0-90-generic it stopped working again. Same problem with 5.4.0-91-generic. Detaching and reattaching the adapter doesn't help, but after suspend and resume it starts working again, until the next boot. I had the same problem earlier and it was fixed here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1939638 , but the bug got reintroduced in kernel 5.4.0-90-generic most likely due to this patch: * Fix cold plugged USB device on certain PCIe USB cards (LP: #1945211) - Revert "UBUNTU: SAUCE: Revert "usb: core: reduce power-on-good delay time of root hub"" I'm running Ubuntu 20.04. USB2 ports work without problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-91-generic 5.4.0-91.102 ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151 Uname: Linux 5.4.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jttoivon 2745 F pipewire-media- /dev/snd/controlC0: jttoivon 2745 F pipewire-media- /dev/snd/seq:jttoivon 2744 F pipewire CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Sat Dec 4 12:46:18 2021 InstallationDate: Installed on 2020-01-23 (680 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: HP HP ZBook Studio G5 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-91-generic root=UUID=c6b19f0f-68ff-4d8c-985a-c3ed88345389 ro quiet splash resume=UUID=f25913ea-6478-45dc-8f64-ea5d721a8f25 vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-91-generic N/A linux-backports-modules-5.4.0-91-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2021 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.16.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.4C.00 dmi.chassis.asset.tag: 5CD9495R4G dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.16.00:bd04/22/2021:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.4C.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2ZC51EA#AK8 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953223/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1900388] Re: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
kernel: blk_update_request: I/O error, dev sr0, sector 661504 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 kernel: Buffer I/O error on dev sr0, logical block 82688, async page read Description:Ubuntu 20.04.3 LTS Release:20.04 Machine: Type: Desktop Mobo: Micro-Star model: MPG B550 GAMING EDGE WIFI (MS-7C91) v: 1.0 serial: UEFI: American Megatrends LLC. v: 1.70 date: 06/29/2021 Drive: /dev/sr0 Vendor : ASUS Model : DRW-24F1ST d Revision: 2.00 -- 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/1900388 Title: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 Status in linux package in Ubuntu: Confirmed Bug description: blk_update_request: I/O error, dev sr0, sector 9180400 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 PIONEER BD-RW BDR-205 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-23-generic 5.8.0-23.24 ProcVersionSignature: Ubuntu 5.8.0-23.24-generic 5.8.14 Uname: Linux 5.8.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: navycat2032 F pulseaudio /dev/snd/controlC0: navycat2032 F pulseaudio /dev/snd/controlC1: navycat2032 F pulseaudio CasperMD5CheckResult: skip Date: Mon Oct 19 10:11:53 2020 InstallationDate: Installed on 2020-10-07 (11 days ago) InstallationMedia: Ubuntu-MATE 20.10 "Groovy Gorilla" - Beta amd64 (20201007) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: BASE_BOARD_MANUFACTURER MODEL_NAME ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-23-generic root=UUID=98343bbf-e244-4e6d-889d-fa14ff0254ed 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. RelatedPackageVersions: linux-restricted-modules-5.8.0-23-generic N/A linux-backports-modules-5.8.0-23-generic N/A linux-firmware1.190 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 150-SE-E789 dmi.board.vendor: EVGA dmi.board.version: Patsburg dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd04/09/2018:br4.6:svnBASE_BOARD_MANUFACTURER:pnMODEL_NAME:pvrBASE_BOARD_VERSION:rvnEVGA:rn150-SE-E789:rvrPatsburg: dmi.product.family: X86 AT dmi.product.name: MODEL_NAME dmi.product.sku: PROJECT_SUB_TAG dmi.product.version: BASE_BOARD_VERSION dmi.sys.vendor: BASE_BOARD_MANUFACTURER To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1900388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950903] Re: kernel package does not build nvme-tcp module
** Changed in: linux-aws (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1950903 Title: kernel package does not build nvme-tcp module Status in linux-aws package in Ubuntu: Confirmed Status in linux-aws source package in Focal: Confirmed Status in linux-aws source package in Hirsute: Confirmed Status in linux-aws source package in Impish: Confirmed Status in linux-aws source package in Jammy: Confirmed Bug description: linux-image-5.4.0-1059-aws does not build nvme-tcp kernel module so there is no option to use it. The fix is trivial, just add CONFIG_NVME_TCP=m in the kernel config file used to build the kernel image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1950903/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
Hi Sujith, which exact Marvell card is being used here. We only see a reference to QL41000 but need to know which exact card is in use. ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Incomplete Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950778] Re: Ubuntu 20.04.3 generates IO error message during FIO stress.
** 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/1950778 Title: Ubuntu 20.04.3 generates IO error message during FIO stress. Status in linux package in Ubuntu: Confirmed Bug description: With fio stress on Powerstore fcoe drives (lun) attached by using Qlogic QL41000 series controller, ubuntu 20.04.3 on MX740c blade server generates below mentioned i/o errors. Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1523]:13: Error detection CQE, xid=0x7bd Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1525]:13: err_warn_bitmap=0040: Nov 11 20:25:17 e2e-l10-058234 kernel: [:3b:00.3]:[qedf_process_error_detect:1529]:13: tx_buff_off=, rx_buff_off=, rx_id=041b Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1523]:3: Error detection CQE, xid=0x34d Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1525]:3: err_warn_bitmap=0040: Nov 11 20:25:19 e2e-l10-058234 kernel: [:3b:00.2]:[qedf_process_error_detect:1529]:3: tx_buff_off=, rx_buff_off=, rx_id=01f7 Steps to reproduce. 1. Configure QL41000 series controller on MX MX740c blade server. 2. Configure APM3246 array directly connected to chassis module MX9116n. 3. Install Ubuntu 20.04.3 in any local drive. 4. start I/O by using fio : # fio FileSystemCreateSingle/fio_test.cfg then we can observe error message in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1950778/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954938] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1954938 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Impish) Status: New => Incomplete -- 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/1954938 Title: Include the QCA WCN 6856 v2.1 support - WIFI 6 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954938] [NEW] Include the QCA WCN 6856 v2.1 support - WIFI 6
Public bug reported: TBD. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Affects: linux (Ubuntu Impish) Importance: Undecided Status: Incomplete ** Affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Incomplete ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: hwe-bluetooth hwe-firmware hwe-networking-wifi oem-priority originate-from-1945154 somerville ** Tags added: hwe-bluetooth hwe-firmware hwe-networking-wifi ** Tags added: oem-priority originate-from-1945154 somerville ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => 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/1954938 Title: Include the QCA WCN 6856 v2.1 support - WIFI 6 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Incomplete Status in linux-firmware source package in Impish: New Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: Incomplete Status in linux-firmware source package in Jammy: New Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: TBD. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
SRU: https://lists.ubuntu.com/archives/kernel-
team/2021-December/126645.html (oem-5.14/impish/jammy)
** Description changed:
+ [SRU Justification]
+
+ [Impact]
+
+ Detailed in https://gitlab.freedesktop.org/drm/amd/-/issues/1708, taking
+ some cpu cores offline using cpufreq gadgets or via sysfs may hang the
+ system.
+
+ [Fix]
+
+ In v5.16-rc1 commit d6b88ce2eb9d ("ACPI: processor idle: Allow playing
+ dead in C3 state") fixes this issue.
+
+ [Test Case]
+
+ As stated in aforementioned bug url, setup cpufreq extention to take
+ down a few cpu cores, and trigger system suspend. There are ~50% chances
+ that networking/input/... would hang and the user can only reboot by
+ sysrq keys.
+
+ [Where problems could occur]
+
+ According to the patch discussion thread in
+ https://lore.kernel.org/linux-acpi/20210922133116.102-1-richard.g...@amd.com/,
+ the limitation to allow enter_dead in no more than ACPI_STATE_C2 might
+ not have a practical meaning, but simply C2 was the deepest supported
+ then.
+
+ [Other Info]
+
+ While this is currently only available in v5.16-rc1 and affects AMD
+ Cezanne/Barcelo, oem-5.14/impish and jammy are nominated.
+
+ == original bug report ==
+
https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Reproduce steps:
1. Install cpufeq gnome extension
(https://extensions.gnome.org/extension/1082/cpufreq/)
2. Click on the cpu freq extention in the top bar
3. Slide the "cores online" from 16 to 3
4. close lid of laptop
Expected result: the laptop goes into suspend
Actual result: the laptop stay on but screen is now always black and keyboard
input is ignored
Fix committed to v5.16-rc1:
https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1
- ---
+ ---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.20
Architecture: amd64
AudioDevicesInUse:
- USERPID ACCESS COMMAND
- /dev/snd/controlC1: ubuntu 1188 F pulseaudio
- /dev/snd/controlC2: ubuntu 1188 F pulseaudio
- /dev/snd/controlC0: ubuntu 1188 F pulseaudio
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: ubuntu 1188 F pulseaudio
+ /dev/snd/controlC2: ubuntu 1188 F pulseaudio
+ /dev/snd/controlC0: ubuntu 1188 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
-
+
DistributionChannelDescriptor:
- # This is the distribution channel descriptor for the OEM CDs
- # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
- canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
+ canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-09-09 (97 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
- lono wireless extensions.
-
- enp1s0f0 no wireless extensions.
+ lono wireless extensions.
+
+ enp1s0f0 no wireless extensions.
Lsusb:
- Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
- Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
- Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE
+ Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+ Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: AMD Celadon-CZN
Package: linux-firmware 1.187.23+staging.38 [origin:
LP-PPA-canonical-hwe-team-linux-firmware-staging]
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem
root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config
no_console_suspend
ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
- linux-restricted-modules-5.14.0-9011-oem N/A
- linux-backports-modules-5.14.0-9011-oem N/A
- linux-firmware 1.187.23+staging.38
+ linux-restricted-modules-5.14.0-9011-oem N/A
+ linux-backports-modules-5.14.0-9011-oem N/A
+ linux-firmware 1.187.23+staging.38
RfKill:
-
+
Tags: third-party-packages focal
Uname: Linux 5.14.0-9011-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953386 Title: hisi_sas driver may oops in prep_ssp_v3_hw() Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The hisi_sas driver occasionally oopses on boot. [ 32.724666] Unable to handle kernel NULL pointer dereference at virtual address 0110 [ 32.732720] Mem abort info: [ 32.735504] ESR = 0x9604 [ 32.738546] Exception class = DABT (current EL), IL = 32 bits [ 32.70] SET = 0, FnV = 0 [ 32.747482] EA = 0, S1PTW = 0 [ 32.750612] Data abort info: [ 32.753478] ISV = 0, ISS = 0x0004 [ 32.757298] CM = 0, WnR = 0 [ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [ 32.766755] [0110] *pgd= [ 32.771700] Internal error: Oops: 9604 [#1] SMP [ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3 hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x (ptrval)) [ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24 [ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 32.834884] Workqueue: :74:02.0_disco_q sas_discover_domain [libsas] [ 32.839182] hns3 :bd:00.0 enp189s0f0: renamed from eth8 [ 32.841558] pstate: a0c9 (NzCv daif +PAN +UAO) [ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.864354] sp : 21833a00 [ 32.867653] x29: 21833a00 x28: b790728621e0 [ 32.872940] x27: b790728607d8 x26: b79072861158 [ 32.878227] x25: d7b07b9340a0 x24: 0028 [ 32.883515] x23: d7906cd69400 x22: d7906cd69418 [ 32.02] x21: b79072aad3d0 x20: 21b33000 [ 32.894089] x19: b79072aad3d0 x18: 0030 [ 32.899376] x17: 9e710776 x16: 3efb16aabb00 [ 32.904663] x15: x14: 3efb976abcef [ 32.909950] x13: 0006 x12: b79072863480 [ 32.915237] x11: b79072aad3e0 x10: b79072861148 [ 32.920524] x9 : x8 : 24cc0fb0 [ 32.925812] x7 : x6 : 003f [ 32.931099] x5 : 0040 x4 : 20a0 [ 32.936386] x3 : d79071e2d400 x2 : 21833bb4 [ 32.941673] x1 : b79072863460 x0 : 28a0 [ 32.946960] Call trace: [ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main] [ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main] [ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main] [ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas] [ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas] [ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas] [ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas] [ 33.000192] sas_discover_domain+0x340/0x664 [libsas] [ 33.005225] process_one_work+0x1bc/0x3ec [ 33.009217] worker_thread+0x58/0x4a0 [ 33.012863] kthread+0x13c/0x170 [ 33.016077] ret_from_fork+0x10/0x18 [ 33.019638] Code: 2a004820 2a04 f9400ed8 f9410061 (3943a319) [ 33.025705] ---[ end trace da9256b7aa3297ba ]--- [Test Case] Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller. [Fix] e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd [Where things could go wrong] We could potentially be trading one boot time crash for another that hasn't popped up in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1953386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547836/+files/ProcInterrupts.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547839/+files/WifiSyslog.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547837/+files/ProcModules.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547840/+files/acpidump.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547834/+files/ProcCpuinfoMinimal.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547838/+files/UdevDb.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547835/+files/ProcEnviron.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547832/+files/Lsusb-v.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547831/+files/Lsusb-t.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547827/+files/CRDA.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547826/+files/AlsaInfo.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547829/+files/Lspci.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547828/+files/CurrentDmesg.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547833/+files/ProcCpuinfo.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1954930/+attachment/5547830/+files/Lspci-vt.txt -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1188 F pulseaudio /dev/snd/controlC2: ubuntu 1188 F pulseaudio /dev/snd/controlC0: ubuntu 1188 F pulseaudio CasperMD5CheckResult: skip Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-09-09 (97 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IwConfig: lono wireless extensions. enp1s0f0 no wireless extensions. Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: AMD Celadon-CZN Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] PackageArchitecture: all ProcFB: 0 amdgpu ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.14.0-9011-oem N/A linux-backports-modules-5.14.0-9011-oem N/A linux-firmware 1.187.23+staging.38 RfKill: Tags: third-party-packages focal Uname: Linux 5.14.0-9011-oem x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 06/30/2021 dmi.bios.release: 19.1 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: RLD1005B_AB dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Celadon-CZN dmi.board.vendor: AMD dmi.board.version: Base Board Version dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvrRLD1005B_AB:bd06/30/2021:br19.1:svnAMD:pnCeladon-CZN:pvr1:rvnAMD:rnCeladon-CZN:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789: dmi.product.family: Renoir dmi.product.name: Celadon-CZN dmi.product.sku: 123456789 dmi.product.version: 1 dmi.sys.vendor: AMD To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] Re: AMD: Suspend not working when some cores are disabled through cpufreq
[ 123.964355] r8169 :01:00.0 enp1s0f0: Link is Down [ 124.353255] PM: suspend entry (s2idle) [ 124.366348] Filesystems sync: 0.013 seconds [ 124.983434] rfkill: input handler enabled [ 125.062413] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 125.064287] OOM killer disabled. [ 125.064288] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 125.390929] ACPI: EC: interrupt blocked [ 125.469200] ACPI: EC: interrupt unblocked [ 125.510332] pci :00:00.2: can't derive routing for PCI INT A [ 125.510335] pci :00:00.2: PCI INT A: no GSI [ 125.511064] [drm] PCIE GART of 1024M enabled. [ 125.511068] [drm] PTB located at 0x00F40090 [ 125.511083] amdgpu :03:00.0: amdgpu: SMU is resuming... [ 125.512588] amdgpu :03:00.0: amdgpu: dpm has been disabled [ 125.513573] amdgpu :03:00.0: amdgpu: SMU is resumed successfully! [ 125.522694] nvme nvme0: Shutdown timeout set to 10 seconds [ 125.526041] nvme nvme0: 16/0/0 default/read/poll queues [ 125.691534] amdgpu :03:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring sdma0 test failed (-110) [ 125.691698] [drm:amdgpu_device_ip_resume_phase2 [amdgpu]] *ERROR* resume of IP block failed -110 [ 125.691806] amdgpu :03:00.0: amdgpu: amdgpu_device_ip_resume failed (-110). [ 125.691808] PM: dpm_run_callback(): pci_pm_resume+0x0/0x90 returns -110 [ 125.691820] amdgpu :03:00.0: PM: failed to resume async: error -110 [ 125.693966] OOM killer enabled. [ 125.693967] Restarting tasks ... done. [ 125.702960] PM: suspend exit [ 201.335694] sysrq: This sysrq operation is disabled. [ 201.543676] sysrq: This sysrq operation is disabled. [ 201.719682] sysrq: This sysrq operation is disabled. [ 202.231681] sysrq: Emergency Sync [ 202.240025] Emergency Sync complete [ 203.031695] sysrq: Emergency Remount R/O ** Tags added: apport-collected focal third-party-packages ** Description changed: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored - Fix committed to v5.16-rc1: - https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 + Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.20 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: ubuntu 1188 F pulseaudio + /dev/snd/controlC2: ubuntu 1188 F pulseaudio + /dev/snd/controlC0: ubuntu 1188 F pulseaudio + CasperMD5CheckResult: skip + Dependencies: + + DistributionChannelDescriptor: + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X152 + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-09-09 (97 days ago) + InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 + IwConfig: + lono wireless extensions. + + enp1s0f0 no wireless extensions. + Lsusb: + Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 003 Device 002: ID 062a:4c01 MosArt Semiconductor Corp. 2.4G INPUT DEVICE + Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: AMD Celadon-CZN + Package: linux-firmware 1.187.23+staging.38 [origin: LP-PPA-canonical-hwe-team-linux-firmware-staging] + PackageArchitecture: all + ProcFB: 0 amdgpu + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9011-oem root=UUID=668f30b7-78ec-472e-9916-c9b1cbdbbbc6 ro automatic-oem-config no_console_suspend + ProcVersionSignature: Ubuntu 5.14.0-9011.11+staging.37-oem 5.14.20 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-5.14.0-9011-oem N/A + linux-backports-modules-5.14.0-9011-oem N/A + linux-firmware 1.187.23+staging.38 + RfKill: + + Tags: third-party-packages focal + Uname: Linux 5.14.0-9011-oem x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 06/30/2021 + dmi.bios.release: 19.1 + dmi.bios.vendor: INSYDE Corp. +
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Changed in: linux-raspi-5.4 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux-raspi-5.4 (Ubuntu Bionic) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-raspi2 (Ubuntu Bionic) Assignee: (unassigned) => Juerg Haefliger (juergh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi-5.4 package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi-5.4 source package in Bionic: Confirmed Status in linux-raspi2 source package in Bionic: Confirmed Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Status in linux-raspi source package in Impish: Confirmed Bug description: [ Impact ] I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. [ Test Case ] $ sudo dmesg | grep -B1 -A1 'loop: module' [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0 [4.903386] loop: module loaded [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517 [ Fix ] Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8). [ Where Problems Could Occur ] Loop devices need to be created on-demand if more than 8 are required. If that fails, user space will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954931] [NEW] Jammy update: v5.15.8 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.8 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: 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/1954931 Title: Jammy update: v5.15.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed 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.15.8 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954931/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Description changed: + [ Impact ] + I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. + + [ Test Case ] + + $ sudo dmesg | grep -B1 -A1 'loop: module' + [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0 + [4.903386] loop: module loaded + [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517 + + [ Fix ] + + Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8). + + [ Where Problems Could Occur ] + + Loop devices need to be created on-demand if more than 8 are required. + If that fails, user space will fail. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi-5.4 package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi-5.4 source package in Bionic: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Status in linux-raspi source package in Impish: Confirmed Bug description: [ Impact ] I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. [ Test Case ] $ sudo dmesg | grep -B1 -A1 'loop: module' [0.791122] cacheinfo: Unable to detect cache hierarchy for CPU 0 [4.903386] loop: module loaded [4.906092] spi-bcm2835 fe204000.spi: could not get clk: -517 [ Fix ] Set CONFIG_BLK_DEV_LOOP_MIN_COUNT to the default value (8). [ Where Problems Could Occur ] Loop devices need to be created on-demand if more than 8 are required. If that fails, user space will fail. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953008] Re: Support USB4 DP alt mode for AMD Yellow Carp graphics card
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1953008
Title:
Support USB4 DP alt mode for AMD Yellow Carp graphics card
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Committed
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Committed
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
USB4 DP alt mode not available on AMD yellow carp.
[Fix]
Several fixing commits from upstream, inclusive of one titled
"drm/amd/display: Fixup previous PSR policy commit" sauced commit to
fix backport problems for commit 9470620e99e9 ("drm/amd/display: Enable
PSR by default on newer DCN").
This also depends on the firmware updates.
[Test Case]
Plug an external monitor with USB Type-C input function to AMD RMB CRB
(which has yellow carp) usbc0 and usbc1.
[Where problems could occur]
The patches revealed multiple dmub firmware versions were skipped. This
might introduce incompatibilities between driver code and the firmware.
== linux-firmware SRU ==
[Impact]
Need new firmware to enable USB4 DP alt mode for AMD yellow carp.
[Fix]
Already-in-upstream commit 581f8a3aae02 ("amdgpu: update yellow carp
dmcub firmware") to be backported.
[Test Case]
Need also kernel driver fixes to verify.
[Where problems could occur]
This introduces new features required both kernel driver and firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Required linux-firmware:
* 581f8a3a amdgpu: update yellow carp dmcub firmware
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: ubuntu 1304 F pulseaudio
/dev/snd/controlC0: ubuntu 1304 F pulseaudio
CasperMD5CheckResult: skip
Dependencies:
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X173
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2021-12-02 (0 days ago)
InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary
20200502-05:58
IwConfig:
lono wireless extensions.
enp1s0f0 no wireless extensions.
MachineType: AMD LilacKD-RMB
Package: linux-firmware
PackageArchitecture: all
ProcFB: 0 amdgpu
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1008-oem
root=UUID=82b889f1-11ce-4ecf-99e7-65c895cdc771 ro automatic-oem-config
ProcVersionSignature: Ubuntu 5.14.0-1008.8-oem 5.14.17
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-5.14.0-1008-oem N/A
linux-backports-modules-5.14.0-1008-oem N/A
linux-firmware 1.187.20+staging.35
RfKill:
Tags: third-party-packages focal
Uname: Linux 5.14.0-1008-oem x86_64
UnreportableReason: This is not an official Ubuntu package. Please remove any
third party package and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 09/15/2021
dmi.bios.release: 190.196
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: RRL0080C
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: LilacKD-RMB
dmi.board.vendor: AMD
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias:
dmi:bvnINSYDECorp.:bvrRRL0080C:bd09/15/2021:br190.196:svnAMD:pnLilacKD-RMB:pvr1:rvnAMD:rnLilacKD-RMB:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:sku123456789:
dmi.product.family: Rembrandt
dmi.product.name: LilacKD-RMB
dmi.product.sku: 123456789
dmi.product.version: 1
dmi.sys.vendor: AMD
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1953008/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help :
[Kernel-packages] [Bug 1951011] Re: linux-aws: Make a signed kernel
** Also affects: linux-aws (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-aws-hwe (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws-hwe (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-aws-hwe (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-aws-hwe (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws-hwe (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-aws-hwe (Ubuntu Impish) Status: New => Invalid ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal ** Changed in: linux-aws (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Hirsute) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-aws (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux-aws (Ubuntu Impish) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Impish) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws-hwe in Ubuntu. https://bugs.launchpad.net/bugs/1951011 Title: linux-aws: Make a signed kernel Status in linux-aws package in Ubuntu: New Status in linux-aws-hwe package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Invalid Status in linux-aws-hwe source package in Xenial: In Progress Status in linux-aws source package in Bionic: In Progress Status in linux-aws-hwe source package in Bionic: Invalid Status in linux-aws source package in Focal: In Progress Status in linux-aws-hwe source package in Focal: Invalid Status in linux-aws source package in Hirsute: In Progress Status in linux-aws-hwe source package in Hirsute: Invalid Status in linux-aws source package in Impish: In Progress Status in linux-aws-hwe source package in Impish: Invalid Bug description: SRU Justification [Impact] Ubuntu AWS kernels on secure boot instances will not load. [Fix] Generate signed kernels and packages [Test Plan] Boot in a secure boot (UEFI) environment. [Where things could go wrong] This is a new packaging feature. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1951011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954930] [NEW] AMD: Suspend not working when some cores are disabled through cpufreq
Public bug reported: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux (Ubuntu Impish) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: High Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: amd oem-priority originate-from-1954322 ** Tags added: amd oem-priority originate-from-1954322 ** Description changed: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored - Fix committed to v5.15-rc3: + Fix committed to v5.16-rc1: https://github.com/torvalds/linux/commit/d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1 ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Importance: Undecided => High ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => High ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- 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/1954930 Title: AMD: Suspend not working when some cores are disabled through cpufreq 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: In Progress Status in linux source package in Impish: In Progress Status in linux-oem-5.14 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: https://gitlab.freedesktop.org/drm/amd/-/issues/1708 Reproduce steps: 1. Install cpufeq gnome extension (https://extensions.gnome.org/extension/1082/cpufreq/) 2. Click on the cpu freq extention in the top bar 3. Slide the "cores online" from 16 to 3 4. close lid of laptop Expected result: the laptop goes into suspend Actual result: the laptop stay on but screen is now always black and keyboard input is ignored Fix committed to v5.16-rc1:
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
** Changed in: ubuntu-z-systems
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
Fix Committed
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix 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
than the current limit of 12K.
Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1948807] Re: Boot time from snap in 20/stable increases boot time on 3.5 seconds
** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Bionic) ** No longer affects: linux-raspi2 (Ubuntu Focal) ** No longer affects: linux-raspi2 (Ubuntu Hirsute) ** No longer affects: linux-raspi2 (Ubuntu Impish) ** Also affects: linux-raspi-5.4 (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-raspi2 (Ubuntu Bionic) ** Also affects: linux-raspi2 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-raspi-5.4 (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1948807 Title: Boot time from snap in 20/stable increases boot time on 3.5 seconds Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi-5.4 package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi-5.4 source package in Bionic: New Status in linux-raspi2 source package in Bionic: New Status in linux-raspi source package in Focal: Confirmed Status in linux-raspi source package in Hirsute: Confirmed Status in linux-raspi source package in Impish: Confirmed Bug description: I am seeing what looks as a regression in pi-kernel snap for UC20: there are around 3.5 additional seconds spent in boot time. In the image from cdimage (2021-06-30), I see: [1.856540] random: crng init done [1.871798] loop: module loaded (see https://paste.ubuntu.com/p/CkfWXY5Vgf/) while if I build an image from latest snaps in the 20/stable channel, I get: [1.855481] random: crng init done [5.349491] loop: module loaded (see https://paste.ubuntu.com/p/CNt42gdDcZ/) The pi-kernel snap revision is 353. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1948807/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags removed: focal ** Tags added: bot-stop-nagging ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Changed in: linux-azure (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux-azure (Ubuntu) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1954926 Title: Focal: CIFS stable updates Status in linux-azure package in Ubuntu: In Progress 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-azure/+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 1954924] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc drm_vram_helper i2c_algo_bit ib_uverbs nvmet_fc
[Kernel-packages] [Bug 1954924] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547805/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547811/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear
[Kernel-packages] [Bug 1954924] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547808/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547815/+files/acpidump.txt ** Description changed: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. + Env specs: + Ubuntu-Server 20.04.3 LTS + Kernel: 5.4.0-89-generic + CPU: AMD EPYC 7H12 + At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. - Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc drm_vram_helper i2c_algo_bit ib_uverbs nvmet_fc crct10dif_pclmul ib_core crc32_pclmul ttm ghash_clmulni_intel drm_kms_helper aesni_intel nvmet syscopyarea crypto_simd sysfillrect cryptd nvme_fc glue_helper sysimgblt nvme_fabrics ahci fb_sys_fops
[Kernel-packages] [Bug 1954924] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547813/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix 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
than the current limit of 12K.
Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1
To manage notifications
[Kernel-packages] [Bug 1954924] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547812/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1954924] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547814/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547806/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547809/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath
[Kernel-packages] [Bug 1954924] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547810/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1954924] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547807/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547802/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547804/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc
[Kernel-packages] [Bug 1954924] [NEW] Kernel 5.4 - general protection fault SMP NOPTI
Public bug reported: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib lpfc drm_vram_helper i2c_algo_bit ib_uverbs nvmet_fc crct10dif_pclmul ib_core crc32_pclmul ttm ghash_clmulni_intel drm_kms_helper aesni_intel nvmet syscopyarea crypto_simd sysfillrect cryptd nvme_fc glue_helper sysimgblt nvme_fabrics ahci fb_sys_fops mlx5_core tg3 libahci nvme_core pci_hyperv_intf drm tls scsi_transport_fc mlxfw megaraid_sas i2c_piix4 wmi [1673239.664974] ---[ end trace b20e1996a1c8240d ]--- ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags:
[Kernel-packages] [Bug 1954924] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1954924/+attachment/5547803/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954924 Title: Kernel 5.4 - general protection fault SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: Setup is comprised of multiple compute nodes in an OpenStack setup, all nodes being connected to a SAN storage through FC. Env specs: Ubuntu-Server 20.04.3 LTS Kernel: 5.4.0-89-generic CPU: AMD EPYC 7H12 At random times we observe the nodes getting locked up, system load is increasing and no actions can be taken, leading to having to reboot the server to recover. There is no pattern in this and stress testing the servers does not reproduce this. Log snippet: [1673239.174269] general protection fault: [#1] SMP NOPTI [1673239.183446] CPU: 97 PID: 1224718 Comm: cadvisor Not tainted 5.4.0-89-generic #100-Ubuntu [1673239.192622] Hardware name: Dell Inc. PowerEdge R7525/0590KW, BIOS 2.3.6 07/06/2021 [1673239.203336] RIP: 0010:string_nocheck+0x38/0x60 [1673239.212811] Code: 66 85 c0 74 3e 83 e8 01 4c 8d 5c 07 01 31 c0 eb 19 49 39 fa 76 03 44 88 07 48 83 c7 01 41 8d 71 01 48 83 c0 01 4c 39 df 74 0f <44> 0f b6 04 02 41 89 c1 89 c6 45 84 c0 75 d8 4c 89 d2 e8 11 ff ff [1673239.232904] RSP: 0018:a25f3199fba0 EFLAGS: 00010046 [1673239.244331] RAX: RBX: a25f3199fc58 RCX: 0a00ff04 [1673239.256551] RDX: d969688991a5a25c RSI: 8de32b56 RDI: 8de32b5400c6 [1673239.269226] RBP: a25f3199fba0 R08: 9c445a00 R09: 000a [1673239.279111] R10: 8de32b56 R11: 8de42b5400c5 R12: 8de32b56 [1673239.289855] R13: d969688991a5a25c R14: 0a00ff04 R15: 8de32b5400c6 [1673239.299447] FS: 7f925a7fc700() GS:8df87f44() knlGS: [1673239.308670] CS: 0010 DS: ES: CR0: 80050033 [1673239.317988] CR2: 7f9012efcfb8 CR3: 007fa1abe000 CR4: 00340ee0 [1673239.327377] Call Trace: [1673239.337796] string+0x4a/0x60 [1673239.347948] vsnprintf+0x26f/0x4e0 [1673239.356909] seq_vprintf+0x35/0x50 [1673239.365819] seq_printf+0x53/0x70 [1673239.374919] __blkg_prfill_rwstat+0x5d/0xb0 [1673239.383362] blkg_prfill_rwstat_field+0x97/0xc0 [1673239.391580] blkcg_print_blkgs+0xba/0xf0 [1673239.399891] ? blkg_prfill_rwstat+0xc0/0xc0 [1673239.408266] blkg_print_stat_bytes+0x45/0x50 [1673239.416378] cgroup_seqfile_show+0x56/0xc0 [1673239.424336] kernfs_seq_show+0x27/0x30 [1673239.432208] seq_read+0xdc/0x490 [1673239.440065] kernfs_fop_read+0x35/0x1b0 [1673239.448107] __vfs_read+0x1b/0x40 [1673239.456329] vfs_read+0xab/0x160 [1673239.465529] ksys_read+0x67/0xe0 [1673239.473872] __x64_sys_read+0x1a/0x20 [1673239.481269] do_syscall_64+0x57/0x190 [1673239.488798] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [1673239.497445] RIP: 0033:0x4cc910 [1673239.504694] Code: 8b 7c 24 10 48 8b 74 24 18 48 8b 54 24 20 49 c7 c2 00 00 00 00 49 c7 c0 00 00 00 00 49 c7 c1 00 00 00 00 48 8b 44 24 08 0f 05 <48> 3d 01 f0 ff ff 76 20 48 c7 44 24 28 ff ff ff ff 48 c7 44 24 30 [1673239.519380] RSP: 002b:00c01dd1e7a0 EFLAGS: 0202 ORIG_RAX: [1673239.526527] RAX: ffda RBX: 00c46f00 RCX: 004cc910 [1673239.534890] RDX: 1000 RSI: 00c00c2cd000 RDI: 000e [1673239.542958] RBP: 00c01dd1e7f0 R08: R09: [1673239.549915] R10: R11: 0202 R12: [1673239.558350] R13: 0002 R14: 0001 R15: 0002 [1673239.565178] Modules linked in: veth vhost_net nf_conntrack_netlink vhost tap dm_queue_length cls_u32 sch_cbq xsk_diag udp_diag raw_diag unix_diag af_packet_diag tcp_diag inet_diag netlink_diag ebtable_filter ebtables sch_ingress geneve ip6_udp_tunnel udp_tunnel nfnetlink_cttimeout nfnetlink aufs overlay rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache bonding ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 xt_tcpudp xt_comment xt_state xt_conntrack iptable_filter bpfilter nls_iso8859_1 scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_ssif amd64_edac_mod edac_mce_amd dell_smbios kvm_amd dcdbas kvm wmi_bmof dell_wmi_descriptor ccp k10temp ipmi_si ipmi_devintf ipmi_msghandler acpi_power_meter mac_hid sch_fq_codel tcp_bbr openvswitch nsh nf_conncount nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 msr dm_multipath br_netfilter bridge stp llc sunrpc ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq [1673239.565265] async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib
[Kernel-packages] [Bug 1954926] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1954926 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: 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/1954926 Title: Focal: CIFS stable updates Status in linux-azure package in Ubuntu: In Progress 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-azure/+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 1954926] [NEW] Focal: CIFS stable updates
Public bug reported: 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 ** Affects: linux-azure (Ubuntu) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Tags: bot-stop-nagging -- 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/1954926 Title: Focal: CIFS stable updates Status in linux-azure package in Ubuntu: In Progress 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-azure/+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 1954680] Re: zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to Ubuntu 20.04)
** Information type changed from Private 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/1954680
Title:
zcrypt DD: Toleration for new IBM Z Crypto Hardware - (Backport to
Ubuntu 20.04)
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Status in linux source package in Hirsute:
In Progress
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
than the current limit of 12K.
Upstream-ID: bd39654a2282c1a51c044575a6bc00d641d5dfd1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1954680/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1953334] Re: [UBUNTU 20.04] KVM hardware diagnose data improvements for guest kernel - kernel part
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Hirsute)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1953334
Title:
[UBUNTU 20.04] KVM hardware diagnose data improvements for guest
kernel - kernel part
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
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 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 covers the qemu/KVM bits.
__
[Kernel-packages] [Bug 1896420] Re: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1896420 Title: seccomp_bpf in seccomp from ubuntu_kernel_selftests failed to build on B-5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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 1954773] Re: New fix for jack detection after resume on CS8409 sound driver
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954773
Title:
New fix for jack detection after resume on CS8409 sound driver
Status in HWE Next:
New
Status in linux package in Ubuntu:
Incomplete
Status in linux-oem-5.14 package in Ubuntu:
New
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.14 source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux-oem-5.14 source package in Impish:
Invalid
Bug description:
[SRU Justification]
[Impact]
On some platforms with Cirrus CS8409 audio codec, the external headset will
fail to be detected after system resume.
[Fix]
Cirrus released a new fix commit 65cc4ad62a9e ('ALSA: hda/cs8409: Set PMSG_ON
earlier inside cs8409 driver'). It sets the power_state to ON before the
unsolicited event arrives to make sure the jack detection can be invoked after
resume.
[Test]
Plug-in an external headset in front headset port, suspend/resume the system
then check whether the headset function works as expected.
[Where problem could occur]
Low. It only affect the platforms with Cirrus codec CS8409 which used to have
problem.
== Original Bug Description ==
[Summary] System can't detect external headset after suspend
[Steps to reproduce]
1. install manifest and boot into OS
2. plug-in an external headset in front headset port
3. un-plug external headset
4. suspend system
5. resume system from suspend
6. plug-in an external headset
[Expected result]
System could detect external headset after suspend
[Actual result]
System can't detect external headset after suspend
[Failure rate]
3/3
[Additional information]
CID: 202110-29567
SKU: DLPV-SFF-DVT-C1
Image: canonical-oem-somerville-focal-amd64-20200502-85+fossa-davos-adl+X152
system-manufacturer: Dell Inc.
system-product-name: Vostro 3710
bios-version: 0.13.73
CPU: 12th Gen Intel(R) Core(TM) i7-12700 (20x)
GPU: :00:02.0 VGA compatible controller [0300]: Intel Corporation Device
[8086:4680] (rev 0c)
kernel-version: 5.13.0-1019-oem
[Stage]
Issue reported and logs collected right after it happened
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954773/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954300] Re: mt7921e: Failed to start WM firmware
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
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-firmware source package in Focal:
In Progress
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
In Progress
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:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e :03:00.0: WM Firmware Version: 01, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e :03:00.0: Message 8002 (seq 9) timeout
mt7921e :03:00.0: Failed to start WM firmware
mt7921e: probe of :03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ checkbox-cli run com.canonical.certification::stress/reboot
[Where problems could occur]
This imports fixes requiring both kernel driver and proprietary firmware
updates, the firmware part might cause instability or so.
== original bug report ==
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e :03:00.0: WM Firmware
Version: 01, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 :02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e :03:00.0: Message 8002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e :03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of :03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954633] Re: s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
** Changed in: linux (Ubuntu Impish)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954633
Title:
s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
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 source package in Focal:
Invalid
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-oem-5.13 source package in Hirsute:
Invalid
Status in linux-oem-5.14 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
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:
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:
[SRU Justification]
[Impact]
AMD Ryzen 7 platforms fail to s2idle when powered by bettery.
[Fix]
Upstream fix commit 49201b90af81 ("platform/x86: amd-pmc: Fix s2idle
failures on certain AMD laptops") from v5.16-rc5.
[Test Case]
Run checkbox suspend/resume tests on battey:
$ checkbox-cli run \
com.canonical.certification::stress-suspend-30-cycles-with-reboots-automated
[Where problems could occur]
This shortens AMD PMC communication poll delay to a half of the original
value. While we don't have much information about the exact value range
allowed, the side effect couldn't be evaluated practically. This change
was ACKed by AMD developers and has been marked cc stable, we'll
probably bump into it anyway.
[Other Info]
This may affect kernel >= 5.11. While Hirsute is near its EOL, it was
skipped here.
== original bug report ==
kernel: amd_pmc AMDI0005:00: SMU response timed out
kernel: amd_pmc AMDI0005:00: suspend failed
kernel: PM: dpm_run_callback(): acpi_subsys_suspend_noirq+0x0/0x50 returns
-110
kernel: amd_pmc AMDI0005:00: PM: failed to suspend noirq: error -110
kernel: PM: noirq suspend of devices failed
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954633/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954646] Re: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954646 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Fix pci port lost when hotplug dock Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: New Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.13 source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] On Intel Maple Ridge, when hotplug TBT4 dock, PCIe bus show error "severity=Uncorrected (Non-Fatal)", and failed to probe. [Fix] Re-enable PCIe port LTR after reset or hotplug, and probe it properly. [Test] Verified on HW with TBT4 dock. it works fine. Also tested Tiger Lake-LP Thunderbolt 4, tbt4 dock works fine. Tested on AMD Cezanne, PCIe works fine, it doesn't support thunderbolt. [Where problems could occur] PCI bus may break. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954646/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945590] Re: Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
** Changed in: linux (Ubuntu Impish)
Status: Confirmed => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1945590
Title:
Thinkpad E14 Gen2: Kernel panic with trackpad and trackpoint enabled
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
Confirmed
Bug description:
[Impact]
On some thinkpads we may get a kernel panic at boot, because the
elantech driver (trakcpad) can trigger out-of-bounds access in the
stack.
[Test case]
Simply boot the kernel on one of the affected systems (e.g., Thinkpad
E14 Gen2).
[Fix]
Prevent the stack out of bound access by applying the following
upstream commit (from linux-next):
1d72d9f960cc ("Input: elantech - fix stack out of bound access in
elantech_change_report_id()")
[Regression potential]
The fix is touching the elantech driver, so we could only see
regressions with this specific trackpad/mouse driver.
[Original bug report]
I installed the Ubuntu 21.10 beta and as soon as I boot I get the
kernel panic that I am attaching.
I also installed Ubuntu 21.04 and upgraded, as soon as I boot with the
5.13 kernel I get the same problem, disabling the trackpad and
trackpoint in the bios the problem disappears.
Everything works with the 5.11 kernel.
I remain available for further details and sorry for my lack of experience.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: linux-image-5.13.0-16-generic 5.13.0-16.16
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: pietro 1810 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 30 10:26:10 2021
InstallationDate: Installed on 2021-09-29 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: LENOVO 20TA0033IX
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-16-generic
root=UUID=b5ea9465-4cd9-408b-8e30-458acf90181b ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.13.0-16-generic N/A
linux-backports-modules-5.13.0-16-generic N/A
linux-firmware 1.201
SourcePackage: linux
UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago)
dmi.bios.date: 09/02/2021
dmi.bios.release: 1.43
dmi.bios.vendor: LENOVO
dmi.bios.version: R1EET43W(1.43 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TA0033IX
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.43
dmi.modalias:
dmi:bvnLENOVO:bvrR1EET43W(1.43):bd09/02/2021:br1.43:efr1.43:svnLENOVO:pn20TA0033IX:pvrThinkPadE14Gen2:skuLENOVO_MT_20TA_BU_Think_FM_ThinkPadE14Gen2:rvnLENOVO:rn20TA0033IX:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E14 Gen 2
dmi.product.name: 20TA0033IX
dmi.product.sku: LENOVO_MT_20TA_BU_Think_FM_ThinkPad E14 Gen 2
dmi.product.version: ThinkPad E14 Gen 2
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945590/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1952817] Re: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1952817 Title: [SRU][I/OEM-5.13/OEM-5.14] Fix USB3.1 hotplug after S3 on AMD renoir Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Bug description: [Impact] On new amdgpu renoir firmware, the USB-type-C port is useless when uplug the USB-type-C <-> DP/HDMI/VGA Dongle after the system resumed from S3. [Fix] Restore the old amdgpu fw, this issue is gone. For new fw, AMD make kernel fix be ready, after backport, the issue is not reproduced on new fw. Cherry-picked from stable kernel release to fix it. [Test] After S3 on renoir's platforms, hotplug USB, the USB3.1 devices works good. [Where problems could occur] AMD renoir platform may have issues when suspend. Jammy already got this commit via stable updates v5.15.3 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1952817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1953386 Title: hisi_sas driver may oops in prep_ssp_v3_hw() Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The hisi_sas driver occasionally oopses on boot. [ 32.724666] Unable to handle kernel NULL pointer dereference at virtual address 0110 [ 32.732720] Mem abort info: [ 32.735504] ESR = 0x9604 [ 32.738546] Exception class = DABT (current EL), IL = 32 bits [ 32.70] SET = 0, FnV = 0 [ 32.747482] EA = 0, S1PTW = 0 [ 32.750612] Data abort info: [ 32.753478] ISV = 0, ISS = 0x0004 [ 32.757298] CM = 0, WnR = 0 [ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [ 32.766755] [0110] *pgd= [ 32.771700] Internal error: Oops: 9604 [#1] SMP [ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3 hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x (ptrval)) [ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24 [ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 32.834884] Workqueue: :74:02.0_disco_q sas_discover_domain [libsas] [ 32.839182] hns3 :bd:00.0 enp189s0f0: renamed from eth8 [ 32.841558] pstate: a0c9 (NzCv daif +PAN +UAO) [ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.864354] sp : 21833a00 [ 32.867653] x29: 21833a00 x28: b790728621e0 [ 32.872940] x27: b790728607d8 x26: b79072861158 [ 32.878227] x25: d7b07b9340a0 x24: 0028 [ 32.883515] x23: d7906cd69400 x22: d7906cd69418 [ 32.02] x21: b79072aad3d0 x20: 21b33000 [ 32.894089] x19: b79072aad3d0 x18: 0030 [ 32.899376] x17: 9e710776 x16: 3efb16aabb00 [ 32.904663] x15: x14: 3efb976abcef [ 32.909950] x13: 0006 x12: b79072863480 [ 32.915237] x11: b79072aad3e0 x10: b79072861148 [ 32.920524] x9 : x8 : 24cc0fb0 [ 32.925812] x7 : x6 : 003f [ 32.931099] x5 : 0040 x4 : 20a0 [ 32.936386] x3 : d79071e2d400 x2 : 21833bb4 [ 32.941673] x1 : b79072863460 x0 : 28a0 [ 32.946960] Call trace: [ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main] [ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main] [ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main] [ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas] [ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas] [ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas] [ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas] [ 33.000192] sas_discover_domain+0x340/0x664 [libsas] [ 33.005225] process_one_work+0x1bc/0x3ec [ 33.009217] worker_thread+0x58/0x4a0 [ 33.012863] kthread+0x13c/0x170 [ 33.016077] ret_from_fork+0x10/0x18 [ 33.019638] Code: 2a004820 2a04 f9400ed8 f9410061 (3943a319) [ 33.025705] ---[ end trace da9256b7aa3297ba ]--- [Test Case] Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller. [Fix] e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd [Where things could go wrong] We could potentially be trading one boot time crash for another that hasn't popped up in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1953386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840122] Re: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block
** Tags removed: amd64 apport-bug apport-collected id-5d557981385f317578944153 verification-done verification-done-bionic ** Tags added: rls-jj-incoming -- 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/1840122 Title: System fails to reboot from live session or ubiquity-dm - squashfs_read_data failed to read block Status in subiquity: New Status in casper package in Ubuntu: New Status in finalrd package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Status in casper source package in Bionic: Fix Released Status in finalrd source package in Bionic: New Status in linux source package in Bionic: Confirmed Status in casper source package in Eoan: Fix Released Status in finalrd source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Status in casper source package in Focal: Fix Released Status in finalrd source package in Focal: New Status in linux source package in Focal: New Status in casper source package in Hirsute: New Status in finalrd source package in Hirsute: New Status in linux source package in Hirsute: New Status in casper source package in Impish: New Status in finalrd source package in Impish: New Status in linux source package in Impish: New Status in casper source package in Jammy: New Status in finalrd source package in Jammy: Triaged Status in linux source package in Jammy: Confirmed Bug description: Last known good image: Eoan Ubuntu Desktop 20190715 Similar results started to happen with new linux-hwe kernel based on eoan for 18.04.4 release. Test Case: 1. Boot eoan desktop to a live session 2. Wait a couple of minutes until snapd settles 3. Reboot the system from the system menu or from the command line Expected result: The system reboots Actual result: The systems fails to reboot or shutdown and displays some errors about failing to unmount /cdrom and squashfs errors in a loop. Unmounting /cdrom... [FAILED] Failed unmounting /cdrom. [ OK ] Started Shuts down the "li…" preinstalled system cleanly. [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. [ 115.744188] print_req_error: I/O error, dev sr0, sector 1508872 flags 80700 [ 115.768139] print_req_error: I/O error, dev sr0, sector 1508872 flags 0 [ 115.771469] print_req_error: I/O error, dev loop0, sector 1501550 flags 0 [ 115.775824] SQUASHFS error: squashfs_read_data failed to read block 0x2dd2d998 This also causes daily tests to fail and is reproducible in a VM and bare metal booted in legacy bios mode ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: casper 1.414 ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Uname: Linux 5.2.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 14 08:31:30 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190813) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: casper UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.2.0-10.11-generic 5.2.4 Tags: eoan Uname: Linux 5.2.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.414 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 IwConfig: lono wireless extensions. ens3 no wireless extensions. LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190814) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 qxldrmfb
[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface
** Changed in: linux (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed 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 1947206] Re: Updates to ib_peer_memory requested by Nvidia
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1947206 Title: Updates to ib_peer_memory requested by Nvidia Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Fix Committed 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 1954834] Re: Focal update: v5.4.162 upstream stable release
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1954834
Title:
Focal update: v5.4.162 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
Fix Committed
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.162 upstream stable release
from git://git.kernel.org/
arm64: zynqmp: Do not duplicate flash partition label property
arm64: zynqmp: Fix serial compatible string
ARM: dts: NSP: Fix mpcore, mmc node names
scsi: lpfc: Fix list_add() corruption in lpfc_drain_txq()
arm64: dts: hisilicon: fix arm,sp805 compatible string
RDMA/bnxt_re: Check if the vlan is valid before reporting
usb: musb: tusb6010: check return value after calling platform_get_resource()
usb: typec: tipd: Remove WARN_ON in tps6598x_block_read
arm64: dts: qcom: msm8998: Fix CPU/L2 idle state latency and residency
arm64: dts: freescale: fix arm,sp805 compatible string
ASoC: SOF: Intel: hda-dai: fix potential locking issue
clk: imx: imx6ul: Move csi_sel mux to correct base register
ASoC: nau8824: Add DMI quirk mechanism for active-high jack-detect
scsi: advansys: Fix kernel pointer leak
firmware_loader: fix pre-allocated buf built-in firmware use
ARM: dts: omap: fix gpmc,mux-add-data type
usb: host: ohci-tmio: check return value after calling platform_get_resource()
ARM: dts: ls1021a: move thermal-zones node out of soc/
ARM: dts: ls1021a-tsn: use generic "jedec,spi-nor" compatible for flash
ALSA: ISA: not for M68K
tty: tty_buffer: Fix the softlockup issue in flush_to_ldisc
MIPS: sni: Fix the build
scsi: target: Fix ordered tag handling
scsi: target: Fix alua_tg_pt_gps_count tracking
iio: imu: st_lsm6dsx: Avoid potential array overflow in st_lsm6dsx_set_odr()
powerpc/5200: dts: fix memory node unit name
ALSA: gus: fix null pointer dereference on pointer block
powerpc/dcr: Use cmplwi instead of 3-argument cmpli
sh: check return code of request_irq
maple: fix wrong return value of maple_bus_init().
f2fs: fix up f2fs_lookup tracepoints
sh: fix kconfig unmet dependency warning for FRAME_POINTER
sh: math-emu: drop unused functions
sh: define __BIG_ENDIAN for math-emu
clk: ingenic: Fix bugs with divided dividers
clk/ast2600: Fix soc revision for AHB
clk: qcom: gcc-msm8996: Drop (again) gcc_aggre1_pnoc_ahb_clk
mips: BCM63XX: ensure that CPU_SUPPORTS_32BIT_KERNEL is set
sched/core: Mitigate race cpus_share_cache()/update_top_cache_domain()
tracing: Save normal string variables
tracing/histogram: Do not copy the fixed-size char array field over the field
size
RDMA/netlink: Add __maybe_unused to static inline in C file
perf bpf: Avoid memory leak from perf_env__insert_btf()
perf bench futex: Fix memory leak of perf_cpu_map__new()
perf tests: Remove bash construct from record+zstd_comp_decomp.sh
net: bnx2x: fix variable dereferenced before check
iavf: check for null in iavf_fix_features
iavf: free q_vectors before queues in iavf_disable_vf
iavf: Fix failure to exit out from last all-multicast mode
iavf: prevent accidental free of filter structure
iavf: validate pointers
iavf: Fix for the false positive ASQ/ARQ errors while issuing VF reset
MIPS: generic/yamon-dt: fix uninitialized variable error
mips: bcm63xx: add support for clk_get_parent()
mips: lantiq: add support for clk_get_parent()
platform/x86: hp_accel: Fix an error handling path in 'lis3lv02d_probe()'
scsi: core: sysfs: Fix hang when device state is set via sysfs
net: sched: act_mirred: drop dst for the direction from egress to ingress
net: dpaa2-eth: fix use-after-free in dpaa2_eth_remove
net: virtio_net_hdr_to_skb: count transport header in UFO
i40e: Fix correct max_pkt_size on VF RX queue
i40e: Fix NULL ptr dereference on VSI filter sync
i40e: Fix changing previously set num_queue_pairs for PFs
i40e: Fix ping is lost after configuring ADq on VF
i40e: Fix creation of first queue by omitting it if is not power of two
i40e: Fix display error code in dmesg
NFC: reorganize the functions in nci_request
drm/nouveau: hdmigv100.c: fix corrupted HDMI Vendor InfoFrame
NFC: reorder the logic in nfc_{un,}register_device
KVM: PPC: Book3S HV: Use GLOBAL_TOC for kvmppc_h_set_dabr/xdabr()
perf/x86/intel/uncore: Fix filter_tid mask for CHA events on Skylake Server
[Kernel-packages] [Bug 1954828] Re: Focal update: v5.4.161 upstream stable release
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954828 Title: Focal update: v5.4.161 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed 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.161 upstream stable release from git://git.kernel.org/ scsi: ufs: Fix interrupt error message for shared interrupts MIPS: Fix assembly error from MIPSr2 code used within MIPS_ISA_ARCH_LEVEL ext4: fix lazy initialization next schedule time computation in more granular unit scsi: ufs: Fix tm request when non-fatal error happens fortify: Explicitly disable Clang support parisc/entry: fix trace test in syscall exit path PCI/MSI: Destroy sysfs before freeing entries PCI/MSI: Deal with devices lying about their MSI mask capability PCI: Add MSI masking quirk for Nvidia ION AHCI erofs: remove the occupied parameter from z_erofs_pagevec_enqueue() erofs: fix unsafe pagevec reuse of hooked pclusters Linux 5.4.161 UBUNTU: upstream stable to v5.4.161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954828/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954912] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954912 Title: my touchpad is not working Status in linux package in Ubuntu: Confirmed Bug description: sometimes the touchpad works and sometimes it doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: limon 1499 F pulseaudio /dev/snd/controlC0: limon 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 17:23:02 2021 InstallationDate: Installed on 2020-03-19 (635 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 3546 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=6c58f4cb-8aff-4a3e-9280-258358f605c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-06 (130 days ago) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XP6MW dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn0XP6MW:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3546 dmi.product.sku: 065C 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/1954912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954912] [NEW] my touchpad is not working
Public bug reported: sometimes the touchpad works and sometimes it doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: limon 1499 F pulseaudio /dev/snd/controlC0: limon 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 17:23:02 2021 InstallationDate: Installed on 2020-03-19 (635 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 3546 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=6c58f4cb-8aff-4a3e-9280-258358f605c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-06 (130 days ago) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XP6MW dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn0XP6MW:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3546 dmi.product.sku: 065C dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1954912 Title: my touchpad is not working Status in linux package in Ubuntu: New Bug description: sometimes the touchpad works and sometimes it doesn't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-90-generic 5.4.0-90.101 ProcVersionSignature: Ubuntu 5.4.0-90.101-generic 5.4.148 Uname: Linux 5.4.0-90-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: limon 1499 F pulseaudio /dev/snd/controlC0: limon 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Dec 15 17:23:02 2021 InstallationDate: Installed on 2020-03-19 (635 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Vostro 3546 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-90-generic root=UUID=6c58f4cb-8aff-4a3e-9280-258358f605c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-90-generic N/A linux-backports-modules-5.4.0-90-generic N/A linux-firmware1.187.20 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2021-08-06 (130 days ago) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0XP6MW dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnVostro3546:pvrNotSpecified:rvnDellInc.:rn0XP6MW:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3546 dmi.product.sku: 065C 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/1954912/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954617] Re: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
Tested on a machine that previous have that issue. After install 5.14 1011 oem kernel from focal proposed, then this is fixed. ** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954617 Title: Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) 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: New Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] On ADL platform, I+N sku, get the cpufreq errors during boot-up, [ 1.058427] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19) [ 1.058451] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 1 (-19) [ 1.058469] cpufreq: cpufreq_online: Failed to initialize policy for cpu: 2 (-19) [Fix] Fixed by 46573fd6369f(cpufreq: intel_pstate: hybrid: Rework HWP calibration) The commit has been landed on mainline since v5.15-rc1. [Test Case] 1. boot-up the machine. 2. check dmesg if the cpufreq error is presented. [Where problems could occur] low To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954617/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954612] Re: alsa/hda: the microphone can't be detected on a couple of lenovo machines
tested on a Lenovo M80s with the kernel linux-oem-5.14/5.14.0-1011.11 in focal-proposed, this issue was fixed. ** 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-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1954612 Title: alsa/hda: the microphone can't be detected on a couple of lenovo machines 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 Committed Bug description: [Impact] We plug a microphone in the audio jack, but the driver can't detect the microphone and we try to record sound via this mic, can't record any sound. [Fix] Backport one patch from upstream. [Test] Booting the patched kernel, open the gnome-sound-setting, plug a microphone, we could see the system detect the microphone, and use this mic to record sound, the sound is recorded successfully. [Where problems could occur] The change only applies to the specific machines with those SSIDs, it will not introduce regression on other machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1954612/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949063] Re: Add F81966 watchdog support
This bug was fixed in the package linux-hwe-5.11 - 5.11.0-43.47~20.04.2 --- linux-hwe-5.11 (5.11.0-43.47~20.04.2) focal; urgency=medium * focal/linux-hwe-5.11: 5.11.0-43.47~20.04.2 -proposed tracker (LP: #1954350) * Add F81966 watchdog support (LP: #1949063) - SAUCE: watchdog: f71808e_wdt: Add F81966 support -- Stefan Bader Mon, 13 Dec 2021 11:45:24 +0100 ** Changed in: linux-hwe-5.11 (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1949063 Title: Add F81966 watchdog support Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-hwe-5.11 package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-hwe-5.11 source package in Focal: Fix Released Status in linux-hwe-5.13 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-hwe-5.11 source package in Hirsute: Invalid Status in linux-hwe-5.13 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 Status in linux-hwe-5.13 source package in Impish: Invalid Status in linux source package in Jammy: In Progress Status in linux-hwe-5.11 source package in Jammy: Invalid Status in linux-hwe-5.13 source package in Jammy: Invalid Bug description: [Impact] f71808e_wdt watchdog driver can't recognize F81966 chip. [Fix] AAEON provides a patch to add the ID. https://www.spinics.net/lists/kernel/msg4147351.html [Test] Testing was done on the Aaeon SSE-OPTI [Where problems could occur] Simply adding one ID, should not introduce any regressions. [Misc] This patch is for ODM project and need this to be included as soon as possible, so we submit this patch as a sauce patch before upstream merges it. BTW, Jammy already included this commit when the patch was submitted for the SRU the first time. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1949063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1950868] Re: Display error after reopening notebook top
I have the same error within amdgpu. After closing and reopeing the notebook top, the display is totally distorted. The whole screen is covered with white snowflakes And then i have to change kernel to 5.4.0-91-generic - System:Kernel: 5.4.0-91-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 5.0.7 wm: muffin dm: LightDM Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal Machine: Type: Laptop System: MECHREVO product: S2 Air Series PF4NU1F v: Standard serial: Mobo: MECHREVO model: PF4NU1F v: Standard serial: BIOS: American Megatrends v: N.1.06MRO03 date: 08/04/2020 Battery: ID-1: BAT0 charge: 43.3 Wh condition: 43.3/46.7 Wh (93%) volts: 12.8/11.4 model: standard serial: status: Full CPU: Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64 type: MT MCP arch: Zen rev: 1 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 92626 Speed: 2267 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 2362 2: 2429 3: 2271 4: 2162 5: 4139 6: 4100 7: 3027 8: 2809 9: 2734 10: 2755 11: 2483 12: 2478 13: 3089 14: 3086 15: 3834 16: 3775 Graphics: Device-1: AMD Renoir vendor: Tongfang Hongkong Limited driver: N/A bus ID: 04:00.0 chip ID: 1002:1636 Display: x11 server: X.Org 1.20.13 driver: ati,fbdev unloaded: modesetting,radeon,vesa resolution: 1920x1080~77Hz OpenGL: renderer: llvmpipe (LLVM 12.0.0 256 bits) v: 4.5 Mesa 21.0.3 compat-v: 3.1 direct render: Yes Audio: Device-1: AMD vendor: Tongfang Hongkong Limited driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:1637 Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: Tongfang Hongkong Limited driver: N/A bus ID: 04:00.5 chip ID: 1022:15e2 Device-3: AMD Family 17h HD Audio vendor: Tongfang Hongkong Limited driver: snd_hda_intel v: kernel bus ID: 04:00.6 chip ID: 1022:15e3 Sound Server: ALSA v: k5.4.0-91-generic Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel bus ID: 01:00.0 chip ID: 8086:24fb IF: wlp1s0 state: down mac: Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Tongfang Hongkong Limited driver: r8169 v: kernel port: f000 bus ID: 02:00.0 chip ID: 10ec:8168 IF: eno1 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 476.94 GiB used: 23.53 GiB (4.9%) ID-1: /dev/nvme0n1 vendor: A-Data model: IM2P33F8-512GD size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: Partition: ID-1: / size: 183.08 GiB used: 11.35 GiB (6.2%) fs: ext4 dev: /dev/nvme0n1p1 ID-2: /home size: 280.61 GiB used: 12.19 GiB (4.3%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: swap-1 size: 3.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p3 Sensors: System Temperatures: cpu: 65.9 C mobo: N/A Fan Speeds (RPM): N/A Repos: No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 1: deb http: //mirrors.ustc.edu.cn/linuxmint uma main upstream import backport 2: deb http: //mirrors.huaweicloud.com/repository/ubuntu focal main restricted universe multiverse 3: deb http: //mirrors.huaweicloud.com/repository/ubuntu focal-updates main restricted universe multiverse 4: deb http: //mirrors.huaweicloud.com/repository/ubuntu focal-backports main restricted universe multiverse 5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse 6: deb http: //archive.canonical.com/ubuntu/ focal partner Info: Processes: 327 Uptime: 1h 03m Memory: 15.12 GiB used: 3.09 GiB (20.4%) Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.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/1950868 Title: Display error after reopening notebook top Status in linux package in Ubuntu: Confirmed Bug description: Hi all, I probably experienced an error within amdgpu. After closing and reopeing the notebook top, the display is totally distorted. Switching to a virtual console doesnt help. You may find a screenshot attached. The error came up in recent version (X)Ubuntu 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-22-generic 5.13.0-22.22 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 ApportVersion:
[Kernel-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
Spoken too soon. There's a kernel config option that we might be missing (CONFIG_ROOT_NFS), which seems to pull in code that parses nfsroot kernel commandline options. ** Changed in: linux-raspi (Ubuntu Impish) Status: Invalid => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in linux-raspi package in Ubuntu: Triaged Status in linux-raspi source package in Impish: Triaged Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
@koba nvidia module won't even build against oem kernel 5.14, so I can't test that. Removing i915.enable_psr=0 is not really a supported configuration on this machine. Keeping PSR on causes it to occasionally hard freeze after hours of work. tbh after all this time I've lost any hope of this getting fixed and any will to continue trying different configurations. It must be something very non-trivial if we haven't even been able to pin this down after 8 months of back and forth with all the debug logs switched on, so I am thinking of just ditching this laptop and getting a Mac instead. -- 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/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux-oem-5.13 package in Ubuntu: Won't Fix Status in linux-oem-5.14 package in Ubuntu: Won't Fix Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
There is no powerlimit via RAPL also here. Prochot can be generated by some device on the system. We don't know the source. If some old kernel works it is possible that newer kernel activated some new device which is causing issue. It is also possible that some device is now malfunctioning on the HW. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio
[Kernel-packages] [Bug 1945221] Re: CPU frequency stuck at minimum value..again Ubuntu 20.04.3
-- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1945221 Title: CPU frequency stuck at minimum value..again Ubuntu 20.04.3 Status in thermald package in Ubuntu: In Progress Bug description: I would really like to find out why my cpu's keep reverting back to a cpu powersave mode after I get a kernel update then reboot. I cleaned my laptops vent but this seems to happen whenever a new kernel is updated and installed. https://askubuntu.com/questions/1366090/ubuntu-20-04-3-lts- significant-throttling-of- intel-i7-processor?noredirect=1#comment2345549_1366090 Description:Ubuntu 20.04.3 LTS Release:20.04 Computer Summary Computer Processor Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Memory 16315MB (4407MB used) Machine TypeLaptop Operating SystemUbuntu 20.04.3 LTS User Name rt (rt) Date/Time Mon 30 Aug 2021 02:33:09 PM EDT Display Resolution 1920x1080 pixels OpenGL Renderer Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) X11 Vendor The X.Org Foundation Audio Devices Audio Adapter HDA-Intel - HDA Intel HDMI Audio Adapter HDA-Intel - HDA Intel PCH Audio Adapter USB-Audio - USB Audio Device Input Devices Power Button Sleep Button Lid Switch Power Button AT Translated Set 2 keyboard USB Audio Device ETPS/2 Elantech Touchpad Logitech Anywhere MX Video Bus HDA Intel PCH Mic HDA Intel PCH Front Headphone HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 Printers (CUPS) OfficeJet_Pro_6978 Default SCSI Disks TSSTcorp CDDVDW SN-208DB ATA INTEL SSDMCEAC12 ATA ST1000LM014-1EJ1 Operating System Version Kernel Linux 5.4.0-81-generic (x86_64) Version #91-Ubuntu SMP Thu Jul 15 19:09:17 UTC 2021 C Library GNU C Library / (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31 DistributionUbuntu 20.04.3 LTS Current Session Computer Name sys76 User Name rt (rt) Languageen_US.UTF-8 () Home Directory /home/rt Misc Uptime 20 minutes Load Average0.83, 1.37, 1.62 Available entropy in /dev/random3649 bits (healthy) rt@sys76:~$ dpkg -l *freq* | grep ii rt@sys76:~$ rt@sys76:~$ sudo turbostat --Summary --quiet --show Busy%,Bzy_MHz,PkgTmp,PkgWatt,GFXWatt,IRQ --interval 6 Busy% Bzy_MHz IRQ PkgTmp PkgWatt GFXWatt 2.95800 334747 2.160.01 2.76800 306949 2.150.01 5.85800 512248 2.730.01 11.87 800 800847 3.410.04 8.23800 577847 2.860.05 rt@sys76:~$ lscpu Architecture:x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s):1 Vendor ID: GenuineIntel CPU family: 6 Model: 60 Model name: Intel(R) Core(TM) i7-4700MQ CPU @ 2.40GHz Stepping:3 CPU MHz: 798.103 CPU max MHz: 3400. CPU min MHz: 800. BogoMIPS:4788.65 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache:1 MiB L3 cache:6 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulne rable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitizatio n Vulnerability Spectre v2:Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIB P conditional, RSB filling Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async
[Kernel-packages] [Bug 1954904] [NEW] bpf pointer tainted kaslr leak
*** This bug is a security vulnerability *** Private security bug reported: [Impact] adjust_ptr_min_max_vals will allow a pointer arithmetic with any value, but set the register to a SCALAR, preventing further pointer operations, leading to a pointer leak, aka, KASLR leak. [Potential regression] Any potential fixes will change the verifier, which means that some BPF code that was previously allowed may be prevented to load. It may also lead to other code being allowed that leads to other vulnerabilities. [Test case] Use a privately shared code to test it. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private Security -- 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/1954904 Title: bpf pointer tainted kaslr leak Status in linux package in Ubuntu: New Bug description: [Impact] adjust_ptr_min_max_vals will allow a pointer arithmetic with any value, but set the register to a SCALAR, preventing further pointer operations, leading to a pointer leak, aka, KASLR leak. [Potential regression] Any potential fixes will change the verifier, which means that some BPF code that was previously allowed may be prevented to load. It may also lead to other code being allowed that leads to other vulnerabilities. [Test case] Use a privately shared code to test it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954904/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1954716] Re: rpi nfsroot vers=4 not supported anymore?
** Changed in: linux-raspi (Ubuntu Impish) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1954716 Title: rpi nfsroot vers=4 not supported anymore? Status in linux-raspi package in Ubuntu: Triaged Status in linux-raspi source package in Impish: Invalid Bug description: I'm running `5.13.0-1011-raspi #13-Ubuntu SMP PREEMPT Fri Nov 19 18:40:23 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux` and have successfully set up netbooting on my RPi 4B (4GB). When I do not specify a `vers=` in cmdline.txt, NFS version 3 is used. I'd like to move to version 4, but unlike the setup described in https://forums.raspberrypi.com/viewtopic.php?p=1751741#p1751741, I cannot get `vers=4` (or any sub-version to work): the console logs `invalid value for vers.` for whatever I try. Current working cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp ro ip=dhcp rootwait fixrtc splash ``` Nonworking cmdline.txt: ``` dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1 root=/dev/nfs nfsroot=192.168.3.101:/srv/pinet/root,tcp,vers=4 ro ip=dhcp rootwait fixrtc splash ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1954716/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1953386] Re: hisi_sas driver may oops in prep_ssp_v3_hw()
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- 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/1953386 Title: hisi_sas driver may oops in prep_ssp_v3_hw() Status in kunpeng920: In Progress Status in kunpeng920 ubuntu-18.04 series: In Progress Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: In Progress Bug description: [Impact] The hisi_sas driver occasionally oopses on boot. [ 32.724666] Unable to handle kernel NULL pointer dereference at virtual address 0110 [ 32.732720] Mem abort info: [ 32.735504] ESR = 0x9604 [ 32.738546] Exception class = DABT (current EL), IL = 32 bits [ 32.70] SET = 0, FnV = 0 [ 32.747482] EA = 0, S1PTW = 0 [ 32.750612] Data abort info: [ 32.753478] ISV = 0, ISS = 0x0004 [ 32.757298] CM = 0, WnR = 0 [ 32.760256] user pgtable: 4k pages, 48-bit VAs, pgd = (ptrval) [ 32.766755] [0110] *pgd= [ 32.771700] Internal error: Oops: 9604 [#1] SMP [ 32.776557] Modules linked in: realtek hibmc_drm aes_ce_blk aes_ce_cipher ttm crct10dif_ce ghash_ce drm_kms_helper ixgbe(+) syscopyarea sha2_ce sysfillrect sysimgblt fb_sys_fops ptp sha256_arm64 sha1_ce hns3 hisi_sas_v3_hw(+) hinic pps_core hisi_sas_main drm hclge mdio libsas ahci hnae3 scsi_transport_sas libahci gpio_dwapb hid_generic usbhid hid aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 [ 32.811755] Process kworker/u256:1 (pid: 1280, stack limit = 0x (ptrval)) [ 32.819118] CPU: 66 PID: 1280 Comm: kworker/u256:1 Not tainted 4.15.18+ #24 [ 32.826047] Hardware name: Huawei TaiShan 2280 V2/BC82AMDC, BIOS 2280-V2 CS V3.B160.01 01/15/2020 [ 32.834884] Workqueue: :74:02.0_disco_q sas_discover_domain [libsas] [ 32.839182] hns3 :bd:00.0 enp189s0f0: renamed from eth8 [ 32.841558] pstate: a0c9 (NzCv daif +PAN +UAO) [ 32.851878] pc : prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.857426] lr : hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.864354] sp : 21833a00 [ 32.867653] x29: 21833a00 x28: b790728621e0 [ 32.872940] x27: b790728607d8 x26: b79072861158 [ 32.878227] x25: d7b07b9340a0 x24: 0028 [ 32.883515] x23: d7906cd69400 x22: d7906cd69418 [ 32.02] x21: b79072aad3d0 x20: 21b33000 [ 32.894089] x19: b79072aad3d0 x18: 0030 [ 32.899376] x17: 9e710776 x16: 3efb16aabb00 [ 32.904663] x15: x14: 3efb976abcef [ 32.909950] x13: 0006 x12: b79072863480 [ 32.915237] x11: b79072aad3e0 x10: b79072861148 [ 32.920524] x9 : x8 : 24cc0fb0 [ 32.925812] x7 : x6 : 003f [ 32.931099] x5 : 0040 x4 : 20a0 [ 32.936386] x3 : d79071e2d400 x2 : 21833bb4 [ 32.941673] x1 : b79072863460 x0 : 28a0 [ 32.946960] Call trace: [ 32.949398] prep_ssp_v3_hw+0x64/0x340 [hisi_sas_v3_hw] [ 32.954600] hisi_sas_task_exec.constprop.0+0x304/0x640 [hisi_sas_main] [ 32.961184] hisi_sas_exec_internal_tmf_task+0xec/0x290 [hisi_sas_main] [ 32.967767] hisi_sas_init_device+0x84/0x100 [hisi_sas_main] [ 32.973401] hisi_sas_dev_found+0xa4/0x24c [hisi_sas_main] [ 32.978864] sas_notify_lldd_dev_found+0x44/0xc0 [libsas] [ 32.984239] sas_discover_end_dev+0x24/0x30 [libsas] [ 32.989182] sas_ex_discover_devices+0x950/0xbfc [libsas] [ 32.994557] sas_discover_root_expander+0x12c/0x150 [libsas] [ 33.000192] sas_discover_domain+0x340/0x664 [libsas] [ 33.005225] process_one_work+0x1bc/0x3ec [ 33.009217] worker_thread+0x58/0x4a0 [ 33.012863] kthread+0x13c/0x170 [ 33.016077] ret_from_fork+0x10/0x18 [ 33.019638] Code: 2a004820 2a04 f9400ed8 f9410061 (3943a319) [ 33.025705] ---[ end trace da9256b7aa3297ba ]--- [Test Case] Boot a hi1620-based server w/ root disk attached to hisi_sas v3 controller. [Fix] e1ba0b0b4451 scsi: hisi_sas: Fix to only call scsi_get_prot_op() for non-NULL scsi_cmnd [Where things could go wrong] We could potentially be trading one boot time crash for another that hasn't popped up in testing. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1953386/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1933359] Re: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request
** Changed in: linux (Ubuntu Impish) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1933359 Title: [SRU][Ubuntu 21.10][Broadcom] mpi3mr driver submission request Status in linux package in Ubuntu: Fix Released Status in linux source package in Impish: Fix Committed Bug description: [Impact] Broadcom is coming up with next generation high performance Storage IO and RAID controllers. For details, follow: https://www.spinics.net/lists/linux-scsi/msg147868.html This family of controllers is managed by "mpi3mr" Linux device driver(written from scratch). First patchset of the driver is accepted by Linux upstream. The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git The driver will be part of 5.14 mainline Linux kernel release. Here is the list of commit ids: [Fixes] 9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints 74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support 28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check 2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume 44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of VD I/O timeout 71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging f061178e0762 scsi: mpi3mr: Complete support for soft reset 463429f8dd5c scsi: mpi3mr: Add support for threaded ISR 392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives 82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook 0ea177343f1f scsi: mpi3mr: Add change queue depth support e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks 8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook ff9561e910fc scsi: mpi3mr: Print IOC info for debugging 54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware fb9b04574f14 scsi: mpi3mr: Add support for recovering controller e36710dc06e3 scsi: mpi3mr: Additional event handling 8e653455547a scsi: mpi3mr: Add support for PCIe device event handling 13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling 672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread 023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair 824a156633df scsi: mpi3mr: Base driver code c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig Please include this driver in Ubuntu 21.10 release. Let me know for any questions. [Testing] Load the driver Run IO [Regression Risk] No extra test cases are needed, normal regression test cases such as driver load & running IOs are enough. [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/impish/+ref/mpi3mr_driver_bcom2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933359/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
