[Kernel-packages] [Bug 2008217] Re: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201)
This bug was fixed in the package linux-firmware - 20220329.git681281e4-0ubuntu3.12 --- linux-firmware (20220329.git681281e4-0ubuntu3.12) jammy; urgency=medium * Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201) (LP: #2008217) - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX201 -- Juerg Haefliger Fri, 24 Mar 2023 09:09:41 +0100 ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2008217 Title: Unsolicited wake from suspend with bluetooth connected (Intel AX211/AX201) Status in HWE Next: New Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-firmware source package in Lunar: Fix Released Bug description: [Summary] The system will auto wake from suspend with bluetooth connected. Note: 1. BT headset, BT Keyboard and BT mouse all can duplicate 2. RTL 8852BE & Intel AX201 cannot duplicate [Steps to reproduce] 1. Install dell-bto-jammy-jellyfish-quilladin-X72-20230216-17.iso 2. Boot to OS 3. Pair the bluetooth headset device. 4. Enter suspend. [Expected result] The system will not auto wake when the bluetooth device is connected. [Actual result] The system will auto wake from suspend with bluetooth connected. [Failure rate] 3/10 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2008217/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009952] Re: [amdgpu][psr] Screen flickering/ tearing on 6.1 kernel
** Summary changed: - Screen flickering/ tearing on 6.1 kernel + [amdgpu][psr] Screen flickering/ tearing on 6.1 kernel ** Tags added: psr -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2009952 Title: [amdgpu][psr] Screen flickering/ tearing on 6.1 kernel Status in linux-meta-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 package in Ubuntu: New Bug description: After upgrading from kernel 5.19.0-35-generic to 6.1.0-1007-oem there is occasional screen flicker/ tear. It happens around every minute; it seems connected to window/ pointer movement, but I have no clear way of reproducing. Disruption is minor, but annoying. I'm running 22.04 LTS on a new Thinkpad T14s with AMD Ryzen 6850u. The system is fully functional. No crashes, nothing breaks. Background on the use of 6.1.0-1007-oem: 5.19.0-35-generic breaks suspend/ resume on my laptop, see https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2007718. In a way, running 6.1 is a 'flight forward', since 5.15.0-67-generic (previous 22.04.1 LTS kernel) works well, with working suspend/ resume, and without screen flicker. But that's an 'old' kernel now, missing some nice improvements for the newer Ryzen APUs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-oem-22.04c 6.1.0.1007.7 ProcVersionSignature: Ubuntu 6.1.0-1007.7-oem 6.1.6 Uname: Linux 6.1.0-1007-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 10 13:09:20 2023 InstallationDate: Installed on 2023-02-06 (31 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-meta-oem-6.1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2009952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Downgraded bluez from 5.64-0ubuntu1 to 5.53-0ubuntu3.6
2. forgot the bt device on my phone and power cycle the machine
ii bluez 5.53-0ubuntu3.6
amd64Bluetooth tools and daemons
Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17
17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
3. Ran setup again, and then ran demo, the move command still works, I
can see cursor move.
BTW, the commit Dilyn found shoule not be relavent, I see the same warning
message with 5.15 kernel + 5.64 bluez
09572fca7223 Bluetooth: hci_sock: Add support for BT_{SND,RCV}BUF
2023-03-31T05:00:02.985301Z WARN ble::sys::mgmt: Failed to set
BT_SNDMTU: Protocol not available (os error 92)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2006517
Title:
Bluetooth works on desktop but not on ubuntu core
Status in bluez package in Ubuntu:
Confirmed
Bug description:
We have built a snap that uses some bluetooth functionality.
The snap runs well when using Ubuntu desktop 22.04 (all updates applied end
of Jan 2022).
We have tried using this same snap on Ubuntu Core 22 running on X86_64.
On some hardware platforms (thinkpad E15 and x86 Mac) everything works as
expected.
We can install the snap on Jammy 22.04 or Core 22 on these platforms and get
expected functionality regardless of OS.
On our targeted platform (a Dell 5570) things are not working. When running
22.04 Jammy, everything works. When running Core 22, some advanced bluetooth
functionality is not available.
Since the Core 22 image installs and runs on other X86_64 hardware we suspect
a device driver issue.
Attached are several files taken from the Dell 5570
1) dmesg from Core 22.
2) dmesg from Jammy 22.04
3) output of lspci from Jammy 22.04
4) Output of lsusb from Jammy 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013438] [NEW] Add support for Pensando SoC
Public bug reported: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. ** Affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** Affects: linux-meta-iot (Ubuntu) Importance: Undecided Status: New ** Affects: linux-iot (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Affects: linux-meta-iot (Ubuntu Focal) Importance: Undecided Assignee: Jesse Sung (wenchien) Status: In Progress ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-meta-iot (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu) ** Also affects: linux-iot (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Focal) ** Changed in: linux-iot (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux-meta-iot (Ubuntu Focal) Assignee: (unassigned) => Jesse Sung (wenchien) ** Changed in: linux-iot (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-meta-iot (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013438 Title: Add support for Pensando SoC Status in linux-iot package in Ubuntu: New Status in linux-meta-iot package in Ubuntu: New Status in linux-iot source package in Focal: In Progress Status in linux-meta-iot source package in Focal: In Progress Bug description: This bug is for tracking the progress of adding Pensando SoC support in focal:linux-iot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-iot/+bug/2013438/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core
1. Fresh installed ubuntu-22.04.2-desktop 2. Installed 5.15 kernel ii bluez 5.64-0ubuntu1 amd64Bluetooth tools and daemons Linux u-Precision-5570 5.15.0-69-generic #76-Ubuntu SMP Fri Mar 17 17:19:29 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux 3. Installed customer's 2 snaps and run the setup and connect the bt device from my phone 4. The move command works, I can see cursor on my phone. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2006517 Title: Bluetooth works on desktop but not on ubuntu core Status in bluez package in Ubuntu: Confirmed Bug description: We have built a snap that uses some bluetooth functionality. The snap runs well when using Ubuntu desktop 22.04 (all updates applied end of Jan 2022). We have tried using this same snap on Ubuntu Core 22 running on X86_64. On some hardware platforms (thinkpad E15 and x86 Mac) everything works as expected. We can install the snap on Jammy 22.04 or Core 22 on these platforms and get expected functionality regardless of OS. On our targeted platform (a Dell 5570) things are not working. When running 22.04 Jammy, everything works. When running Core 22, some advanced bluetooth functionality is not available. Since the Core 22 image installs and runs on other X86_64 hardware we suspect a device driver issue. Attached are several files taken from the Dell 5570 1) dmesg from Core 22. 2) dmesg from Jammy 22.04 3) output of lspci from Jammy 22.04 4) Output of lsusb from Jammy 22.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
Test is good with kinetic/linux-azure/5.19.0-1023.24 and kinetic/linux- aws/5.19.0-1023.24 ** Tags removed: verification-needed-kinetic ** Tags added: verification-done-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/2006546 Title: Improve arp_ndisc_evict_nocarrier.sh test result processing Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Bug description: [Impact] The arp_ndisc_evict_nocarrier.sh in selftests/net didn't pass a proper return value for failed test cases. Thus we might get false negatives if the last command runs successfully. [Fix] * 1856628baa selftests: net: return non-zero for failures reported in arp_ndisc_evict_nocarrier This patch can be cherry-picked into affected kernels. Lunar has been patched already. J-hwe-5.17 will be deprecated thus it will be skipped. [Test] Run the patched test, this should not cause any regression as sub tests are good with our kernels (except there is a cleanup issue in bug 1968310) One can deliberately fail a test by hijacking the if statement for the return value check to make sure this patch is working as expected. [Where problems could occur] This patch improves the result interpretation, we might see new failures being reported. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004122] Re: Cheese camera times out cheese program 4 nexigo
[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/2004122 Title: Cheese camera times out cheese program 4 nexigo Status in linux package in Ubuntu: Expired Bug description: Simply does not work in linux 20.10 ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: cheese 43~alpha-1 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 Uname: Linux 5.19.0-29-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-compute-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-driver-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Sun Jan 29 14:15:59 2023 InstallationDate: Installed on 2023-01-29 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP All-in-One 22-c0xx ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese43~alpha-1 cheese-common 43~alpha-1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/22/2022 dmi.bios.release: 15.48 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.asset.tag: 8CC8400GVQ dmi.board.name: 8446 dmi.board.vendor: HP dmi.board.version: dmi.chassis.type: 13 dmi.chassis.vendor: HP dmi.ec.firmware.release: 3.12 dmi.modalias: dmi:bvnAMI:bvrF.30:bd06/22/2022:br15.48:efr3.12:svnHP:pnHPAll-in-One22-c0xx:pvr:rvnHP:rn8446:rvr:cvnHP:ct13:cvr:sku3LB95AA#ABA: dmi.product.family: 103C_53311M HP OPP dmi.product.name: HP All-in-One 22-c0xx dmi.product.sku: 3LB95AA#ABA dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cj 1487 F wireplumber /dev/snd/controlC1: cj 1487 F wireplumber /dev/snd/seq:cj 1484 F pipewire CRDA: N/A CasperMD5CheckMismatches: ./preseed/ubuntu.seed ./pool/restricted/n/nvidia-graphics-drivers-515/libnvidia-gl-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-compute-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-driver-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-common-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-kernel-source-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/nvidia-utils-515_515.76+really.515.65.01-0ubuntu1_amd64.deb ./pool/restricted/n/nvidia-graphics-drivers-515/xserver-xorg-video-nvidia-515_515.76+really.515.65.01-0ubuntu1_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 InstallationDate: Installed on 2023-01-29 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: HP HP All-in-One 22-c0xx Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-29-generic root=UUID=fb9f6fa2-9bba-4386-816a-c7b89b097e9e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-29-generic N/A linux-backports-modules-5.19.0-29-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.3 Tags: wayland-session kinetic Uname: Linux 5.19.0-29-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: 06/22/2022 dmi.bios.release: 15.48
[Kernel-packages] [Bug 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
fcnal-test.sh can be tested on kinetic/linux-azure/5.19.0-1023.24, focal/linux-aws/5.4.0-1100.108 and focal/linux-azure/5.4.0-1106.112 ** Tags removed: verification-needed-focal verification-needed-kinetic ** Tags added: verification-done-focal verification-done-kinetic -- 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/2006391 Title: net:fcnal-test.sh 'nettest' command not found on F/K Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: On Focal and Kinetic the fcnal-test.sh does not run because it reports that 'nettest' command not found; skipping tests This is due to the nettest binary not being found in the path and skipping the tests, but it is built and exists in the net directory where the tests are run. There are also other tests in selftests/net that are skipped due to the binary being missing. There is a patch upstream "selftests/net: Find nettest in current directory" (bd5e1e42826f18147afb0) that fixes this by looking in the current directory. The patch is in Jammy through stable updates, but the patch hasnt made it to the other stable trees yet for whatever reasons so might as well just cherry-pick them into F/K. - [Impact] fcnal-test.sh in selftests/net gets skipped with 'nettest' command not found because its looking for the nettest binary in the path and not in the current directory where the binary is built and run from. There are also other tests in net that are skipped due to this binary not being found. [Fix] Add the current directory to the path and check again. This patch exists in Jammy through a stable update but hasn't made it to the other upstream-stable trees yet, but might as well get the patch in our other trees to enable this test to run. [Backport] For focal patch skip the pmtu.sh file as nettest is not run there and is not checked. Also minor context adjustments on return variable. [Potential regression] None. Just enabling the tests to run. [Tests] Verified tests are now not skipped and run. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006391/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013331] Re: net:udpgro_fwd.sh in ubuntu_kernel_selftests failed (received 5 vxlan packets, expected 1) with RISCV64 kernels
This issue can be found on J-(allwinner|riscv|starfive)-5.19 as well. ** Tags added: jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-allwinner in Ubuntu. https://bugs.launchpad.net/bugs/2013331 Title: net:udpgro_fwd.sh in ubuntu_kernel_selftests failed (received 5 vxlan packets, expected 1) with RISCV64 kernels Status in ubuntu-kernel-tests: New Status in linux-allwinner package in Ubuntu: New Status in linux-riscv package in Ubuntu: New Status in linux-starfive package in Ubuntu: New Status in linux-allwinner source package in Kinetic: New Status in linux-riscv source package in Kinetic: New Status in linux-starfive source package in Kinetic: New Bug description: Issue found on Kinetic 5.19 RISCV kernels, the IPv6 "GRO frag list over UDP tunnel" test failed with: # GRO frag list over UDP tunnelfail - received 5 vxlan packets, expected 1 Also, './udpgso_bench_tx: sendmsg: Connection refused' error message can be found in test report (bug 1950627) * kinetic/linux-allwinner/5.19.0-1009.9 # selftests: net: udpgro_fwd.sh # IPv4 # No GRO ok # GRO frag listok # GRO fwd ok # UDP fwd perfudp rx: 19 MB/s15707 calls/s # udp tx: 32 MB/s 559 calls/s559 msg/s # ./udpgso_bench_tx: sendmsg: Connection refused # fail client exit code 1, server 0 # UDP GRO fwd perfudp rx: 14 MB/s11560 calls/s # udp tx: 27 MB/s 469 calls/s469 msg/s # udp rx: 30 MB/s24798 calls/s # udp tx: 33 MB/s 560 calls/s560 msg/s # udp rx: 25 MB/s21155 calls/s # GRO frag list over UDP tunnelok # GRO fwd over UDP tunnel ok # UDP tunnel fwd perf udp rx: 7 MB/s 6214 calls/s # udp tx: 18 MB/s 307 calls/s307 msg/s # udp rx: 21 MB/s17202 calls/s # udp tx: 22 MB/s 388 calls/s388 msg/s # udp rx: 23 MB/s19497 calls/s # UDP tunnel GRO fwd perf udp rx: 12 MB/s 9884 calls/s # udp tx: 22 MB/s 376 calls/s376 msg/s # udp rx: 23 MB/s19334 calls/s # udp tx: 24 MB/s 412 calls/s412 msg/s # udp rx: 24 MB/s19776 calls/s # IPv6 # No GRO ok # GRO frag listok # GRO fwd ok # UDP fwd perfudp rx: 18 MB/s14789 calls/s # udp tx: 33 MB/s 576 calls/s576 msg/s # ./udpgso_bench_tx: sendmsg: Connection refused # fail client exit code 1, server 0 # UDP GRO fwd perfudp rx: 17 MB/s14020 calls/s # udp tx: 31 MB/s 534 calls/s534 msg/s # udp rx: 34 MB/s27995 calls/s # udp tx: 32 MB/s 556 calls/s556 msg/s # udp rx: 30 MB/s24576 calls/s # udp tx: 31 MB/s 537 calls/s537 msg/s # GRO frag list over UDP tunnelfail - received 5 vxlan packets, expected 1 # GRO fwd over UDP tunnel ok # UDP tunnel fwd perf udp rx: 14 MB/s11619 calls/s # udp tx: 24 MB/s 412 calls/s412 msg/s # ./udpgso_bench_tx: sendmsg: Connection refused # fail client exit code 1, server 0 # UDP tunnel GRO fwd perf udp rx: 18 MB/s15294 calls/s # udp tx: 27 MB/s 462 calls/s462 msg/s # udp rx: 26 MB/s21873 calls/s # udp tx: 27 MB/s 459 calls/s459 msg/s # udp rx: 27 MB/s22437 calls/s not ok 1 selftests: net: udpgro_fwd.sh # exit=1 * kinetic/linux-riscv/5.19.0-1015.16 # selftests: net: udpgro_fwd.sh # IPv4 # No GRO ok # GRO frag listok # GRO fwd ok # UDP fwd perfudp rx: 8 MB/s 6990 calls/s # udp tx: 27 MB/s 464 calls/s464 msg/s # udp rx: 32 MB/s26306 calls/s # udp tx: 38 MB/s 646 calls/s646 msg/s # udp rx: 44 MB/s35862 calls/s # udp tx: 44 MB/s 756 calls/s756 msg/s # UDP GRO fwd perfudp rx: 19 MB/s16099 calls/s # udp tx: 36 MB/s 614 calls/s614 msg/s # udp rx: 42 MB/s34700 calls/s # udp tx: 43 MB/s 735 calls/s735 msg/s # udp rx: 43 MB/s35145 calls/s # udp tx: 43 MB/s 742 calls/s742 msg/s # GRO frag list over UDP tunnelok # GRO fwd over UDP tunnel ok # UDP tunnel fwd perf udp rx: 12 MB/s10028 calls/s # udp tx: 25 MB/s
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI: 55f373889af0 RDI: 0012 mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08: R09: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12:
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda RBX: 55f373907c60 RCX: 7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RDX: RSI: 55f373889af0 RDI: 0012 mars 27 10:33:54 gandalf kernel: RBP: 55f373889af0 R08: R09: 7ffc801035d0 mars 27 10:33:54 gandalf kernel: R10: 0012 R11: 0246 R12: 0002 mars
[Kernel-packages] [Bug 2012908] Re: nvidia driver 515 fails to boot on kernel 6.2
I have exactly the same problem (this is on a Gigabyte Aero 15 YD 11th gen laptop), and had the same fix of migrating from v515 to v525. Annoyingly Software -> Additional Drivers is totally broken for me, too---when I select the driver and click apply something happens and a progress bar goes across the screen, and then I just get an empty error box (no title or actual message though). If someone could tell me how to extract logs from that so I could make a new issue, I'd be happy to oblige. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2012908 Title: nvidia driver 515 fails to boot on kernel 6.2 Status in linux-signed package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: I just updated my Lunar install, which brought me the 6.2 kernel, and it failed to start, stalling after enumerating my USB devices, until something times out with a message saying that the udev event queue failed to be drained. When attempting to move on to the normal graphics boot from rescue mode once the timeout is hit, I simply get a black screen. I'm blaming this on the nvidia driver because of this appearing in the log: mars 27 10:33:54 gandalf kernel: INFO: task systemd-udevd:304 blocked for more than 120 seconds. mars 27 10:33:54 gandalf kernel: Tainted: P OE 6.2.0-18-generic #18-Ubuntu mars 27 10:33:54 gandalf kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. mars 27 10:33:54 gandalf kernel: task:systemd-udevd state:D stack:0 pid:304 ppid:258flags:0x4006 mars 27 10:33:54 gandalf kernel: Call Trace: mars 27 10:33:54 gandalf kernel: mars 27 10:33:54 gandalf kernel: __schedule+0x2aa/0x610 mars 27 10:33:54 gandalf kernel: schedule+0x63/0x110 mars 27 10:33:54 gandalf kernel: schedule_preempt_disabled+0x15/0x30 mars 27 10:33:54 gandalf kernel: __mutex_lock.constprop.0+0x3f8/0x7a0 mars 27 10:33:54 gandalf kernel: ? __kmem_cache_alloc_node+0x19d/0x340 mars 27 10:33:54 gandalf kernel: ? nv_drm_calloc+0x1e/0x40 [nvidia_drm] mars 27 10:33:54 gandalf kernel: __mutex_lock_slowpath+0x13/0x20 mars 27 10:33:54 gandalf kernel: mutex_lock+0x3c/0x50 mars 27 10:33:54 gandalf kernel: __nv_drm_connector_detect_internal+0x15c/0x2f0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_connector_detect+0xe/0x20 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_helper_probe_detect_ctx+0xa3/0x120 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: check_connector_changed+0x52/0x200 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: drm_helper_hpd_irq_event+0xbc/0x170 [drm_kms_helper] mars 27 10:33:54 gandalf kernel: nv_drm_load+0x2e7/0x480 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: drm_dev_register+0x10e/0x250 [drm] mars 27 10:33:54 gandalf kernel: nv_drm_probe_devices+0x111/0x200 [nvidia_drm] mars 27 10:33:54 gandalf kernel: ? __pfx_init_module+0x10/0x10 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_drm_init+0x1e/0x60 [nvidia_drm] mars 27 10:33:54 gandalf kernel: nv_linux_drm_init+0xe/0xff0 [nvidia_drm] mars 27 10:33:54 gandalf kernel: do_one_initcall+0x5e/0x250 mars 27 10:33:54 gandalf kernel: do_init_module+0x7b/0x260 mars 27 10:33:54 gandalf kernel: load_module+0xc76/0xd60 mars 27 10:33:54 gandalf kernel: ? kernel_read_file+0x2a4/0x320 mars 27 10:33:54 gandalf kernel: __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: ? __do_sys_finit_module+0xc4/0x140 mars 27 10:33:54 gandalf kernel: __x64_sys_finit_module+0x18/0x30 mars 27 10:33:54 gandalf kernel: do_syscall_64+0x5b/0x90 mars 27 10:33:54 gandalf kernel: ? ksys_mmap_pgoff+0x120/0x260 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? exit_to_user_mode_prepare+0x30/0xb0 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? syscall_exit_to_user_mode+0x29/0x50 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: ? do_syscall_64+0x67/0x90 mars 27 10:33:54 gandalf kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc mars 27 10:33:54 gandalf kernel: RIP: 0033:0x7fd3dc85d89d mars 27 10:33:54 gandalf kernel: RSP: 002b:7ffc801034a8 EFLAGS: 0246 ORIG_RAX: 0139 mars 27 10:33:54 gandalf kernel: RAX: ffda
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws-5.15/5.15.0.1034.38~20.04.23)
All autopkgtests for the newly accepted linux-meta-aws-5.15 (5.15.0.1034.38~20.04.23) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-aws-5.15/5.15.0-1034.38~20.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
I can see fcnal-test.sh failing on focal/linux-azure/5.4.0-1106.112, focal/linux-aws/5.4.0-1100.108, jammy/linux-aws/5.15.0-1034.38 and jammy/linux-azure/5.15.0-1036.43 ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013422] [NEW] net: sched: allow flower to match vxlan options
Public bug reported: * Explain the bug(s) In upstream, TCA_POLICE_PKTRATE64 was introduced after TCA_FLOWER_KEY_ENC_OPT_VXLAN_GBP. linux-bluefiled only has TCA_POLICE_PKTRATE64 related support and does not have VXLAN support which will cause "ovs" project compile error because of lacking of VXALN GBP related support. * Brief explanation of fixes Cherry-pick. No adaptation. Add VXLAN support for flower to allow flower to match vxlan options d8f9dfae49ce net: sched: allow flower to match vxlan options * How to test 1) Compile "ovs" project, build succesfully. 2) VXLAN option can be used as match condition in tc. eg: # ip link add name vxlan0 type vxlan dstport 0 external # tc qdisc add dev vxlan0 ingress # tc filter add dev vxlan0 protocol ip parent : \ flower \ enc_src_ip 10.0.99.192 \ enc_dst_ip 10.0.99.193 \ enc_key_id 11 \ vxlan_opts 01020304/ \ ip_proto udp \ action mirred egress redirect dev eth0 * What it could break. Nothing. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2013422 Title: net: sched: allow flower to match vxlan options Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) In upstream, TCA_POLICE_PKTRATE64 was introduced after TCA_FLOWER_KEY_ENC_OPT_VXLAN_GBP. linux-bluefiled only has TCA_POLICE_PKTRATE64 related support and does not have VXLAN support which will cause "ovs" project compile error because of lacking of VXALN GBP related support. * Brief explanation of fixes Cherry-pick. No adaptation. Add VXLAN support for flower to allow flower to match vxlan options d8f9dfae49ce net: sched: allow flower to match vxlan options * How to test 1) Compile "ovs" project, build succesfully. 2) VXLAN option can be used as match condition in tc. eg: # ip link add name vxlan0 type vxlan dstport 0 external # tc qdisc add dev vxlan0 ingress # tc filter add dev vxlan0 protocol ip parent : \ flower \ enc_src_ip 10.0.99.192 \ enc_dst_ip 10.0.99.193 \ enc_key_id 11 \ vxlan_opts 01020304/ \ ip_proto udp \ action mirred egress redirect dev eth0 * What it could break. Nothing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1036.43~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 (5.15.0-1036.43~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.15/5.15.0-1036.43~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.15 (5.15.0-1036.43~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-azure-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
I would like to begin by expressing my sincere appreciation for your invaluable assistance in identifying the performance issue and presenting us with a clear reproducer for testing. Your contributions have been extremely helpful. We have carefully considered the possibility of reverting the NFS-related patches and have consulted with both our kernel team and specialists. While we acknowledge that the patch does address a functional error as outlined in LP#2003053, we also recognize that the bug responsible for the misbehavior of the new mechanism has been fixed. However, we understand that the current impact on performance resulting from the additional traffic is a significant concern. Despite the fact that the new mechanism adheres to the principles of POSIX design, we are faced with the challenge of devising an appropriate approach to address this issue. We understand that the new mechanism in NFS is having an impact on your production environment and we are fully committed to working with upstream to resolve the issue. As soon as we and upstream reach a consensus, we will open a new bug to address the performance issue. We sincerely apologize for any inconvenience caused by this issue, and we appreciate your patience and understanding as we work towards a solution that is both effective and aligned with POSIX design principles. -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc.
[Kernel-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen, since upgrading to Jammy
** Tags added: kinetic lunar ** Summary changed: - Annoying boot messages interfering with splash screen, since upgrading to Jammy + Annoying boot messages interfering with splash screen -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1970069 Title: Annoying boot messages interfering with splash screen Status in linux package in Ubuntu: Confirmed Status in plymouth package in Ubuntu: Confirmed Bug description: Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not as clean as it used to be. Basically, the flow used to be in 20.04: GRUB > Splash screen > Login prompt Currently in 22.04: GRUB > Splash screen > Messages (in the attached file) > Splash screen again for a sec > Login prompt All of those messages already existed in 20.04, the difference is that they were not appearing during boot. I was able to get rid of the "usb" related messages by just adding "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash". Regarding the fsck related message, I can get rid of them by adding "fsck.mode=skip". However, I do not want to just disable fsck or set the loglevel to 0. This is not a sustainable solution. Something definitely changed here. These messages are not of enough relevance to be shown at boot by default, and they should remain hidden like they were in Focal. Obviously a minor issue, but important to the whole look and feel of the OS for desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011616] Re: Connection timeout due to conntrack limits
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2011616 Title: Connection timeout due to conntrack limits Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: New Status in linux source package in Lunar: In Progress Status in linux-gcp source package in Lunar: New Bug description: Customers of GKE 1.25 and 1.26 are affected by the conntrack performance issue that causes random connection timeouts. The fix has been committed to to the upstream's net git repo and to prodkernel and needs to be backported to Ubuntu versions with kernel 5.15. https://partnerissuetracker.corp.google.com/issues/272090522 Fix: https://git.kernel.org/pub/scm/linux/kernel/git/netfilter/nf.git/commit/?id=c77737b736ceb50fdf150434347dbd81ec76dbb1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013397] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659248/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing
[Kernel-packages] [Bug 2013397] acpidump.txt
** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659251/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) - Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] - Flags: bus master, fast devsel, latency 0, IRQ 130 - Memory at a280 (64-bit, non-prefetchable) [size=32K] - Memory at a200 (64-bit, non-prefetchable) [size=8M] - Memory at a000 (64-bit, prefetchable) [size=4M] - Kernel driver in use: brcmfmac - Kernel modules: brcmfmac + Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] + Flags: bus master, fast devsel, latency 0, IRQ 130 + Memory at a280 (64-bit, non-prefetchable) [size=32K] + Memory at a200 (64-bit, non-prefetchable) [size=8M] + Memory at a000 (64-bit, prefetchable) [size=4M] + Kernel driver in use: brcmfmac + Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: ipotti531 1569 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard - Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse - Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub - Bus 001 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 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard + Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse + Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: - linux-restricted-modules-5.15.0-67-generic N/A - linux-backports-modules-5.15.0-67-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.10 + linux-restricted-modules-5.15.0-67-generic N/A + linux-backports-modules-5.15.0-67-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: - 0: phy0: Wireless LAN - Soft blocked: no - Hard blocked: no + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string
[Kernel-packages] [Bug 2013397] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659249/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2013397] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659250/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions --
[Kernel-packages] [Bug 2013397] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659247/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions --
[Kernel-packages] [Bug 2013397] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659239/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing
[Kernel-packages] [Bug 2013397] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659246/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions
[Kernel-packages] [Bug 2013397] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659245/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions --
[Kernel-packages] [Bug 2013397] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659243/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions --
[Kernel-packages] [Bug 2013397] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659242/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2013397] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659244/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to:
[Kernel-packages] [Bug 2013397] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659241/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing
[Kernel-packages] [Bug 2013397] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659240/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing
[Kernel-packages] [Bug 2013397] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659238/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2013397] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659237/+files/IwConfig.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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing
[Kernel-packages] [Bug 2013397] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659236/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions --
[Kernel-packages] [Bug 2013397] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659235/+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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: 1569 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-01-25 (64 days ago) InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer PRIME Z390-A Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: jammy Uname: Linux 5.15.0-67-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: 09/20/2018 dmi.bios.release: 5.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0506 dmi.board.asset.tag: Default string dmi.board.name: PRIME Z390-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: PRIME Z390-A dmi.product.sku: SKU dmi.product.version: 0506 dmi.sys.vendor: System manufacturer modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 # gitam changed to zero on 12.2.2023 enabled=0 mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 2013397] Re: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module
apport information ** Tags added: apport-collected jammy ** Description changed: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. - So... for the moment the only solution for it is to select in grub the - kernel 5.15.0-67-generic which is working. And of course waiting for a - kernel patch fixing the issue :-) + So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ipotti531 1569 F pulseaudio + CasperMD5CheckResult: pass + CurrentDesktop: MATE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2023-01-25 (64 days ago) + InstallationMedia: Ubuntu-MATE 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 004: ID 1a2c:2124 China Resource Semico Co., Ltd Keyboard + Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse + Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: System manufacturer PRIME Z390-A + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-67-generic root=UUID=86422ccd-a589-4319-88cf-d68b870c27a0 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-67.74-generic 5.15.85 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-67-generic N/A + linux-backports-modules-5.15.0-67-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.10 + RfKill: + 0: phy0: Wireless LAN + Soft blocked: no + Hard blocked: no + Tags: jammy + Uname: Linux 5.15.0-67-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: 09/20/2018 + dmi.bios.release: 5.6 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0506 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME Z390-A + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev 1.xx + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0506:bd09/20/2018:br5.6:svnSystemmanufacturer:pnPRIMEZ390-A:pvr0506:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ390-A:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: PRIME Z390-A + dmi.product.sku: SKU + dmi.product.version: 0506 + dmi.sys.vendor: System manufacturer + modified.conffile..etc.default.apport: + # set this to 0 to disable apport, or to 1 to enable it + # you can temporarily override this with + # sudo service apport start force_start=1 + # gitam changed to zero on 12.2.2023 + enabled=0 + mtime.conffile..etc.default.apport: 2023-02-12T17:45:21.538041 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/2013397/+attachment/5659234/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-azure/5.15.0.1036.32)
All autopkgtests for the newly accepted linux-meta-azure (5.15.0.1036.32) for jammy have finished running. The following regressions have been reported in tests triggered by the package: digimend-dkms/10-4 (amd64, arm64) glibc/2.35-0ubuntu3.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013390] 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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: Confirmed Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09: Mar 21 15:35:59
[Kernel-packages] [Bug 2013397] 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 2013397 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
Additional required patch was identified (https://github.com/dynup/kpatch/commit/324a43714b1227b5688e22966a5ee4414c8861d1) due to ftrace graph livepatch transition issue (https://github.com/SUSE/qa_test_klp/issues/17). Patch submitted and tested - pending mailing list review. ** Bug watch added: github.com/SUSE/qa_test_klp/issues #17 https://github.com/SUSE/qa_test_klp/issues/17 -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Fix Committed Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: Invalid Status in linux source package in Jammy: Fix Committed Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Released Bug description: [ Impact ] * kpatch upstream has gained support for more architectures which we would like to enable on LTS release. Since building livepatches using the kpatch tooling makes the most sense on LTS kernels. * This SRU is to enable s390x builds of kpatch on kinetic & jammy. * Separately linux kernel patches for s390x will also be backported to the GA kernel, whilst hwe-5.19 kernel already has all bugfixes to support livepatches. [ Test Plan ] * Attempt to run and load sample integration livepatches from the kpatch integration source code, against v5.15 & v5.19 kernels. These should succeed on: - amd64 jammy v5.15 - amd64 & s390x jammy v5.19 - amd64 & s390x kinetic v5.19 [ Where problems could occur ] * The newly generated livepatches produced by this kpatch may have different content (more or less sections/sybmols/relocations/etc), but remain compatible with all prior kernels and tool-chains. * This is a fairly large upstream update to the tooling. * One command line option to kpatch-build is no longer supported '-e', instead long form command line option must be used '--oot- module'. And '--ott-module-src' becomes mandatory in such cases, previously '--sourcedire' was required. Additional command line options added '--oot-module-src, -R|--non- replace'. '--skip-gcc-check' is still supported but prints warnings, it is deprecated in favour of '--skip-compiler-check'. kpatch-cc utility is added, which is a toolchain wrapper. Thus adjustments might be needed to scripts used to invoke and create kpatch modules. * Majority of non-test/non-doc changes are to do with: - add support for s390x and 32bit powerpc - add support for newer kernels and compilers (support & bugfixes to various sections and symbols) - more strict checking and bugfixes w.r.t. livepatch generation - refactoring and better build support for cross-compiled modules, compilation for various linux distributions, and code cleanups. * Some of the fixes from these new upstream releases have already been cherry-picked in the kpatch, but others might soon be needed on x84, i.e. to support gcc-12 built kernels. $ git log --no-merges --oneline v0.8.0..v0.9.7 -- kmod/ kpatch- build/ > shortlog.txt d46fea98ef kpatch-build: strengthen conditions for changed sections 9fac261ed0 kpatch-build: rela section could disappear after patched fe45029b4d kpatch-build: fix KBUILD_MODNAME for OOT modules 8cc0fedefb kpatch-build: use err.h instead of error.h for musl support 07433e98c0 kpatch-cc: fix stripping of source tree prefix 33368a88cd create-diff-object: add support for .return_sites section (x86) e921c557f9 macros: tweak syscall patching macros a1171b112e create-diff-object: Create missing section symbol 0308d52bcd kpatch/s390: Enable kpatch build support b0330ab18e kpatch/s390: Add additional bundled symbols. eb4a85f778 kpatch/s390: Add exclusion lists f0d00a9290 kpatch/s390: Add initial support for kpatch 10002f5aa6 kpatch/s390: Add gcc prerequisite flags for kpatch c6d0b5450b lookup: fix symtab parsing 52863dace0 create-diff-object: fix endianness in kpatch_no_sibling_calls_ppc64le() 017015a725 create-diff-object: make kpatch_check_relocations() more precise f0e3da336c create-diff-object: fix string extraction 86d5208b46 create-diff-object: error on symbol conversion failure 325bccd89d create-diff-object: skip conversion for sections which never have symbols 8508abd3b1 create-diff-object: allow converstion of empty symbols 8d5a628bde create-diff-object: add extra check for symbol conversion edge case 01427d50a1 create-diff-object: move addend math to a new function bec6488af6 create-diff-object: add rela_insn() error check 6b1895a6b7
[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA
** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09: Mar 21 15:35:59 LattePanda kernel: [437064.977591] R10:
[Kernel-packages] [Bug 2013390] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659231/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659230/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08:
[Kernel-packages] [Bug 2013390] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659229/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08:
[Kernel-packages] [Bug 2013390] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659233/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659228/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08:
[Kernel-packages] [Bug 2013390] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659232/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659223/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659224/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659226/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659225/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659227/+files/PciMultimedia.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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08:
[Kernel-packages] [Bug 2013390] CurrentDmesg.txt
** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659221/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659222/+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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: New Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09:
[Kernel-packages] [Bug 2013390] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659220/+files/Card0.Codecs.codec.2.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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: Incomplete Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8
[Kernel-packages] [Bug 2013390] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/2013390/+attachment/5659219/+files/Card0.Codecs.codec.0.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/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: Incomplete Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8
[Kernel-packages] [Bug 2013390] Re: CPU Lockup related to xhci/DMA
apport information ** Tags added: apport-collected jammy ** Description changed: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09: Mar 21 15:35:59 LattePanda kernel: [437064.977591] R10: R11: b42d4007cff8 R12: 9737c026c000 Mar 21 15:35:59 LattePanda kernel: [437064.977592] R13: 9737c026c260 R14: 0079 R15: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977594] FS:
[Kernel-packages] [Bug 2013397] [NEW] Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module
Public bug reported: Description:Ubuntu 22.04.1 LTS Release:22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: brcmfmac -- 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/2013397 Title: Kernel 5.15.0-69-generic breaking the Broadcom brcmfmac module Status in linux package in Ubuntu: New Bug description: Description: Ubuntu 22.04.1 LTS Release: 22.04 lspci -vnn successfully in kernel 5.15.0-67-generic 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries Device [14e4:43c3] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:86fb] Flags: bus master, fast devsel, latency 0, IRQ 130 Memory at a280 (64-bit, non-prefetchable) [size=32K] Memory at a200 (64-bit, non-prefetchable) [size=8M] Memory at a000 (64-bit, prefetchable) [size=4M] Kernel driver in use: brcmfmac Kernel modules: brcmfmac dmesg -k | grep brcmfmac broken in kernel 5.15.0-69-generic [4.102083] usbcore: registered new interface driver brcmfmac [4.102148] brcmfmac :03:00.0: enabling device ( -> 0002) [4.209554] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4366c-pcie for chip BCM4366/4 [4.216533] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.bin failed with error -2 [4.224774] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.System manufacturer-PRIME Z390-A.txt failed with error -2 [4.225411] brcmfmac :03:00.0: Direct firmware load for brcm/brcmfmac4366c-pcie.txt failed with error -2 [5.053177] brcmfmac :03:00.0: brcmf_pcie_init_ringbuffers: invalid max_flowrings(264) module brcmfmac not loading anymore because of error brcmf_pcie_init_ringbuffers: invalid max_flowrings(264). This is likely a regression in kernel source code /drivers/net/wireless/broadcom/brcm80211/brcmfmac/pcie.c. So... for the moment the only solution for it is to select in grub the kernel 5.15.0-67-generic which is working. And of course waiting for a kernel patch fixing the issue :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2013397/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Medium Assignee: Michael Reed (mreed8855) Status: 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/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Incomplete Status in linux source package in Kinetic: New Status in linux source package in Lunar: Incomplete Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some case, Intel's SPR-HBM needs this. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] [Where problems could occur] The regression risk is low [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856871] Re: i/o error if next unused loop device is queried
** Also affects: parted (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: udev (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: snapd (Ubuntu Bionic) Importance: Undecided Status: New ** No longer affects: parted (Ubuntu Bionic) ** No longer affects: snapd (Ubuntu Bionic) ** No longer affects: systemd (Ubuntu Bionic) ** No longer affects: udev (Ubuntu Bionic) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Jorge Merlino (jorge-merlino) -- 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/1856871 Title: i/o error if next unused loop device is queried Status in linux package in Ubuntu: Fix Released Status in parted package in Ubuntu: Invalid Status in snapd package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in udev package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] * There's an I/O error on fsync() in a detached loop device if it has been previously attached. The issue is that write cache is enabled in the attach path in loop_configure() but it isn't disabled in the detach path; thus it remains enabled in the block device regardless of whether it is attached or not. * fsync() on detached loop devices can be called by partition tools and commands run by sosreport, so the unexpected kernel error message might surprise users or even distract from the actual issue being investigatedr. It might also trigger alerts in logging/monitoring/alerting stacks [Fix] * Disable write cache in the detach path [Test Plan] * Attach and detach an image to a loop device and test fsync return value aterwards # DEV=/dev/loop7 # IMG=/tmp/image # truncate --size 1M $IMG # losetup $DEV $IMG # losetup -d $DEV Before: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= -1 EIO (Input/output error) Warning: Error fsyncing/closing /dev/loop7: Input/output error [ 982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 After: # strace -e fsync parted -s $DEV print 2>&1 | grep fsync fsync(3)= 0 [Where problems could occur] * The detach path for block devices is modified. Worst case scenario would be an error when detaching loop devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1034.38~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1034.38~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1023.24~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1023.24~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006692] Re: net:fcnal-test.sh didn't return a non-zero value even with some sub-tests failed
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/2006692 Title: net:fcnal-test.sh didn't return a non-zero value even with some sub- tests failed Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: [Impact] The net/fcnal-test.sh on F/J won't return a non-zero value even with some sub test cases failed, here is an example on Jammy: # Tests passed: 857 # Tests failed: 5 ok 1 selftests: net: fcnal-test.sh Therefore it's marked as PASSED on our report and making it difficult to spot these failures: # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping local, VRF bind - VRF IP [FAIL] # TEST: ping local, device bind - ns-A IP [FAIL] # With VRF # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # SYSCTL: net.ipv4.ping_group_range=0 2147483647 # SYSCTL: net.ipv4.raw_l3mdev_accept=1 # TEST: ping out, vrf device+address bind - ns-B IPv6 LLA [FAIL] [Fix] * 0f8a3b48f9 selftests: net/fcnal-test.sh: add exit code This patch can be cherry-picked into Focal and Jammy kernel. We don't have this test in Bionic, and this patch has already landed on Kinetic and OEM-5.17 [Test] Run the patched test, the return value will be 1 whenever the number of failed test cases is not 0. [Where problems could occur] Change limited to testing tools, but we're expected to see new failures in Jammy. With bug 2006391 fixed later on, we will see failures reported in F/K as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2006692/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1034.38)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1034.38) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) nvidia-graphics-drivers-525/525.89.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.15/5.15.0-1034.38~20.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.15 (5.15.0-1034.38~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.20.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-restricted-modules-aws-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws/5.15.0-1034.38)
All autopkgtests for the newly accepted linux-restricted-modules-aws (5.15.0-1034.38) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) nvidia-graphics-drivers-525/525.89.02-0ubuntu0.22.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure-5.19/5.19.0-1023.24~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-azure-5.19 (5.19.0-1023.24~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003267] Re: [EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04 release
This bug is awaiting verification that the linux-aws/5.15.0-1034.38
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists, change the tag 'verification-needed-jammy' to
'verification-failed-jammy'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-aws
--
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/2003267
Title:
[EGS] Backport intel_idle support for Eagle Stream Ubuntu 22.04
release
Status in intel:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Bug description:
== SRU Justification ==
Intel has requested the following patches which enable enable Intel_idle for
eagle stream.
Intel has customers that would like to use the intel_idle driver on latest
SPR (Sapphire Rapids).
These patches have all landed upstream, but are not in Jammy.
These patches will enable customers to use Ubuntu 22.04 on new hardware
from Intel.
== Fixes ==
9edf3c0ffef0 ("intel_idle: add SPR support")
da0e58c038e6 ("intel_idle: add 'preferred_cstates' module argument")
3a9cf77b60dc ("intel_idle: add core C6 optimization for SPR")
03eb65224e57 ("cpuidle: intel_idle: Drop redundant backslash at line end")
39c184a6a9a7 ("intel_idle: Fix the 'preferred_cstates' module parameter")
7eac3bd38d18 ("intel_idle: Fix SPR C6 optimization")
1548fac47a11 ("intel_idle: make SPR C1 and C1E be independent")
== Regression Potential ==
Medium. These patches are specific to enable intel_idle support for Sapphire
Rapids. Changes
are specific to Intel and tested by Intel.
== Test Case ==
A test kernel was built with these patches and tested by Intel.
Intel tested on SPR-SP machine and see the correct 190us and 600us residency
for the C6 state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/2003267/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006077] Re: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/2006077 Title: Fix the ACPI _CPC not found error from kernel dmesg on some dynamic SSDT table loaded firmwares Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: [Impact] Some machines which have dynamically loaded SSDT tables, will not be loaded and get the CPPC not worked. [Fix] Fix the regression by some load supports for CPPC from an SSDT dynamically when _OSC reports CPPC v2. And make the "[\_SB.PR00._CPC], AE_NOT_FOUND" gone. [Test] Verified all the OEM dynamic table loaded or the "[\_SB.PR00._CPC], AE_NOT_FOUND" error exist or not on demesg . [Where problems could occur] Low risk, It only helps to CPPC support loaded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Released Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ Included in v6.2-rc1 d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug is awaiting verification that the linux-aws/5.15.0-1034.38 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1036.43)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.15.0-1036.43) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-azure/5.15.0-1036.43)
All autopkgtests for the newly accepted linux-restricted-modules-azure (5.15.0-1036.43) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-azure [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013390] 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 2013390 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2013390 Title: CPU Lockup related to xhci/DMA Status in linux package in Ubuntu: Incomplete Bug description: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_cod el ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89
[Kernel-packages] [Bug 2013390] [NEW] CPU Lockup related to xhci/DMA
Public bug reported: CPU lockup problems have been encountered on a number of computers running kernel 5.15 or later, but this problem could've been introduced in an earlier version. Three of these systems are running a light weight version of Ubuntu. The kernels that have been tested are 4.19, 5.15, 5.18, 5.19, 6.0, and 6.1. The basic setup that's running and causing problems is a program that starts several (4+) distinct processes and communicates with different ACM/USB concurrently. This problem can be encountered a few minutes after starting this program up to about a week later, but it generally happens after ~1-3 days. When the lock up occurs, if there are the same number or fewer CPU cores than the running number of running processes doing ACM/USB device communication, nothing else will execute due to all of the CPU cores being locked up until the watchdog frees things up. The longest lockup that has been encountered was over 20 minutes! The computers that this problem has been tested and verified to be present on are the NUC7i5BNK, the ASRock NUC BOX-1260P, and the LattePanda Delta 3. Although, this problem appears to be system agnostic; if kernel version ~5.15 or later is being used, it'll likely happen if this program is setup and run on any system when enough known ACM/USB devices are connected to it and communicated with concurrently from different processes. The main reason "this program" is being stated in a broad sense is because multiple different setups fitting that description have been tested trying to get around encountered problems in various clever ways and this problem has persisted regardless of what's been done. Here's a short snippet from the LattePanda Delta 3's syslog: Mar 21 15:35:59 LattePanda kernel: [437064.977491] NMI watchdog: Watchdog detected hard LOCKUP on cpu 1 Mar 21 15:35:59 LattePanda kernel: [437064.977496] Modules linked in: tls binfmt_misc snd_sof_pci_intel_icl snd_sof_intel_hda_common soundwire_intel soundwire_generic_allocation soundwire_cadence intel_rapl_msr snd_sof_intel_hda mei_hdcp snd_sof_pci snd_sof_xtensa_dsp snd_sof snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi intel_rapl_common soundwire_bus x86_pkg_temp_thermal intel_powerclamp snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic coretemp ledtrig_audio snd_soc_core nls_iso8859_1 snd_compress ac97_bus kvm_intel snd_pcm_dmaengine snd_hda_intel snd_intel_dspcfg kvm snd_intel_sdw_acpi intel_cstate snd_hda_codec snd_hda_core btusb rtsx_usb_ms btrtl btbcm snd_hwdep btintel bluetooth memstick iwlmvm snd_pcm ecdh_generic snd_timer ecc wmi_bmof mac80211 snd libarc4 soundcore 8250_dw mei_me mei iwlwifi ftdi_sio pl2303 cp210x cdc_acm usbserial cfg80211 goodix acpi_tad mac_hid acpi_pad dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua sch_fq_codel ramoops efi_pstore reed_solomon Mar 21 15:35:59 LattePanda kernel: [437064.977544] pstore_blk pstore_zone ip_tables x_tables autofs4 btrfs blake2b_generic xor zstd_compress raid6_pq libcrc32c rtsx_usb_sdmmc rtsx_usb mmc_block i915 ttm drm_kms_helper syscopyarea sysfillrect igb sysimgblt fb_sys_fops spi_pxa2xx_platform cec dca crct10dif_pclmul rc_core dw_dmac i2c_i801 crc32_pclmul dw_dmac_core ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_smbus i2c_algo_bit sdhci_pci ahci cqhci drm libahci intel_lpss_pci sdhci intel_lpss xhci_pci idma64 xhci_pci_renesas wmi video pinctrl_jasperlake Mar 21 15:35:59 LattePanda kernel: [437064.977572] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G L 5.15.0-67-lowlatency #74-Ubuntu Mar 21 15:35:59 LattePanda kernel: [437064.977575] Hardware name: LattePanda LattePanda 3 Delta/LattePanda 3 Delta, BIOS LP-BS-7-S70JR120-CN51G-D 08/15/2022 Mar 21 15:35:59 LattePanda kernel: [437064.977576] RIP: 0010:native_queued_spin_lock_slowpath.part.0+0x4f/0x200 Mar 21 15:35:59 LattePanda kernel: [437064.977584] Code: 0f ba 2b 08 0f 92 c2 8b 03 0f b6 d2 c1 e2 08 30 e4 09 d0 a9 00 01 ff ff 0f 85 2a 01 00 00 85 c0 74 0e 8b 03 84 c0 74 08 f3 90 <8b> 03 84 c0 75 f8 b8 01 00 00 00 66 89 03 5b 41 5c 41 5d 41 5e 41 Mar 21 15:35:59 LattePanda kernel: [437064.977586] RSP: 0018:b42d4007ce80 EFLAGS: 0002 Mar 21 15:35:59 LattePanda kernel: [437064.977587] RAX: 000c0101 RBX: 9737c026c2ac RCX: 0017 Mar 21 15:35:59 LattePanda kernel: [437064.977589] RDX: RSI: RDI: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977590] RBP: b42d4007cea8 R08: R09: Mar 21 15:35:59 LattePanda kernel: [437064.977591] R10: R11: b42d4007cff8 R12: 9737c026c000 Mar 21 15:35:59 LattePanda kernel: [437064.977592] R13: 9737c026c260 R14: 0079 R15: 9737c026c2ac Mar 21 15:35:59 LattePanda kernel: [437064.977594] FS: () GS:97393808() knlGS: Mar 21 15:35:59 LattePanda kernel: [437064.977595] CS: 0010 DS: ES:
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.15.0.1034.33)
All autopkgtests for the newly accepted linux-meta-aws (5.15.0.1034.33) for jammy have finished running. The following regressions have been reported in tests triggered by the package: dm-writeboost/2.2.13-1ubuntu2 (amd64, arm64) dpdk-kmods/0~20220111+git-1ubuntu1~22.04.1 (amd64, arm64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu17~22.04.1 (amd64, arm64) systemd/249.11-0ubuntu3.7 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux-oracle/5.4.0-1099.108 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux-oracle -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware
[Kernel-packages] [Bug 2009325] Re: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74
This bug is awaiting verification that the linux- azure-4.15/4.15.0-1163.178 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed-bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-bionic-linux-azure-4.15 verification-needed-bionic -- 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/2009325 Title: NFS deathlock with last Kernel 5.4.0-144.161 and 5.15.0-67.74 Status in linux package in Ubuntu: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-aws source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-aws source package in Kinetic: Fix Released Status in linux source package in Lunar: In Progress Status in linux-aws source package in Lunar: Invalid Bug description: After updating on the kernel 5.4.0-144.161 at Ubuntu 18 and 5.15.0-67.74 at Ubuntu 20, we have a 100% CPU outlation and 20 to 30 Mbit traffic to the clients for our NFS servers. All clients are extremely slow when it comes to access to the NFS resources. Restart and use older kernel, fixed the problem. Ubuntu 18 5.4.0-139-generic Ubuntu 20 5.15.0-60-Generic I don't have a NFS problem with this kernel. Problem came with the last releas on March 3rd, 2023 --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:00 seq crw-rw 1 root audio 116, 33 Mär 4 15:00 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-67-generic root=/dev/mapper/vg1-root ro net.ifnames=0 biosdevname=0 kvm.nx_huge_pages=auto elevator=noop ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 RelatedPackageVersions: linux-restricted-modules-5.15.0-67-generic N/A linux-backports-modules-5.15.0-67-generic N/A linux-firmware 1.187.36 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.15.0-67-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 11/12/2020 dmi.bios.release: 4.6 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:br4.6:efr0.0:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mär 4 15:03 seq crw-rw 1 root audio 116, 33 Mär 4 15:03 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.28 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1023.24~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1023.24~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988836] Autopkgtest regression report (linux-restricted-modules-aws-5.19/5.19.0-1023.24~22.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-aws-5.19 (5.19.0-1023.24~22.04.1) for jammy have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.04.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/jammy/update_excuses.html#linux-restricted-modules-aws-5.19 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1978980] Re: [amdgpu] Wrong external screen resolution after wake up from sleep
I have the same problem on my Dell Latitude 5400 on Ubuntu 22.04.2 LTS connected via HDMI to AOC Q3279VWFD8. After sleep the resolution goes from 2560x1440 75hz to 1920x1080 60hz -- 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/1978980 Title: [amdgpu] Wrong external screen resolution after wake up from sleep Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04, running KDE) I started experiencing a problem with external screen resolution after the wake up from sleep. The monitor resolution is small (1280x768) and doesn't respect the setting prior the sleep (1920x1200). After the wake up from sleep: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1280x768 59.94* # a list of lower resolutions ``` There is an error when trying to change the setting to the highest resolution supported by the monitor (which is not included in the above list). ``` > xrandr --output DisplayPort-1 --mode 1920x1200 xrandr: cannot find mode 1920x1200 ``` After the turn off and turn on of the external monitor, the resolution is somehow added to the xrandr list: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95 + # a list of resolutions 1280x768 59.94* # a list of lower resolutions ``` Now it is possible to change the resolution: ``` > xrandr --output DisplayPort-1 --mode 1920x1200 # no output, the resolution was successfully changed ``` After the change, the resolution is successfully changed and xrandr gives proper output: ``` > xrandr HDMI-A-0 disconnected (normal left inverted right x axis y axis) DisplayPort-0 disconnected (normal left inverted right x axis y axis) DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 535mm x 339mm 1920x1200 59.95*+ # a list of lower resolutions ``` The problem is not present on fresh start. However, it is consistently present after the wake up from sleep. What can cause the problem and how may I fix it? Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the external monitor is connected via USB-C. There are no problems with laptop screen resolution, only external monitor is affected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Jun 16 18:12:05 2022 DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad E595 [17aa:5124] InstallationDate: Installed on 2019-08-21 (1030 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20NE000BMC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft vt.handoff=7 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago) dmi.bios.date: 01/26/2022 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET44W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NE000BMC dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495: dmi.product.family: ThinkPad E495 dmi.product.name: 20NE000BMC dmi.product.sku:
[Kernel-packages] [Bug 2012953] Re: No HDMI with Intel Iris Xe Graphics
Hi Jarno I didn't try because the laptop don't even see the screen plugged in hdmi. Nothing happens, screen turns to sleep mode. that is confirmed with the screen setting in Cinnamon : only the laptop screen is mentioned. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2012953 Title: No HDMI with Intel Iris Xe Graphics Status in linux package in Ubuntu: Incomplete Bug description: Hi I have a XMG Focus 17 laptop. i7-12700H with Intel Iris Xe Graphics Nvidia RTX 3060. Dualboot LinuxMint 21.1 (based on Ubuntu 22.04) / Windows 10 Kernel 5.15.0-67-generic HDMI output (2nd screen, TV) works fine with : -Windows -LinuxMint with Nvidia card activated BUT don't work with : LinuxMint with Intel Graphic GPU. I have the same pb on another laptop DELL VOSTRO 5630 (no Nvidia, only Intel GPU), running LinuxMint 21.1 too. So the issue comes from the Intel Iris GPU. My hdmi wires are OK. Here are some command lines ouputs : $ inxi -bG System: Host: vincent-XMG-FOCUS-M22 Kernel: 5.15.0-67-generic x86_64 bits: 64 Desktop: Cinnamon 5.6.8 Distro: Linux Mint 21.1 Vera Machine: Type: Laptop System: SchenkerGmbH product: XMG FOCUS (M22) v: N/A serial: Mobo: NB01 model: NP5x_NP6x_NP7xPNP serial: UEFI: INSYDE v: 1.07.09RTR2 date: 12/01/2022 Battery: ID-1: BAT0 charge: 51.3 Wh (100.0%) condition: 51.3/52.5 Wh (97.8%) CPU: Info: 14-core (6-mt/8-st) 12th Gen Intel Core i7-12700H [MST AMCP] speed (MHz): avg: 715 min/max: 400/4600:4700:3500 Graphics: Device-1: Intel Alder Lake-P Integrated Graphics driver: i915 v: kernel Device-2: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: N/A Device-3: Acer BisonCam NB Pro type: USB driver: uvcvideo Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915 resolution: 1920x1080~144Hz OpenGL: renderer: Mesa Intel Graphics (ADL GT2) v: 4.6 Mesa 22.2.5 Network: Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi Device-2: Intel Ethernet I219-V driver: e1000e Drives: Local Storage: total: 2.73 TiB used: 1.13 TiB (41.5%) Info: Processes: 386 Uptime: 3h 12m Memory: 15.34 GiB used: 3.21 GiB (20.9%) Shell: Bash inxi: 3.3.13 --- $ grep . /sys/class/drm/*/status /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-DP-3/status:disconnected /sys/class/drm/card0-DP-4/status:disconnected /sys/class/drm/card0-eDP-1/status:connected Thanks a lot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2013383] [NEW] mlxbf-bootctl: support SMC call for setting ARM boot state
Public bug reported: SRU Justification: [Impact] Add a new SMC call which allows setting the ARM boot progress state to "OS is up". [Fix] * Add a new SMC call in mlxbf-bootctl which allows setting the ARM boot progress state to "OS is up". [Test Case] * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists [Regression Potential] * No known regression because it is just adding a sysfs entry. It is backward compatible with older TAF images. If the SMC call is not supported by ATF, it is ignored. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/2013383 Title: mlxbf-bootctl: support SMC call for setting ARM boot state Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Add a new SMC call which allows setting the ARM boot progress state to "OS is up". [Fix] * Add a new SMC call in mlxbf-bootctl which allows setting the ARM boot progress state to "OS is up". [Test Case] * Check that /sys/devices/platform/MLNXBF04:00/driver/os_up exists [Regression Potential] * No known regression because it is just adding a sysfs entry. It is backward compatible with older TAF images. If the SMC call is not supported by ATF, it is ignored. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/2013383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Tested against H965i, resolved my problem. -- 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/1971151 Title: [SRU][Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification: [Impact] Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: f304d35e5995 scsi: mpi3mr: Update driver version to 8.0.0.69.0 7dbd0dd8cde3 scsi: mpi3mr: Add support for NVMe passthrough 986d6bad2103 scsi: mpi3mr: Expose adapter state to sysfs 43ca11005098 scsi: mpi3mr: Add support for PEL commands 506bc1a0d6ba scsi: mpi3mr: Add support for MPT commands f3de4706c1e0 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header f5e6d5a34376 scsi: mpi3mr: Add support for driver commands 4268fa751365 scsi: mpi3mr: Add bsg device support 1fcbe4c49039 scsi: mpi3mr: Fix kernel-doc 4094981db7b6 scsi: mpi3mr: Rework mrioc->bsg_device model to fix warnings 9feb5c4c3f95 scsi: mpi3mr: Add target device related sysfs attributes e51e76edddb1 scsi: mpi3mr: Add shost related sysfs attributes bc7896d31a92 scsi: mpi3mr: Return error if dma_alloc_coherent() fails a25eafd13e5f scsi: mpi3mr: Fix a NULL vs IS_ERR() bug in mpi3mr_bsg_init() 256bd4f23d9c scsi: mpi3mr: Return I/Os to an unrecoverable HBA with DID_ERROR 2dd8389f96d6 scsi: mpi3mr: Hidden drives not removed during soft reset 1aa529d40025 scsi: mpi3mr: Increase I/O timeout value to 60s [Test Plan] 1. Install and boot kernel 2. Run basic I/O tests [Where problems could occur] Moderate to low regression risk for the kernel as most changes are in the driver [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/mpi3mr_bsg_support_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/1951447 Title: ubuntu_kernel_selftests: net:udpgso_bench.sh failed Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: 04:41:59 DEBUG| [stdout] # selftests: net: udpgso_bench.sh 04:41:59 DEBUG| [stdout] # ipv4 04:41:59 DEBUG| [stdout] # tcp 04:42:00 DEBUG| [stdout] # tcp tx: 2736 MB/s46415 calls/s 46415 msg/s 04:42:00 DEBUG| [stdout] # tcp rx: 2737 MB/s46161 calls/s 04:42:01 DEBUG| [stdout] # tcp tx: 2735 MB/s46392 calls/s 46392 msg/s 04:42:01 DEBUG| [stdout] # tcp rx: 2739 MB/s46226 calls/s 04:42:02 DEBUG| [stdout] # tcp tx: 2717 MB/s46092 calls/s 46092 msg/s 04:42:02 DEBUG| [stdout] # tcp zerocopy 04:42:02 DEBUG| [stdout] # ./udpgso_bench_tx: connect: Connection refused 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: PASS=17 SKIP=0 FAIL=1 04:42:54 DEBUG| [stdout] # udpgso_bench.sh: ^[[0;31mFAIL^[[0m 04:42:54 DEBUG| [stdout] not ok 1 selftests: net: udpgso_bench.sh # exit=1 04:42:54 DEBUG| [stdout] make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' 04:42:54 ERROR| Exception escaping from test: Traceback (most recent call last): File "/home/ubuntu/autotest/client/shared/test.py", line 411, in _exec _call_test_function(self.execute, *p_args, **p_dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 823, in _call_test_function return func(*args, **dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 291, in execute postprocess_profiled_run, args, dargs) File "/home/ubuntu/autotest/client/shared/test.py", line 212, in _call_run_once self.run_once(*args, **dargs) File "/home/ubuntu/autotest/client/tests/ubuntu_kernel_selftests/ubuntu_kernel_selftests.py", line 252, in run_once raise error.TestError(test_name + ' failed.') TestError: net:udpgso_bench.sh failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1951447/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814234] Re: rtcpie in timers from ubuntu_kernel_selftests randomly failing
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: Node: Standard_D11_v2 Kernel: 4.18.0-1008.8~18.04.1 selftests: timers: rtcpie Periodic IRQ rate is 1024Hz. Counting 20 interrupts at: 2Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 4Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 8Hz: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 16Hz:1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 32Hz:1 2 3 4 5 6 7 PIE delta error: 0.034667 should be close to 0.031250 181. 01/30 20:08:46 DEBUG| utils:0153| [stdout] not ok 1..9 selftests: timers: rtcpie [FAIL] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1814234/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987430] Re: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/1987430 Title: Ubuntu 22.04 kernel 5.15.0-46-generic leaks kernel memory in kmalloc-2k slabs Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Since updating to kernel 5.15.0-46-generic (package version 5.15.0-46.49), all of our Ubuntu 22.04 LTS servers are leaking kernel memory; our first server with 8 GB of RAM just fatally OOMed, causing us to detect this. Inspection of OOM reports, /proc/meminfo, and /proc/slabinfo says that it's mostly going to unreclaimable kmalloc-2k slabs: Aug 23 12:51:11 cluster kernel: [361299.864757] Unreclaimable slab info: Aug 23 12:51:11 cluster kernel: [361299.864757] Name Used Total [...] Aug 23 12:51:11 cluster kernel: [361299.864924] kmalloc-2k 6676584KB6676596KB Most of our machines appear to be leaking slab memory at a rate of around 20 to 40 Mbytes/hour, with some machines leaking much faster; the champions are leaking kernel memory at 145 Mbytes/hour and 237 Mbytes/hour. We aren't running any proprietary kernel modules and our only unusual kernel configuration is that we've disabled AppArmor with 'apparmor=0' on the kernel command line. /proc/version_signature: Ubuntu 5.15.0-46.49-generic 5.15.39 Full kernel command line from the Dell R240 system that fatally OOMd: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=3165564f-a2dd-4b39-935b-114f3e23ff54 ro console=ttyS0,115200 console=tty0 apparmor=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/1990849 Title: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54 Status in linux package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Fix Released Status in zfs-linux source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Released Status in zfs-linux source package in Kinetic: Confirmed Status in linux source package in Lunar: Fix Released Status in zfs-linux source package in Lunar: Confirmed Bug description: Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS are broken. Reproducer steps: ``` sudo snap install lxd sudo snap set lxd shiftfs.enable=true sudo lxd init --auto lxc storage create zfs zfs lxc launch images:ubuntu/jammy c1 -s zfs lxc exec c1 -- touch /root/foo touch: cannot touch '/root/foo': Value too large for defined data type ``` Expected result can be achieved by disabling shiftfs: ``` sudo snap set lxd shiftfs.enable=false sudo systemctl reload snap.lxd.daemon lxc launch images:ubuntu/jammy c2 -s zfs lxc exec c2 -- touch /root/foo lxc exec c2 -- ls -la /root/foo -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo ``` Kernel 5.15.0-47-generic does not exhibit this issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-48-generic 5.15.0-48.54 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: user 2240 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Sep 26 14:55:52 2022 InstallationDate: Installed on 2022-03-04 (205 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228) MachineType: LENOVO 20R1000RUS ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/15/2021 dmi.bios.release: 1.34 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET40W(1.34 ) dmi.board.asset.tag: Not Available dmi.board.name: 20R1000RUS 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.15 dmi.modalias: dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20R1000RUS dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990849/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993561] Re: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1993561 Title: RaptorLake: Fix the Screen is shaking by onboard HDMI port in mirror mode Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] The Screen is shaking connected monitor to Onboard HDMI port. [Fix] The interlaced mode is not supported for Intel Gen 12 onwards. Disable interlaced mode for DP on Display >= 12. Due to schedule, SRU for OEM kernels first. After these patches are merged to mainline/drmtip kernel, will SRU for generic kernels. [Test Case] 1.Connected two external Monitor to the onboard HDMI/DP port . 2.Boot OS. 2.set mirror mode. (onboard HDMI / onboard DP) 3.check if screen shakes. [Where problems could occur] Low, Remove interlace support for Display >= 12 so it wouldn't cause a regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1996048] Re: Screen freeze after resuming from suspend (nvme0: I/O timeout)
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1996048 Title: Screen freeze after resuming from suspend (nvme0: I/O timeout) Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] The system hangs after S3 with VMD mode is on. [Fix] Intel provides a fix and still under discussion https://patchwork.kernel.org/project/linux-pci/patch/20221107182735.381552-1-francisco.munoz.r...@linux.intel.com/ Included in v6.2-rc1 d899aa668498 PCI: vmd: Disable MSI remapping after suspend [Test] Verified by us and ODM. [Where problems could occur] The VMCONFIG_MSI_REMAP bit is missing after S3, set it back won't lead to any regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1996048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003161] Re: Fix speaker mute hotkey doesn't work on Dell G16 series
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2003161 Title: Fix speaker mute hotkey doesn't work on Dell G16 series Status in HWE Next: New Status in HWE Next lunar series: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.0 source package in Kinetic: New Status in linux-oem-6.1 source package in Kinetic: New Status in linux source package in Lunar: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Speaker mute and Mic mute hotkey no function on the G16. [Fix] speaker mute event is sent by EC then dell-wmi can't recognize it. Add a new keymap for KEY_MUTE. Send for OEM kernels first then will SRU for generic kernel once the patch is merged. [Test Case] 1. boot-up with the kernel applied the fix. 2. Play video/audio. 3. Press the speak-mute hotkey 4. can't hear any sounds. [Where problems could occur] Low, only add a keymap the affect would be very limited. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2003161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003816] Re: Regression in ext4 during online resize
This bug is awaiting verification that the linux-azure/5.15.0-1036.43 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux-azure verification-needed-jammy -- 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/2003816 Title: Regression in ext4 during online resize Status in cloud-init package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Invalid Status in cloud-init source package in Jammy: Confirmed Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in cloud-init source package in Kinetic: Invalid Status in linux source package in Kinetic: Fix Committed Status in linux-aws source package in Kinetic: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Status in linux-gcp source package in Kinetic: Fix Committed Bug description: Issue resize2fs utility is used to resize the filesystem and is idempotent in nature. But in the 5.15 kernel, successive execution of resize2fs is returning error. Reproduction step (on AWS): Create an AWS instance with AMI ami-056a67ea1b8ffa0fc (Linux 5.15.0-1022-aws) in us-west-2 region and attach an EBS volume. Format and mount the disk - sudo mkfs.ext4 /dev/xvdb, sudo mkdir -p /mnt/ssd0, sudo mount /dev/xvdb /mnt/ssd0 Increase the size of EBS volume. Run sudo resize2fs /dev/xvdb multiple times. The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) The filesystem is already 5242880 (4k) blocks long. Nothing to do! When you run the same step on the latest image ami-0a1d6d351894df6cc (Linux 5.15.0-1026-aws). The first execution returns - $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) Filesystem at /dev/xvdb is mounted on /mnt/ssd0; on-line resizing required old_desc_blocks = 2, new_desc_blocks = 3 The filesystem on /dev/xvdb is now 5242880 (4k) blocks long. The following execution returns $ sudo resize2fs /dev/xvdb resize2fs 1.45.5 (07-Jan-2020) resize2fs: Superblock checksum does not match superblock while trying to open /dev/xvdb Couldn't find valid filesystem superblock. FIX: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=a408f33e895e455f16cf964cb5cd4979b658db7b To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2003816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
