[Kernel-packages] [Bug 1980831] Re: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out!
If it helps at all, I also have my laptop connected to a Samsung monitor via a USB Type C port which it receives the video and charging signal. As this article also mentions: https://gitlab.freedesktop.org/drm/amd/-/issues/2282 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/1980831 Title: GUI freezes randomly, kernel: [drm:amdgpu_dm_commit_planes [amdgpu]] *ERROR* Waiting for fences timed out! Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.19 package in Ubuntu: Confirmed Bug description: When working normally, random freezes happen. Everything freezes, except the mouse cursor. I tried from keyboard to: switch to another window, start a terminal, run a command to restart gnome, enabled ctrl+alt+backspace and tried it to restart X windows, ctrl+alt+delete, switch to another session with ctrl+alt+F1-F9 - nothing works. If I'm listening to something, the sound goes on for a while; sometimes it stops by itself, other times it keeps going. The only way to recover that I've found is to stop the laptop from the power button. For a while I thought it was due to firefox; I installed the deb version and then switched to chrome - same behavior. It didn't happen when I was playing Hollow Knight in Steam, or when I've used the terminal and nothing else. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:27:36 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-06-16 (19 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1980831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/5.19.0-37.38)
All autopkgtests for the newly accepted linux-restricted-modules (5.19.0-37.38) for kinetic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-390/390.157-0ubuntu0.22.10.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/kinetic/update_excuses.html#linux-restricted-modules [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 2007516] Re: screen flicker after PSR2 enabled
Kernel 5.19.0-3035-generic x86_64 has good behavior. I have not seen the artifacts with this version while performing the typical workflow that normally caused it to manifest. https://people.canonical.com/~khfeng/lp2002986-2/ -- 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/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008142] Re: bcmwl driver not installed
broadcom-sta-dkms can be found on the ISO pool on both lunar-desktop and lunar-desktop-legacy. In the live session, "ubuntu-drivers install" reports that "All the available drivers are already installed", but broadcom-sta-dkms isn't installed. "ubuntu-drivers debug" reports broadcom-sta-dkms as needed. manual installation of broadcom-sta-dkms does complete but the system still has no wireless interface and dmesg reports that 'wl: module verification failed: signature and/or required key missing - tainting kernel'. The reconfigure/kmodsign/modprobe workaround in https://discourse.ubuntu.com/t/dkms-package-support-extra-drivers-does- not-work-in-ubuntu-22-10-install-media/31655 does result in a loadable driver but not a wireless interface. Am I missing something? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: New Status in broadcom-sta package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in broadcom-sta source package in Lunar: New Status in subiquity source package in Lunar: New Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008142] Re: bcmwl driver not installed
** Also affects: broadcom-sta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to broadcom-sta in Ubuntu. https://bugs.launchpad.net/bugs/2008142 Title: bcmwl driver not installed Status in ubuntu-desktop-installer: New Status in broadcom-sta package in Ubuntu: New Status in subiquity package in Ubuntu: New Status in broadcom-sta source package in Lunar: New Status in subiquity source package in Lunar: New Bug description: I was testing an installation in qemu and shared a broadcom wireless device with the virtual machine and the drivers for it were not installed. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-desktop-installer (not installed) ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Feb 22 16:23:38 2023 InstallationDate: Installed on 2023-02-23 (0 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230221) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-desktop-installer UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2008142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007331] Please test proposed package
Hello Kai-Heng, or anyone else affected, Accepted pulseaudio into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:15.99.1+dfsg1-1ubuntu2.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-jammy. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Committed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
Hello Kai-Heng, or anyone else affected, Accepted pulseaudio into kinetic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:16.1+dfsg1-1ubuntu3.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- kinetic to verification-done-kinetic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-kinetic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pulseaudio (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-kinetic ** Changed in: pulseaudio (Ubuntu Lunar) Status: Confirmed => Fix Committed ** Changed in: pulseaudio (Ubuntu Jammy) Status: Confirmed => Fix Committed -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Fix Committed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Fix Committed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Fix Committed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/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 Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed 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/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/1814234 Title: rtcpie in timers from ubuntu_kernel_selftests randomly failing Status in ubuntu-kernel-tests: Invalid Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed 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 1968310] Re: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/1968310 Title: arp_ndisc_evict_nocarrier.sh in net from ubuntu_kernel_selftests failed on J-oem-5.17 / K Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.17 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-hwe-5.17 source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-hwe-5.17 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] In selftests: net: arp_ndisc_evict_nocarrier.sh, even all of the sub-tests from this script have passed, the overall test result is still a fail. # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 This is caused by the cleanup() in the script, as it's trying to access a non-existing file. [Fix] * 9c4d7f45d6 selftests: net: fix cleanup_v6() for arp_ndisc_evict_nocarrier This patch can be cherry-picked into all affected kernels. [Test] Run the patched test and the test will pass. [Where problems could occur] Change limited to testing tools, no impact to real kernel function or test performances. [Original Bug Report] Issue found on Jammy OEM 5.17.0-1003.3 It looks like all the sub-tests has passed, but the final return value is not 0. Running 'make run_tests -C net TEST_PROGS=arp_ndisc_evict_nocarrier.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: arp_ndisc_evict_nocarrier.sh # run arp_evict_nocarrier=1 test # ok # run arp_evict_nocarrier=0 test # ok # run all.arp_evict_nocarrier=0 test # ok # run ndisc_evict_nocarrier=1 test # ok # run ndisc_evict_nocarrier=0 test # ok # run all.ndisc_evict_nocarrier=0 test # ok not ok 1 selftests: net: arp_ndisc_evict_nocarrier.sh # exit=255 make: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1968310/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1981773] Re: Make cm32181 sensor work after system suspend
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1981773 Title: Make cm32181 sensor work after system suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 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 Committed Status in linux-oem-5.14 source package in Kinetic: Invalid Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] cm32181 ambient light sensor stops working after system suspend. [Fix] Add PM support for cm32181 so it can work after system suspend. [Test] The sysfs in_illuminance_input continues to change after system suspend. [Where problems could occur] This changeset is limited to a specific device, and it already lacks PM support - so the worst case is that it stops working after resume like it always has been. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1981773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991366] Re: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/1991366 Title: Fix Thunderbolt device hotplug fail when connect via thunderbolt dock Status in HWE Next: New Status in linux package in Ubuntu: Triaged 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 Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] Some Dell laptops where booting with Thunderbolt/USB4 devices connected the BIOS leaves some of the PCIe devices unconfigured. The kernel message shows "No bus number available for hot-added bridge". The connected devices can't be found. [Fix] Current linux PCI distribute the "spare" resources between hotplug ports on hot-add but have not done that upon the initial scan. The patches make the initial root bus scan path to do the same. The additional patches are just a small cleanups that can be applied separately too. [Test] 1. Power on the machine with Thunderbolt/USB4 devices connected. 2. Check the kernel message to see if "No bus number available for hot-added bridge" shows up or not. 3. Check if the Thunderbolt/USB4 devices works or not. [Where problems could occur] The patches only apply the same procedures on initial root bus scan which was not done. If the BIOS configures the PCI correctly, everything is OK. It only takes effect for the BIOS w/ unconfigured PCIe devices. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1991366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/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: In Progress 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 Committed 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 Committed 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: In Progress 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&HDMI 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 2000708] Re: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper)
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/2000708 Title: udpgro_frglist.sh in net from ubuntu_kernel_selftests failed with K-5.19 (Missing nat6to4 helper) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: In Progress Bug description: Issue found with 5.19.0-28.29 Running 'make run_tests -C net TEST_PROGS=udpgro_frglist.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: udpgro_frglist.sh # Missing nat6to4 helper. Build bpfnat6to4.o selftest first not ok 1 selftests: net: udpgro_frglist.sh # exit=255 This is not a regression as the net test build was blocked with bug 1993155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/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 Committed 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 Committed 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 2000709] Re: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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/2000709 Title: net:cmsg_ipv6.sh from ubuntu_kernel_selftests failed with K-5.19 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Kinetic: Fix Committed Bug description: Issue found with 5.19.0-28.29 Running 'make run_tests -C net TEST_PROGS=cmsg_ipv6.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: cmsg_ipv6.sh # Case TCLASS UDP setsock - packet data returned 1, expected 0 # Case TCLASS ICMP setsock - packet data returned 1, expected 0 # Case TCLASS RAW setsock - packet data returned 1, expected 0 # Case TCLASS UDP cmsg - packet data returned 1, expected 0 # Case TCLASS ICMP cmsg - packet data returned 1, expected 0 # Case TCLASS RAW cmsg - packet data returned 1, expected 0 # Case TCLASS UDP both - packet data returned 1, expected 0 # Case TCLASS ICMP both - packet data returned 1, expected 0 # Case TCLASS RAW both - packet data returned 1, expected 0 # Case TCLASS UDP diff - packet data returned 1, expected 0 # Case TCLASS ICMP diff - packet data returned 1, expected 0 # Case TCLASS RAW diff - packet data returned 1, expected 0 # Case HOPLIMIT UDP setsock - packet data returned 1, expected 0 # Case HOPLIMIT ICMP setsock - packet data returned 1, expected 0 # Case HOPLIMIT RAW setsock - packet data returned 1, expected 0 # Case HOPLIMIT UDP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT ICMP cmsg - packet data returned 1, expected 0 # Case HOPLIMIT RAW cmsg - packet data returned 1, expected 0 # Case HOPLIMIT UDP both - packet data returned 1, expected 0 # Case HOPLIMIT ICMP both - packet data returned 1, expected 0 # Case HOPLIMIT RAW both - packet data returned 1, expected 0 # Case HOPLIMIT UDP diff - packet data returned 1, expected 0 # Case HOPLIMIT ICMP diff - packet data returned 1, expected 0 # Case HOPLIMIT RAW diff - packet data returned 1, expected 0 # FAIL - 24/93 cases failed not ok 1 selftests: net: cmsg_ipv6.sh # exit=1 This is not a regression as the net test build was blocked with bug 1993155 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/2000709/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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 Committed 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 Committed 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 2006391] Re: net:fcnal-test.sh 'nettest' command not found on F/K
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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: In Progress Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Committed Status in linux source package in Kinetic: Fix Committed 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 2006546] Re: Improve arp_ndisc_evict_nocarrier.sh test result processing
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-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 Committed 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 2007516] Re: screen flicker after PSR2 enabled
This bug is awaiting verification that the linux/5.19.0-37.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-kinetic' to 'verification-done-kinetic'. If the problem still exists, change the tag 'verification-needed-kinetic' to 'verification-failed-kinetic'. 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-kinetic-linux verification-needed-kinetic -- 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/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009237] [NEW] Bionic update: upstream stable patchset 2023-03-03
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2023-03-03 Ported from the following upstream stable releases: v4.14.304, v4.19.271 v4.14.305, v4.19.272 from git://git.kernel.org/ pNFS/filelayout: Fix coalescing test for single DS net/ethtool/ioctl: return -EOPNOTSUPP if we have no phy stats RDMA/srp: Move large values to a new enum for gcc13 f2fs: let's avoid panic if extent_tree is not created nilfs2: fix general protection fault in nilfs_btree_insert() xhci-pci: set the dma max_seg_size usb: xhci: Check endpoint is valid before dereferencing it prlimit: do_prlimit needs to have a speculation check USB: serial: option: add Quectel EM05-G (GR) modem USB: serial: option: add Quectel EM05-G (CS) modem USB: serial: option: add Quectel EM05-G (RS) modem USB: serial: option: add Quectel EC200U modem USB: serial: option: add Quectel EM05CN (SG) modem USB: serial: option: add Quectel EM05CN modem USB: misc: iowarrior: fix up header size for USB_DEVICE_ID_CODEMERCS_IOW100 usb: core: hub: disable autosuspend for TI TUSB8041 USB: serial: cp210x: add SCALANCE LPE-9000 device id usb: host: ehci-fsl: Fix module alias usb: gadget: g_webcam: Send color matching descriptor per frame usb: gadget: f_ncm: fix potential NULL ptr deref in ncm_bitrate() usb-storage: apply IGNORE_UAS only for HIKSEMI MD202 on RTL9210 serial: pch_uart: Pass correct sg to dma_unmap_sg() serial: atmel: fix incorrect baudrate setup gsmi: fix null-deref in gsmi_get_variable comedi: adv_pci1760: Fix PWM instruction handling UBUNTU: Upstream stable to v4.14.304, v4.19.271 ARM: dts: imx6qdl-gw560x: Remove incorrect 'uart-has-rtscts' HID: intel_ish-hid: Add check for ishtp_dma_tx_map EDAC/highbank: Fix memory leak in highbank_mc_probe() tomoyo: fix broken dependency on *.conf.default IB/hfi1: Reject a zero-length user expected buffer IB/hfi1: Reserve user expected TIDs affs: initialize fsdata in affs_truncate() amd-xgbe: TX Flow Ctrl Registers are h/w ver dependent phy: rockchip-inno-usb2: Fix missing clk_disable_unprepare() in rockchip_usb2phy_power_on() net: nfc: Fix use-after-free in local_cleanup() net: usb: sr9700: Handle negative len net: mdio: validate parameter addr in mdiobus_get_phy() HID: check empty report_list in hid_validate_values() usb: gadget: f_fs: Prevent race during ffs_ep0_queue_wait usb: gadget: f_fs: Ensure ep0req is dequeued before free_request net: mlx5: eliminate anonymous module_init & module_exit dmaengine: Fix double increment of client_count in dma_chan_get() HID: betop: check shape of output reports w1: fix deadloop in __w1_remove_master_device() w1: fix WARNING after calling w1_process() fs: reiserfs: remove useless new_opts in reiserfs_remount Bluetooth: hci_sync: cancel cmd_timer if hci_open failed scsi: hpsa: Fix allocation size for scsi_host_alloc() module: Don't wait for GOING modules tracing: Make sure trace_printk() can output as soon as it can be used ARM: 9280/1: mm: fix warning on phys_addr_t to void pointer assignment EDAC/device: Respect any driver-supplied workqueue polling value netlink: annotate data races around dst_portid and dst_group netlink: annotate data races around sk_state netfilter: conntrack: fix vtag checks for ABORT/SHUTDOWN_COMPLETE netrom: Fix use-after-free of a listening socket. sctp: fail if no bound addresses can be used for a given scope net: ravb: Fix possible hang if RIS2_QFF1 happen net/tg3: resolve deadlock in tg3_reset_task() during EEH Revert "Input: synaptics - switch touchpad on HP Laptop 15-da3001TU to RMI mode" x86/i8259: Mark legacy PIC interrupts with IRQ_LEVEL xen: Fix up build warning with xen_init_time_ops() reference x86/asm: Fix an assembler warning with current binutils x86/entry/64: Add instruction suffix to SYSRET sysctl: add a new register_sysctl_init() interface panic: unset panic_on_warn inside panic() exit: Add and use make_task_dead. objtool: Add a missing comma to avoid string concatenation hexagon: Fix function name in die() h8300: Fix build errors from do_exit() to make_task_dead() transition ia64: make IA64_MCA_RECOVERY bool instead of tristate exit: Put an upper limit on how often we can oops exit: Expose "oops_count" to sysfs exit: Allow oops_limit to be disabled panic: Consolidate open-coded panic_on_warn checks panic: Introduce warn_limit panic: Expose "warn_count" to sysfs exit: Use READ_ONCE() for all oops/warn limit reads mm: kvmalloc does not fallback to vmalloc for incompatible gfp flags ipv6: ensure sane device mtu in tunnels usb:
[Kernel-packages] [Bug 2009219] Re: Backlight com erro, ajustes de som pelo teclado não funcionam.
Thanks for taking the time to report this bug and helping to make Ubuntu better. Your bug report is more likely to get attention if it is made in English, since this is the language understood by the majority of Ubuntu developers. Additionally, please only mark a bug as "security" if it shows evidence of allowing attackers to cross privilege boundaries or to directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009219 Title: Backlight com erro, ajustes de som pelo teclado não funcionam. Status in linux-signed-hwe-5.19 package in Ubuntu: Incomplete Bug description: Erro nos ajsutes de brilho e som pelo teclado, erro na inicialização em tabelas ACPI sobre backlight PCOO. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 14:52:02 2023 InstallationDate: Installed on 2023-03-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
** Description changed: - I update this morning and ubuntu kernel 5.19.0-35 gives black screen. - It appears to be an issue with graphics as I can access a console and - login. I am able boot with 5.19.0-32-generic. I am using nvidia - drivers. + I updated software this morning and on reboot ubuntu kernel 5.19.0-35 + gives black screen. It appears to be an issue with graphics as I can + access a console and login. I am able boot and run normally with + 5.19.0-32-generic. I am using nvidia drivers. -- 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Incomplete Bug description: I updated software this morning and on reboot ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot and run normally with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1965882] Re: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker)
-- 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/1965882 Title: [nouveau] External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) Status in linux package in Ubuntu: Incomplete Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Incomplete Bug description: External monitor plugged into (secondary) Nvidia GPU is all white (plus a little flicker) for gnome-shell/mutter when using nouveau. The primary GPU (i915) still works fine. This seems to be a kernel regression... FAIL: 5.17.0-051700drmtip20220322-generic FAIL: 5.17.0-051700-generic FAIL: 5.15.0-23-generic FAIL: 5.14.21-051421-generic PASS: 5.14.20-051420-generic PASS: 5.14.18-051418-generic PASS: 5.14.15-051415-generic PASS: 5.14.10-051410-generic PASS: 5.14.0-051400-generic PASS: 5.13.19-051319-generic PASS: 5.10.107-0510107-generic ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-23-generic 5.15.0-23.23 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC1', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Tue Mar 22 16:35:58 2022 InstallationDate: Installed on 2021-11-05 (136 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211103) MachineType: Intel(R) Client Systems NUC9i7QNX ProcFB: 0 i915drmfb 1 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic root=UUID=70e2069c-a553-4c6d-abfc-c65e52cb3b43 ro quiet splash nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-23-generic N/A linux-backports-modules-5.15.0-23-generic N/A linux-firmware 20220314.gitcd01f857-0ubuntu2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: QXCFL579.0034.2019.1125.1436 dmi.board.name: NUC9i7QNB dmi.board.vendor: Intel Corporation dmi.board.version: K49245-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.ec.firmware.release: 24.33 dmi.modalias: dmi:bvnIntelCorp.:bvrQXCFL579.0034.2019.1125.1436:bd11/25/2019:br5.13:efr24.33:svnIntel(R)ClientSystems:pnNUC9i7QNX:pvrK49244-403:rvnIntelCorporation:rnNUC9i7QNB:rvrK49245-402:cvnIntelCorporation:ct35:cvr2.0:skuBXNUC9i7QNX: dmi.product.family: QN dmi.product.name: NUC9i7QNX dmi.product.sku: BXNUC9i7QNX dmi.product.version: K49244-403 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965882/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-gcp/5.4.0-1102.111)
All autopkgtests for the newly accepted linux-restricted-modules-gcp (5.4.0-1102.111) 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-gcp [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 2009226] 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 2009226 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/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: Incomplete Bug description: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009226] Re: updating to ubuntu kernel 5.19.0-35 gives black screen
I am not running in problematic update but I have attached sudo lspci -vnvn > lspci-vnvn.log ** Attachment added: "output of sudo lspci -vnvn > lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+attachment/5651446/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: New Bug description: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009226] [NEW] updating to ubuntu kernel 5.19.0-35 gives black screen
Public bug reported: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009226 Title: updating to ubuntu kernel 5.19.0-35 gives black screen Status in linux package in Ubuntu: New Bug description: I update this morning and ubuntu kernel 5.19.0-35 gives black screen. It appears to be an issue with graphics as I can access a console and login. I am able boot with 5.19.0-32-generic. I am using nvidia drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009226/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009222] [NEW] package nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned erro
Public bug reported: Sorry, just found a crash dialog sitting behind other windows ProblemType: Package DistroRelease: Ubuntu 22.10 Package: nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 Uname: Linux 6.1.14-x64v2-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 AptOrdering: nvidia-dkms-470:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 27 10:08:29 2023 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2017-12-06 (1913 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to kinetic on 2022-11-07 (116 days ago) ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package kinetic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/2009222 Title: package nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Sorry, just found a crash dialog sitting behind other windows ProblemType: Package DistroRelease: Ubuntu 22.10 Package: nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 Uname: Linux 6.1.14-x64v2-xanmod1 x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 AptOrdering: nvidia-dkms-470:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Feb 27 10:08:29 2023 ErrorMessage: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2017-12-06 (1913 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal, 3.10.6-1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9 RelatedPackageVersions: dpkg 1.21.9ubuntu1 apt 2.5.3 SourcePackage: nvidia-graphics-drivers-470 Title: package nvidia-dkms-470 470.161.03-0ubuntu0.22.10.1 failed to install/upgrade: installed nvidia-dkms-470 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to kinetic on 2022-11-07 (116 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/2009222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009219] [NEW] Backlight com erro, ajustes de som pelo teclado não funcionam.
Public bug reported: Erro nos ajsutes de brilho e som pelo teclado, erro na inicialização em tabelas ACPI sobre backlight PCOO. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 14:52:02 2023 InstallationDate: Installed on 2023-03-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009219 Title: Backlight com erro, ajustes de som pelo teclado não funcionam. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: Erro nos ajsutes de brilho e som pelo teclado, erro na inicialização em tabelas ACPI sobre backlight PCOO. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Mar 3 14:52:02 2023 InstallationDate: Installed on 2023-03-03 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-oem-6.1/6.1.0-1008.8 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-oem-6.1 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 Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Fix Committed 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 1988346] Re: cm32181 module error blocking suspend
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 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/1988346 Title: cm32181 module error blocking suspend Status in linux package in Ubuntu: Confirmed Bug description: After updating to 22.04.1 (from 20.04) suspend gets interrupted and the system returns after a few seconds. journalctl output ``` Aug 31 19:59:32 nmurphy-laptop kernel: PM: suspend entry (deep) Aug 31 19:59:32 nmurphy-laptop kernel: Filesystems sync: 0.044 seconds Aug 31 19:59:37 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.002 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:37 nmurphy-laptop kernel: Freezing remaining freezable tasks ... (elapsed 3.894 seconds) done. Aug 31 19:59:37 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:37 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:37 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:37 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:37 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:37 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:37 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:37 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:37 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:37 nmurphy-laptop kernel: PM: suspend entry (s2idle) Aug 31 19:59:37 nmurphy-laptop kernel: Filesystems sync: 0.051 seconds Aug 31 19:59:44 nmurphy-laptop kernel: Freezing user space processes ... (elapsed 0.005 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer disabled. Aug 31 19:59:44 nmurphy-laptop kernel: Freezing remaining freezable tasks ... Aug 31 19:59:44 nmurphy-laptop kernel: psmouse serio2: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 Aug 31 19:59:44 nmurphy-laptop kernel: input: TPPS/2 IBM TrackPoint as /devices/rmi4-00/rmi4-00.fn03/serio2/input/input196 Aug 31 19:59:44 nmurphy-laptop kernel: (elapsed 6.917 seconds) done. Aug 31 19:59:44 nmurphy-laptop kernel: printk: Suspending console(s) (use no_console_suspend to debug) Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache Aug 31 19:59:44 nmurphy-laptop kernel: PM: dpm_run_callback(): acpi_subsys_suspend+0x0/0x60 returns -121 Aug 31 19:59:44 nmurphy-laptop kernel: cm32181 i2c-CPLM3218:00: PM: failed to suspend: error -121 Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Stopping disk Aug 31 19:59:44 nmurphy-laptop kernel: PM: Some devices failed to suspend, or early wake event detected Aug 31 19:59:44 nmurphy-laptop kernel: sd 0:0:0:0: [sda] Starting disk Aug 31 19:59:44 nmurphy-laptop kernel: tpm tpm0: TPM is disabled/deactivated (0x6) Aug 31 19:59:44 nmurphy-laptop kernel: OOM killer enabled. Aug 31 19:59:44 nmurphy-laptop kernel: Restarting tasks ... done. Aug 31 19:59:44 nmurphy-laptop kernel: PM: suspend exit Aug 31 19:59:44 nmurphy-laptop systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully. Aug 31 19:59:44 nmurphy-laptop bluetoothd[1129]: Controller resume with wake event 0x0 Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65536]: Failed to put system to sleep. System resumed again: Remote I/O error Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: /dev/sda: Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: setting Advanced Power Management level to 0xfe (254) Aug 31 19:59:44 nmurphy-laptop systemd-sleep[65624]: APM_level= 254 Aug 31 19:59:44 nmurphy-laptop NetworkManager[1131]: [1661972384.8203] audit: op="radio-control" arg="wwan-enabled:off" pid=65646 uid=0 result="success" Aug 31 19:59:44 nmurphy-laptop systemd[1]: systemd-suspend.service: Main proces
[Kernel-packages] [Bug 1999375] Re: Update dg2_dmc to 2.08
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 verification-needed-jammy -- 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/1999375 Title: Update dg2_dmc to 2.08 Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: Invalid Status in linux-firmware source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] i915/dg2 needs this new firmware version to fix some undisclosed bugs The kernel commit is in 6.2 and up, so lunar should eventually be covered once it moves to it. [Test case] Boot a system with the new firmware and a kernel that uses it, and check that the correct version is loaded. [Where things could go wrong] If the kernel is updated before the firmware is available, then loading i915 fails as it can't find the firmware it requires. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1999375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2003053] Re: NFS: client permission error after adding user to permissible group
This bug is awaiting verification that the linux-bluefield/5.4.0-1059.65 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-bluefield -- 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/2003053 Title: NFS: client permission error after adding user to permissible group Status in linux package in Ubuntu: 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 Committed Bug description: [Impact] The NFS client's access cache becomes stale due to the user's group membership changing on the server after the user has already logged in on the client. The access cache only expires if either NFS_INO_INVALID_ACCESS flag is on or timeout (without delegation). Adding a user to a group in the NFS server will not cause any file attributes to change. The client will encounter permission errors until other file attributes are changed or the memory cache is dropped. [Fix] The access cache shall be cleared once the user logs out and logs back in again. 0eb43812c0270ee3d005ff32f91f7d0a6c4943af NFS: Clear the file access cache upon login 029085b8949f5d269ae2bbd14915407dd0c7f902 NFS: Judge the file access cache's timestamp in rcu path 5e9a7b9c2ea18551759833146a181b14835bfe39 NFS: Fix up a sparse warning [Test Plan] 1.[client side] testuser is not part of testgroup testuser@kinetic:~$ ls -ld /mnt/private/ drwxrwx--- 2 root testgroup 4096 Nov 24 08:23 /mnt/private/ testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied 2.[server side] add testuser into testgroup, which has access to folder root@kinetic:~$ usermod -aG testgroup testuser && echo `date +'%s'` > /proc/net/rpc/auth.unix.gid/flush 3.[client side] create a file again but still fail testuser@kinetic:~$ mktemp -p /mnt/private/ mktemp: failed to create file via template ‘/mnt/private/tmp.XX’: Permission denied [Where problems could occur] The fix will apply upstream commits, so the regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2003053/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2002889] Re: 5.15.0-58.64 breaks xen bridge networking (pvh domU)
This bug is awaiting verification that the linux-bluefield/5.4.0-1059.65 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-bluefield -- 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/2002889 Title: 5.15.0-58.64 breaks xen bridge networking (pvh domU) Status in linux package in Ubuntu: Confirmed 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 Bug description: [Impact] Xen guests will not have network access. This fixes a regression due to the fix for CVE-2022-3643. [Testing] This has only been build-tested. [Potential regression] Xen guests might not have network access. -- With 5.15.0-58.64-generic, bridge networking on xen is broken : no packet (check with tcpdump) flowing between dom0 and any domUs attached to a network bridge. downgrading to 5.15.0-57-generic fix the issue. Thus the patch to the netback driver seems the cause. relevant network config : brtctl show : br0 8000.XXXno eno1 vif1.0 relevant domU config : kernel = '/usr/lib/grub-xen/grub-i386-xen_pvh.bin' type = 'pvh' vif = [ 'ip=192.168.10.10 ,bridge=br0' ] No message in dmesg, journal, xen logs.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002889/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2006945] Re: New DG2 workarounds
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 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/2006945 Title: New DG2 workarounds Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Bug description: [Impact] These are hw revision based workarounds from 6.2 that need to be backported for Intel Arc/DG2. [Test case] We don't have known issues that these would fix, but check that things still work normally. [Where things could go wrong] these are limited to a very specific type of hardware, so can't think of what could go wrong To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2006945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007331] Re: Fix HFP mSBC support on Realtek Bluetooth USB controller
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 verification-needed-jammy -- 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/2007331 Title: Fix HFP mSBC support on Realtek Bluetooth USB controller Status in HWE Next: New Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Confirmed Status in linux-oem-6.0 source package in Jammy: Confirmed Status in linux-oem-6.1 source package in Jammy: Confirmed Status in pulseaudio source package in Jammy: Confirmed Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in pulseaudio source package in Kinetic: Confirmed Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in pulseaudio source package in Lunar: Confirmed Bug description: [Impact] When a BT headset is connected Realtek BT USB controller, HFP profile can't play or record sound when mSBC codec is used. [Fix] At Linux kernel side, add a Realtek specific quirk to support mSBC. At PulseAudio side, send more data frames until the connected device sends response. [Test] Connect different headsets to the said controller, HFP can play and record sounds now. Also verified A2DP profile is unaffected. [Where problems could occur] The kernel part is Realtek specific, so the regression risk is very limited. The pulseaudio side only affects HFP profile, since the codeflow only changes when a mic is present. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007331/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007516] Re: screen flicker after PSR2 enabled
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 verification-needed-jammy -- 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/2007516 Title: screen flicker after PSR2 enabled Status in HWE Next: New Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: The screen flicker after ubuntu jammy upgrade kernel to 5.19. The enable_psr2_sel_fetch was disabled in 5.15 kernel but enabled in 5.19 kernel. I try to add "options i915 enable_psr2_sel_fetch=0" to modprobe config can omit the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2007516/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008871] Re: Screen backlight keeps in minimized and can't change it with amdgpu
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 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/2008871 Title: Screen backlight keeps in minimized and can't change it with amdgpu Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: In Progress Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Sometimes the system boots up with both acpi_video0 and amdgpu_bl0 sysfs interfaces and the acpi_video0 doesn't work. [Fix] Add this machine to the video_detect_dmi_table to force it uses native backlight interface which is amdgpu_bl0. https://lkml.org/lkml/2023/3/2/187 [Verify] Verified by our QA and ODM. [Where problems could occur] Pretty safe to add the DMI quirk, won't affect other platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008882] Re: Remove all other acpi_video backlight interface on Dell AIO platforms
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8
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-oem-6.1 verification-needed-jammy
--
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/2008882
Title:
Remove all other acpi_video backlight interface on Dell AIO platforms
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-oem-6.1 source package in Jammy:
In Progress
Status in linux source package in Lunar:
In Progress
Status in linux-oem-6.1 source package in Lunar:
Invalid
Bug description:
[Impact]
There are acpi_video* sysfs backlight interface in the system which are not
working.
For Dell AIO platforms, we use dell_uart_backlight to control the display
brightness.
The old way to fix this is to unregister acpi backlight interfaces in the
backlight driver, but it may lead to some issues and the unregister function
has been removed since v6.1-rc1
77ab9d4d44cd ("ACPI: video: Remove acpi_video_set_dmi_backlight_type()")
[Fix]
The new way to do this is to collect all the quirk and auto detection method
in video_detect.c
I added an audo detection for the Dell AIO platoform to the driver which
should do the same thing as the old way.
[Test]
Verified on the Dell AIO platform and confirmed there is only on
dell_uart_backlight in the sysfs, and no acpi_video* interface.
[Where problems could occur]
There should be no regression potential, it uses different way to do the same
thing, should be pretty safe.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2008882/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009014] Re: Some QHD panels fail to refresh when PSR2 enabled
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 verification-needed-jammy -- 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/2009014 Title: Some QHD panels fail to refresh when PSR2 enabled Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux source package in Kinetic: Confirmed Status in linux-oem-6.1 source package in Kinetic: Invalid Bug description: [Impact] Some QHD (2560x1440) panels which support PSR2 refresh the display abnormally. The display frequently stop responding for few seconds on all user interactions, ex. mouse movement, TTY and any APP GUI. There's no problem on the external monitor. After disabling PSR, the problem will be gone. [Fix] Intel release a fix to calculate the wake up line count and configure them into PSR2_CTL accordingly. [Test] Verified on the problematic panels to check if the display responds smoothly to mouse movement. [Where problems could occur] Only affects the panels on some particular panels which supports PSR2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009014/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8
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-oem-6.1 verification-needed-jammy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1&id=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(&init_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
This bug is awaiting verification that the linux-oem-6.1/6.1.0-1008.8 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-oem-6.1 verification-needed-jammy -- 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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-lowlatency/5.15.0-68.75)
All autopkgtests for the newly accepted linux-restricted-modules-lowlatency (5.15.0-68.75) 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-lowlatency [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 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.19 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
Here are the binary dump of the smbios type 9 for one of the slots, as well as the decoded information and the appropriate section in the spec. I have also attached a copy of the spec in a previous comment. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
** Attachment added: "dmidecode-3.png" https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651414/+files/dmidecode-3.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
** Attachment added: "dmidecode-2.png" https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651413/+files/dmidecode-2.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
** Attachment added: "dmidecode-1.png" https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+attachment/5651412/+files/dmidecode-1.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2004493] Re: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration
HI Mauricio, The following command did not work : sudo apt install --allow-downgrades dmidecode/jammy-updates I was able to download and install dmidecode 3.4 to my jammy instance. I checked the version with dmidecode --v and it stated 3.4. I uploaded my updates bios with slot information, slot pitch and slot width, and checked with the two commands below: $sudo dmidecode -t 9 |more $sudo dmidecode -t 9 -u |more The "-u" command confirmed that the last 5 bytes in the Header and Data hex info were 05 0A A2 03 00 for the E3 PCIe5 drives. However, dmidecode confirmed they were x4 EDSFF E3 drives under slot type and that they were SHort under Length. However, It was missing the additional information to designate the generation and slot pitch/width of the drives. I'll attach screenshots so that you can see what I'm talking about. Can you add these items so that they can match the spec, please. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/2004493 Title: dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration Status in dmidecode package in Ubuntu: Incomplete Bug description: For EDSFF slot type changes no longer indicate the PCIe Generation supported nor do they indicate the full formfactor. To accomodate this severa sections have been added in the spec as follows 7.10.10 System Slots — Slot Information , 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch , 7.10.13 System Slots — Slot Height. Currently they do no show up in the dmidecode 3.3 / Jammy Untested on Kinetic. This is related to a previous bug as well. https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/2004493/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] Re: Fix screen that remains blank forever after it gets locked
** Tags added: oem-priority originate-from-2006667 stella -- 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/2009164 Title: Fix screen that remains blank forever after it gets locked Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009070] Re: [request] Promote module br_netfilter from extras to main
** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2009070 Title: [request] Promote module br_netfilter from extras to main Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: New Status in linux-raspi source package in Jammy: New Status in linux-raspi source package in Kinetic: New Status in linux-raspi source package in Lunar: Confirmed Bug description: MicroK8s has a requirement for the kernel module `br_netfilter` so that it can properly set up all networking related configurations and get a functioning Kubernetes cluster. In Raspberry Pi, this kernel module is part of the extra modules package and not part of main. This leads to two issues: - People installing MicroK8s on a fresh Raspberry Pi install get a non-working Kubernetes cluster, and it's not a great experience having to manually install extra kernel modules for things to work correctly. - Currently, Ubuntu Core does not support loading external kernel modules at all, so it is a hard blocker for running MicroK8s on Ubuntu Core on Raspberry Pi. As such, we want to request that the `br_netfilter` module is promoted from extras to main, so that it is available by default on new installs and get a better out of the box experience. Further, it will unblock people trying out MicroK8s with Ubuntu Core on Rasbperry Pi. Finally, it is worth noting that br_netfilter is part of the main modules in amd64 kernels. As far as the MicroK8s team is concerned, we would like this change to be available primarly in LTS kernels (22.04, 20.04) but also in normal releases (i believe 22.10 and 23.04 would be enough). Happy to provide more details or information if needed, and test any potential builds. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2009070/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009164] [NEW] Fix screen that remains blank forever after it gets locked
Public bug reported: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Medium -- 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/2009164 Title: Fix screen that remains blank forever after it gets locked Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Bug description: [Impact] Once screen is locked under gnome-shell, the screen never wakes up and remains in blank forever. [Fix] "drm/i915: Create resized LUTs for ivb+ split gamma mode" makes gamma LUT operations in atomic context, so userspace can no longer misuse libdrm. "drm/i915: Rework legacy LUT handling" starts to use the reworked gamma LUT. Pull the whole series and series they depends upon to properly support gamma LUT. [Test] The easier way to reproduce the issue is to 1) Login under Wayland 2) Logout and login under X 3) Go back to wayland 4) Super + L to screenlock With the LUT reworked series applied, screen can always come back alive. [Where problems could occur] Regression can happen on refactoring patches with "no functional change intended", let alone overhauls like this one. So only OEM-6.1 and Unstable are targeted to contain the potential regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009164/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009163] 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/2009163 Title: package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: doing apt update and got this. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yoel 2293 F wireplumber /dev/snd/seq:yoel 2290 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Mar 3 08:55:03 2023 ErrorMessage: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-24 (98 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha arm64 (20221124) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=7dcd8379-b84f-4277-9b50-b8b3e9d693b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: Fri, 10 Feb 2023 10:16:42 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 18.2.0 (53488) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009163/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009163] [NEW] package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess
Public bug reported: doing apt update and got this. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yoel 2293 F wireplumber /dev/snd/seq:yoel 2290 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Mar 3 08:55:03 2023 ErrorMessage: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-24 (98 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha arm64 (20221124) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=7dcd8379-b84f-4277-9b50-b8b3e9d693b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) acpidump: dmi.bios.date: Fri, 10 Feb 2023 10:16:42 dmi.bios.release: 0.1 dmi.bios.vendor: Parallels International GmbH. dmi.bios.version: 18.2.0 (53488) dmi.board.asset.tag: None dmi.board.name: Parallels ARM Virtual Platform dmi.board.vendor: Parallels ARM Virtual Machine dmi.board.version: 0.1 dmi.chassis.type: 2 dmi.chassis.vendor: Parallels International GmbH. dmi.modalias: dmi:bvnParallelsInternationalGmbH.:bvr18.2.0(53488):bdFri,10Feb2023101642:br0.1:svnParallelsInternationalGmbH.:pnParallelsARMVirtualMachine:pvr0.1:rvnParallelsARMVirtualMachine:rnParallelsARMVirtualPlatform:rvr0.1:cvnParallelsInternationalGmbH.:ct2:cvr:skuParallels_ARM_VM: dmi.product.family: Parallels VM dmi.product.name: Parallels ARM Virtual Machine dmi.product.sku: Parallels_ARM_VM dmi.product.version: 0.1 dmi.sys.vendor: Parallels International GmbH. modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-package arm64 lunar -- 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/2009163 Title: package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Confirmed Bug description: doing apt update and got this. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.1.0-16-generic 6.1.0-16.16 ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7 Uname: Linux 5.19.0-21-generic aarch64 NonfreeKernelModules: prl_fs_freeze prl_fs prl_tg ApportVersion: 2.26.0-0ubuntu2 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yoel 2293 F wireplumber /dev/snd/seq:yoel 2290 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Fri Mar 3 08:55:03 2023 ErrorMessage: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-11-24 (98 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha arm64 (20221124) IwConfig: lono wireless extensions. enp0s5no wireless extensions. MachineType: Parallels International GmbH. Parallels ARM Virtual Machine ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-21-generic root=UUID=7dcd8379-b84f-4277-9b50-b8b3e9d693b8 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux Title: package linux-headers-6.1.0-16-generic 6.1.0-16.16 failed to install/upgrade: installed linux-headers-6.1.0-16-generic package post-installation script subprocess returned error exit status
[Kernel-packages] [Bug 2009161] [NEW] package libnvidia-compute-418-server (not installed) failed to install/upgrade: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubu
Public bug reported: can not open software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-418-server (not installed) ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 3 21:43:54 2023 ErrorMessage: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubuntu5.20.04.2 InstallationDate: Installed on 2023-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-418-server Title: package libnvidia-compute-418-server (not installed) failed to install/upgrade: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubuntu5.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-418-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418-server in Ubuntu. https://bugs.launchpad.net/bugs/2009161 Title: package libnvidia-compute-418-server (not installed) failed to install/upgrade: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia- ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubuntu5.20.04.2 Status in nvidia-graphics-drivers-418-server package in Ubuntu: New Bug description: can not open software ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-418-server (not installed) ProcVersionSignature: Ubuntu 5.15.0-67.74~20.04.1-generic 5.15.85 Uname: Linux 5.15.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Mar 3 21:43:54 2023 ErrorMessage: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubuntu5.20.04.2 InstallationDate: Installed on 2023-03-03 (0 days ago) InstallationMedia: Ubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 (20220831) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: nvidia-graphics-drivers-418-server Title: package libnvidia-compute-418-server (not installed) failed to install/upgrade: 正试图覆盖 /usr/lib/x86_64-linux-gnu/libnvidia-ml.so，它同时被包含于软件包 nvidia-340 340.108-0ubuntu5.20.04.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418-server/+bug/2009161/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i
This is a completely different problem. Please open a new bug by running 'ubuntu-bug linux-firmware'. -- 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/1969966 Title: No support for Intel Killer AX1675i Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried with 5.18rc1 but no change --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-26 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 20220329.git681281e4-0ubuntu1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. Tags: jammy Uname: Linux 5.17.4-051704-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2
** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009142 Title: nvidia-dkms-390 FTBS with linux 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1969966] Re: No support for Intel Killer AX1675i
Hello everyone I was also getting the following error: ``` Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) ``` I have noticed that the `ibt-19-0-3.sfi` file is not present on the system. As I was unable to find it anywhere on the Internet, I did the following: ``` ln -s /lib/firmware/intel/ibt-19-0-4.ddc /lib/firmware/intel/ibt-19-0-3.ddc ln -s /lib/firmware/intel/ibt-19-0-4.sfi /lib/firmware/intel/ibt-19-0-3.sfi reboot ``` After that, my bluetooth started working! (as far as I can tell, I've just done it, cannot tell you anything about stability) I hope it helps! -- 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/1969966 Title: No support for Intel Killer AX1675i Status in backport-iwlwifi-dkms package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I just installed a Intel Killer AX1675i Wifi+Bluetooth card in my Dell G15 5511 laptop but can't get WiFi or Bluetooth. About WiFi I get these logs: ➜ sudo dmesg|grep wifi -i [4.917786] Loading modules backported from iwlwifi [4.917787] iwlwifi-stack-public:master:9858:4c7cba27 [4.984194] Intel(R) Wireless WiFi driver for Linux [4.985038] iwlwifi :00:14.3: enabling device ( -> 0002) [4.996087] iwlwifi: No config found for PCI dev 43f0/1672, rev=0x351, rfid=0x2010d000 [4.996123] iwlwifi: probe of :00:14.3 failed with error -22 About Bluetooth I get these logs: ➜ sudo dmesg|grep bluetooth -i [4.977780] Bluetooth: Core ver 2.22 [4.977793] NET: Registered PF_BLUETOOTH protocol family [4.977794] Bluetooth: HCI device and connection manager initialized [4.977799] Bluetooth: HCI socket layer initialized [4.977800] Bluetooth: L2CAP socket layer initialized [4.977803] Bluetooth: SCO socket layer initialized [5.002780] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 30 2018 [5.003784] Bluetooth: hci0: Device revision is 0 [5.003787] Bluetooth: hci0: Secure boot is enabled [5.003788] Bluetooth: hci0: OTP lock is enabled [5.003788] Bluetooth: hci0: API lock is enabled [5.003789] Bluetooth: hci0: Debug lock is disabled [5.003789] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [5.006774] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-19-0-3.sfi (-2) [5.007774] Bluetooth: hci0: MSFT supported features length mismatch [7.023197] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.023201] Bluetooth: BNEP filters: protocol multicast [7.023204] Bluetooth: BNEP socket layer initialized I'm in doubt about WiFi, since the message doesn't mention a missing firmware, but Bluetooth is very clear about it. I'm using Ubuntu 22.04 LTS with bleeding edge kernel 5.17.4. I also tried with 5.18rc1 but no change --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Dependencies: firmware-sof-signed 2.0-1ubuntu3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-11-26 (152 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) NonfreeKernelModules: nvidia_modeset nvidia Package: linux-firmware 20220329.git681281e4-0ubuntu1 PackageArchitecture: all RebootRequiredPkgs: Error: path contained symlinks. Tags: jammy Uname: Linux 5.17.4-051704-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to jammy on 2022-02-03 (83 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1969966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp/5.15.0.1031.26)
All autopkgtests for the newly accepted linux-meta-gcp (5.15.0.1031.26) for jammy have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.13.1-1ubuntu0.22.04.3 (amd64, 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-gcp [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 2009141] Re: [UBUNTU 22.04] OS installer exits for zfcp 32G adapter with an unknown error. An error occurred during installation
Please can you check if there is a crash file in /var/crash and if so share this
and ideally the entire /var/log folder (or at least /var/log/installer)? Thx.
We don't have a 32Gbit FCP adapter to test with.
** Package changed: linux (Ubuntu) => subiquity (Ubuntu)
** Also affects: ubuntu-z-systems
Importance: Undecided
Status: New
** Changed in: subiquity (Ubuntu)
Assignee: Skipper Bug Screeners (skipper-screen-team) => (unassigned)
** Changed in: ubuntu-z-systems
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
--
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/2009141
Title:
[UBUNTU 22.04] OS installer exits for zfcp 32G adapter with an unknown
error. An error occurred during installation
Status in Ubuntu on IBM z Systems:
New
Status in subiquity package in Ubuntu:
New
Bug description:
Bug Description:
Installation of Ubuntu 22.04 on s390x failed with an unknown error just after
having successfully activated a zfcp HBA with Fibre-Channel-attached SCSI disks.
I do see 0.0.100d successfully being online and having paths attached:
zfcp-host
0.0.100d online ?
0x500173800cef0111:0x sg16
0x500173800cef0111:0x0001 sdp sg17
0x500173800cef0111:0x0002 sdq sg18
[host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer.txt lines 41-41/9373
byte 238696/1146881 21%]
But immediately after that, the installer reports an error:
An error occurred during installation
??
?subiquity/Early/apply_autoinstall_config
?subiquity/Reporting/apply_autoinstall_config
?subiquity/Error/apply_autoinstall_config
?subiquity/Userdata/apply_autoinstall_config
?subiquity/Package/apply_autoinstall_config
?subiquity/Debconf/apply_autoinstall_config
?subiquity/Kernel/apply_autoinstall_config
?subiquity/Late/apply_autoinstall_config
??
? Sorry, an unknown error occurred. ?
? Information is being collected from the system that will help the ?
? developers diagnose the report. |
It looks like there was some ascii art progress bar while data was
collected and then the dialog updated to:
? [ View full report ]?
? If you want to help improve the installer, you can send an error ?
? report. ?
? [ Send to Canonical ]?
? [ Close report ]|
Next "View full report" was selected?
ProblemType: Bug
Architecture: s390x
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
CurrentDmesg:
[0.093997] Linux version 5.15.0-43-generic (buildd@bos02-s390x-005) (gcc
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#46-Ubuntu SMP Tue Jul 12 12:40:17 UTC 2022 (Ubuntu 5.15.0-43.46-generic
5.15.39)
[0.094001] setup: Linux is running as a z/VM guest operating system in
64-bit mode
[0.360759] Kernel command line:
ip=9.11.116.213::9.11.116.1:255.255.255.0:ilabg13:ence0f:none:9.11.227.25
https://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04.1-live-
server-s39
[ 2677.003438] zfcp 0.0.100d: qdio: ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1
TDD:1 SIGA: W
[ 2677.032397] scsi host0: zfcp
[ 2677.060025] scsi 0:0:0:0: RAID IBM 2810XIV-LUN-0
PQ: 0 ANSI: 5
[ 2677.061
[Kernel-packages] [Bug 2004146] Re: Lunar update: v6.1.7 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Released -- 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/2004146 Title: Lunar update: v6.1.7 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.7 upstream stable release from git://git.kernel.org/ Linux 6.1.7 pinctrl: amd: Add dynamic debugging for active GPIOs Revert "usb: ulpi: defer ulpi_register on ulpi_read_id timeout" block: handle bio_split_to_limits() NULL return io_uring/io-wq: only free worker if it was allocated for creation io_uring/io-wq: free worker if task_work creation is canceled drm/i915: Fix CFI violations in gt_sysfs io_uring/poll: attempt request issue after racy poll wakeup io_uring: lock overflowing for IOPOLL efi: fix NULL-deref in init error path ALSA: usb-audio: Fix possible NULL pointer dereference in snd_usb_pcm_has_fixed_rate() platform/x86/amd: Fix refcount leak in amd_pmc_probe platform/surface: aggregator: Add missing call to ssam_request_sync_free() bnxt: make sure we return pages to the pool net: hns3: fix wrong use of rss size during VF rss config net: lan966x: check for ptp to be enabled in lan966x_ptp_deinit() igc: Fix PPS delta between two synchronized end-points perf kmem: Support field "node" in evsel__process_alloc_event() coping with recent tracepoint restructuring perf kmem: Support legacy tracepoints perf build: Properly guard libbpf includes octeontx2-pf: Fix resource leakage in VF driver unbind selftests/net: l2_tos_ttl_inherit.sh: Ensure environment cleanup on failure. selftests/net: l2_tos_ttl_inherit.sh: Run tests in their own netns. selftests/net: l2_tos_ttl_inherit.sh: Set IPv6 addresses with "nodad". net/mlx5e: Fix macsec possible null dereference when updating MAC security entity (SecY) net/mlx5e: Fix macsec ssci attribute handling in offload path net/mlx5e: Don't support encap rules with gbp option net/mlx5: Fix ptp max frequency adjustment range net/mlx5e: IPoIB, Fix child PKEY interface stats on rx path net/mlx5e: IPoIB, Block PKEY interfaces with less rx queues than parent net/mlx5e: IPoIB, Block queue count configuration when sub interfaces are present net/mlx5e: Verify dev is present for fix features ndo net/mlx5: Fix command stats access after free net/mlx5e: TC, Keep mod hdr actions after mod hdr alloc net/mlx5: check attr pointer validity before dereferencing it Revert "r8169: disable detection of chip version 36" net/sched: act_mpls: Fix warning during failed attribute validation drm/vmwgfx: Remove rcu locks from user resources drm/vmwgfx: Remove vmwgfx_hashtab drm/vmwgfx: Refactor ttm reference object hashtable to use linux/hashtable. drm/vmwgfx: Refactor resource validation hashtable to use linux/hashtable implementation. drm/vmwgfx: Remove ttm object hashtable drm/vmwgfx: Refactor resource manager's hashtable to use linux/hashtable implementation. drm/vmwgfx: Write the driver id registers ice: Add check for kzalloc ice: Fix potential memory leak in ice_gnss_tty_write() drm/amdgpu: Fix potential NULL dereference tools/nolibc: fix the O_* fcntl/open macro definitions for riscv tools/nolibc: restore mips branch ordering in the _start block ASoC: qcom: Fix building APQ8016 machine driver without SOUNDWIRE af_unix: selftest: Fix the size of the parameter to connect() gro: take care of DODGY packets gro: avoid checking for a failed search nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() hvc/xen: lock console list traversal sched/core: Fix arch_scale_freq_tick() on tickless systems octeontx2-af: Fix LMAC config in cgx_lmac_rx_tx_enable nfsd: fix handling of cached open files in nfsd4_open codepath nfsd: rework refcounting in filecache NFSD: Add an nfsd_file_fsync tracepoint nfsd: reorganize filecache.c nfsd: remove the pages_flushed statistic from filecache NFSD: Add an NFSD_FILE_GC flag to enable nfsd_file garbage collection NFSD: Revert "NFSD: NFSv4 CLOSE should release an nfsd_file immediate
[Kernel-packages] [Bug 2004147] Re: Lunar update: v6.1.8 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: Confirmed => Fix Released -- 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/2004147 Title: Lunar update: v6.1.8 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.8 upstream stable release from git://git.kernel.org/ Linux 6.1.8 soc: qcom: apr: Make qcom,protection-domain optional again Revert "wifi: mac80211: fix memory leak in ieee80211_if_add()" block: mq-deadline: Rename deadline_is_seq_writes() net/mlx5: fix missing mutex_unlock in mlx5_fw_fatal_reporter_err_work() octeontx2-pf: Fix the use of GFP_KERNEL in atomic context on rt net/ulp: use consistent error code when blocking ULP octeontx2-pf: Avoid use of GFP_KERNEL in atomic context drm/amdgpu: correct MEC number for gfx11 APUs drm/amdgpu: add tmz support for GC IP v11.0.4 drm/amdgpu: add tmz support for GC 11.0.1 drm/amdgpu: enable GFX Clock Gating control for GC IP v11.0.4 drm/amdgpu: enable GFX Power Gating for GC IP v11.0.4 drm/amdgpu: enable GFX IP v11.0.4 CG support drm/amdgpu: enable PSP IP v13.0.11 support drm/amdgpu/discovery: enable nbio support for NBIO v7.7.1 drm/amdgpu/pm: use the specific mailbox registers only for SMU IP v13.0.4 drm/amdgpu/soc21: add mode2 asic reset for SMU IP v13.0.11 drm/amdgpu/pm: add GFXOFF control IP version check for SMU IP v13.0.11 drm/amdgpu: add smu 13 support for smu 13.0.11 drm/amdgpu/pm: enable swsmu for SMU IP v13.0.11 drm/amdgpu/discovery: add PSP IP v13.0.11 support drm/amdgpu: add gmc v11 support for GC 11.0.4 drm/amdgpu: add gfx support for GC 11.0.4 drm/amdgpu/discovery: set the APU flag for GC 11.0.4 drm/amdgpu: set GC 11.0.4 family drm/amdgpu/discovery: enable mes support for GC v11.0.4 drm/amdgpu/discovery: enable gfx v11 for GC 11.0.4 drm/amdgpu/discovery: enable gmc v11 for GC 11.0.4 drm/amdgpu/discovery: enable soc21 common for GC 11.0.4 x86/fpu: Use _Alignof to avoid undefined behavior in TYPE_ALIGN exit: Use READ_ONCE() for all oops/warn limit reads docs: Fix path paste-o for /sys/kernel/warn_count panic: Expose "warn_count" to sysfs panic: Introduce warn_limit panic: Consolidate open-coded panic_on_warn checks exit: Allow oops_limit to be disabled exit: Expose "oops_count" to sysfs exit: Put an upper limit on how often we can oops panic: Separate sysctl logic from CONFIG_SMP efi: rt-wrapper: Add missing include arm64: efi: Execute runtime services from a dedicated stack fs/ntfs3: Fix attr_punch_hole() null pointer derenference cifs: reduce roundtrips on create/qinfo requests drm/amd/display: disable S/G display on DCN 3.1.4 drm/amd/display: disable S/G display on DCN 3.1.5 drm/amd/display: Fix COLOR_SPACE_YCBCR2020_TYPE matrix drm/amd/display: Calculate output_color_space after pixel encoding adjustment drm/amd/display: Fix set scaling doesn's work drm/i915: Remove unused variable drm/i915: Allow switching away via vga-switcheroo if uninitialized drm/i915/display: Check source height is > 0 drm/i915: re-disable RC6p on Sandy Bridge drm/amdgpu: Correct the power calcultion for Renior/Cezanne. drm/amdgpu: allow multipipe policy on ASICs with one MEC drm/amdgpu: fix amdgpu_job_free_resources v2 ARM: omap1: fix !ARCH_OMAP1_ANY link failures ARM: dts: qcom: apq8084-ifc6540: fix overriding SDHCI VMCI: Use threaded irqs instead of tasklets mei: me: add meteor lake point M DID mei: bus: fix unlink on bus in error path gsmi: fix null-deref in gsmi_get_variable serial: exar: Add support for Sealevel 7xxxC serial cards serial: atmel: fix incorrect baudrate setup serial: amba-pl011: fix high priority character transmission in rs486 mode dmaengine: idxd: Do not call DMX TX callbacks during workqueue disable dmaengine: idxd: Prevent use after free on completion memory dmaengine: idxd: Let probe fail when workqueue cannot be enabled dmaengine: tegra210-adma: fix global intr clear dmaengine: lgm: Move DT parsing after initialization serial: pch_uart: Pass correct sg to dma_unmap_sg(
[Kernel-packages] [Bug 2007583] Re: Jammy update: v6.1.10 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- 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/2007583 Title: Jammy update: v6.1.10 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.10 upstream stable release from git://git.kernel.org/ Linux 6.1.10 net: mctp: purge receive queues on sk destruction rust: print: avoid evaluating arguments in `pr_*` macros in `unsafe` blocks net: fix NULL pointer in skb_segment_list gpiolib-acpi: Don't set GPIOs for wakeup in S3 mode gpiolib: acpi: Add a ignore wakeup quirk for Clevo NL5xRU nvme-apple: only reset the controller when RTKit is running cifs: fix return of uninitialized rc in dfs_cache_update_tgthint() gpiolib: acpi: Allow ignoring wake capability on pins that aren't in _AEI dmaengine: imx-sdma: Fix a possible memory leak in sdma_transfer_init HID: playstation: sanity check DualSense calibration data. HID: uclogic: Add support for XP-PEN Deco 01 V2 s390: workaround invalid gcc-11 out of bounds read warning block: fix hctx checks for batch allocation ACPI: video: Add backlight=native DMI quirk for Acer Aspire 4810T LoongArch: Get frame info in unwind_start() when regs is not available blk-cgroup: fix missing pd_online_fn() while activating policy erofs: clean up parsing of fscache related options kselftest: Fix error message for unconfigured LLVM builds ARM: omap1: fix building gpio15xx arm64: dts: msm8994-angler: fix the memory map mac80211: Fix MLO address translation for multiple bss case erofs/zmap.c: Fix incorrect offset calculation bpf: Skip task with pid=1 in send_signal_common() firmware: arm_scmi: Clear stale xfer->hdr.status arm64: dts: imx8mq-thor96: fix no-mmc property for SDHCI arm64: dts: freescale: Fix pca954x i2c-mux node names ARM: dts: vf610: Fix pca9548 i2c-mux node names ARM: dts: imx: Fix pca9547 i2c-mux node name To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2007583/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2008707] Re: Jammy update: v6.1.13 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux-oem-6.1 (Ubuntu Jammy)
Status: New => Fix Committed
--
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/2008707
Title:
Jammy update: v6.1.13 upstream stable release
Status in linux-oem-6.1 package in Ubuntu:
Invalid
Status in linux-oem-6.1 source package in Jammy:
Fix Committed
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v6.1.13 upstream stable release
from git://git.kernel.org/
Linux 6.1.13
net: sched: sch: Fix off by one in htb_activate_prios()
ASoC: SOF: Intel: hda-dai: fix possible stream_tag leak
nvme-pci: refresh visible attrs for cmb attributes
alarmtimer: Prevent starvation by small intervals and SIG_IGN
perf/x86: Refuse to export capabilities for hybrid PMUs
kvm: initialize all of the kvm_debugregs structure before sending it to
userspace
KVM: x86/pmu: Disable vPMU support on hybrid CPUs (host PMUs)
nvme-rdma: stop auth work after tearing down queues in error recovery
nvme-tcp: stop auth work after tearing down queues in error recovery
net/sched: tcindex: search key must be 16 bits
i40e: Add checking for null for nlmsg_find_attr()
mm: extend max struct page size for kmsan
mm/gup: add folio to list when folio_isolate_lru() succeed
ipv6: Fix tcp socket connection with DSCP.
ipv6: Fix datagram socket connection with DSCP.
ixgbe: add double of VLAN header when computing the max MTU
igb: Fix PPS input and output using 3rd and 4th SDP
igb: conditionalize I2C bit banging on external thermal sensor support
net: mpls: fix stale pointer if allocation fails during device rename
tipc: fix kernel warning when sending SYN message
net: use a bounce buffer for copying skb->mark
net: stmmac: Restrict warning on disabling DMA store and fwd mode
tracing: Make trace_define_field_ext() static
bnxt_en: Fix mqprio and XDP ring checking logic
net: stmmac: fix order of dwmac5 FlexPPS parametrization sequence
net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()
net/sched: act_ctinfo: use percpu stats
net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path
dccp/tcp: Avoid negative sk_forward_alloc by ipv6_pinfo.pktoptions.
ice: xsk: Fix cleaning of XDP_TX frames
net/sched: tcindex: update imperfect hash filters respecting rcu
sctp: sctp_sock_filter(): avoid list_entry() on possibly empty list
net: ethernet: ti: am65-cpsw: Add RX DMA Channel Teardown Quirk
net: bgmac: fix BCM5358 support by setting correct flags
i40e: add double of VLAN header when computing the max MTU
ixgbe: allow to increase MTU to 3K with XDP enabled
ice: fix lost multicast packets in promisc mode
drm/i915/gen11: Wa_1408615072/Wa_1407596294 should be on GT list
drm/vc4: Fix YUV plane handling when planes are in different buffers
drm/vc4: crtc: Increase setup cost in core clock calculation to handle
extreme reduced blanking
revert "squashfs: harden sanity check in squashfs_read_xattr_id_table"
net: Fix unwanted sign extension in netdev_stats_to_stats64()
Revert "mm: Always release pages to the buddy allocator in
memblock_free_late()."
coredump: Move dump_emit_page() to kill unused warning
freezer,umh: Fix call_usermode_helper_exec() vs SIGKILL
gpio: sim: fix a memory leak
mm/migrate: fix wrongly apply write bit after mkdirty on sparc64
mm/filemap: fix page end in filemap_get_read_batch
mm/MADV_COLLAPSE: set EAGAIN on unexpected page refcount
nilfs2: fix underflow in second superblock position calculations
hugetlb: check for undefined shift on 32 bit architectures
sched/psi: Fix use-after-free in ep_remove_wait_queue()
ata: libata-core: Disable READ LOG DMA EXT for Samsung MZ7LH
ata: ahci: Add Tiger Lake UP{3,4} AHCI controller
ALSA: hda/realtek: Enable mute/micmute LEDs and speaker support for HP Laptops
ALSA: hda/realtek: fix mute/micmute LEDs don't work for a HP platform.
ALSA: hda/realtek - fixed wrong gpio assigned
ALSA: hda/conexant: add a new hda codec SN6180
ALSA: hda: Fix codec device field initializan
mmc: mmc_spi: fix error handling in mmc_spi_probe()
mmc: sdio: fix possible resource leaks in some error paths
mmc: meson-gx: fix SDIO mode if cap_sdio_irq isn't set
mmc: jz4740: Work around bug on JZ4760(B)
drm/vmwgfx: Do not drop the reference to the handle too soon
drm/vmwgfx: Stop accessing buffer objects
[Kernel-packages] [Bug 2008708] Re: Jammy update: v6.1.14 upstream stable release
** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-oem-6.1 (Ubuntu) Status: Confirmed => Invalid -- 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/2008708 Title: Jammy update: v6.1.14 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.14 upstream stable release from git://git.kernel.org/ Linux 6.1.14 bpf: add missing header file include randstruct: disable Clang 15 support ext4: Fix function prototype mismatch for ext4_feat_ktype platform/x86: nvidia-wmi-ec-backlight: Add force module parameter platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY audit: update the mailing list in MAINTAINERS wifi: mwifiex: Add missing compatible string for SD8787 sh: define RUNTIME_DISCARD_EXIT s390: define RUNTIME_DISCARD_EXIT to fix link error with GNU ld < 2.36 powerpc/vmlinux.lds: Don't discard .rela* for relocatable builds powerpc/vmlinux.lds: Define RUNTIME_DISCARD_EXIT arch: fix broken BuildID for arm64 and riscv arm64: remove special treatment for the link order of head.o riscv: remove special treatment for the link order of head.o Bluetooth: btusb: Add more device IDs for WCN6855 x86/static_call: Add support for Jcc tail-calls x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions x86/alternatives: Introduce int3_emulate_jcc() uaccess: Add speculation barrier to copy_from_user() nfp: ethtool: fix the bug of setting unsupported port speed nfp: ethtool: support reporting link modes powerpc/64s/radix: Fix RWX mapping with relocated kernel selftests: kvm: move declaration at the beginning of main() KVM: x86: fix deadlock for KVM_XEN_EVTCHN_RESET drm/i915: Remove __maybe_unused from mtl_info spi: mediatek: Enable irq before the spi registration powerpc: dts: t208x: Disable 10G on MAC1 and MAC2 can: kvaser_usb: hydra: help gcc-13 to figure out cmd_len KVM: VMX: Execute IBPB on emulated VM-exit when guest has IBRS KVM: SVM: Skip WRMSR fastpath on VM-Exit if next RIP isn't valid KVM: x86: Fail emulation during EMULTYPE_SKIP on any exception docs: perf: Fix PMU instance name of hisi-pcie-pmu spi: mediatek: Enable irq when pdata is ready scsi: hisi_sas: Fix SATA devices missing issue during I_T nexus reset scsi: libsas: Add smp_ata_check_ready_type() random: always mix cycle counter in add_latent_entropy() sched/psi: Stop relying on timer_pending() for poll_work rescheduling clk: mxl: syscon_node_to_regmap() returns error pointers powerpc: dts: t208x: Mark MAC1 and MAC2 as 10G clk: mxl: Fix a clk entry by adding relevant flags clk: mxl: Add option to override gate clks clk: mxl: Remove redundant spinlocks clk: mxl: Switch from direct readl/writel based IO to regmap based IO drm/edid: Fix minimum bpc supported with DSC1.2 for HDMI sink wifi: rtl8xxxu: gen2: Turn on the rate control wifi: ath11k: fix warning in dma_free_coherent() of memory chunks while recovery drm/etnaviv: don't truncate physical page address To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2008708/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009142 Title: nvidia-dkms-390 FTBS with linux 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009142] Re: nvidia-dkms-390 FTBS with linux 6.2
debdiff in attatch allows to build nvidia-dkms-390 with linux 6.2. ** Patch added: "nvidia-390-support-linux-6.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+attachment/5651284/+files/nvidia-390-support-linux-6.2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009142 Title: nvidia-dkms-390 FTBS with linux 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Bug description: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
This might go a little bumpy. Normally the hwe-5.19 kernel is updated
when the kinetic one is. But states here likely do not follow
automatically.
** Also affects: linux (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.19 (Ubuntu Kinetic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.19 (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux-hwe-5.19 (Ubuntu Kinetic)
Status: New => Invalid
** Changed in: linux (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux (Ubuntu Kinetic)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Kinetic)
Status: New => In Progress
** Changed in: linux-hwe-5.19 (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-hwe-5.19 (Ubuntu Jammy)
Status: New => In Progress
** Changed in: linux-hwe-5.19 (Ubuntu)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu)
Status: Incomplete => Fix Committed
** Changed in: linux (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Fix Committed
Status in linux-hwe-5.19 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-5.19 source package in Jammy:
In Progress
Status in linux source package in Kinetic:
In Progress
Status in linux-hwe-5.19 source package in Kinetic:
Invalid
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1&id=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(&init_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009141] host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer
Default Comment by Bridge
** Attachment added: "host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer"
https://bugs.launchpad.net/bugs/2009141/+attachment/5651277/+files/host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer.txt
** Changed in: ubuntu
Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)
** Package changed: ubuntu => linux (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009141
Title:
[UBUNTU 22.04] OS installer exits for zfcp 32G adapter with an unknown
error. An error occurred during installation
Status in linux package in Ubuntu:
New
Bug description:
Bug Description:
Installation of Ubuntu 22.04 on s390x failed with an unknown error just after
having successfully activated a zfcp HBA with Fibre-Channel-attached SCSI disks.
I do see 0.0.100d successfully being online and having paths attached:
zfcp-host
0.0.100d online ?
0x500173800cef0111:0x sg16
0x500173800cef0111:0x0001 sdp sg17
0x500173800cef0111:0x0002 sdq sg18
[host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer.txt lines 41-41/9373
byte 238696/1146881 21%]
But immediately after that, the installer reports an error:
An error occurred during installation
??
?subiquity/Early/apply_autoinstall_config
?subiquity/Reporting/apply_autoinstall_config
?subiquity/Error/apply_autoinstall_config
?subiquity/Userdata/apply_autoinstall_config
?subiquity/Package/apply_autoinstall_config
?subiquity/Debconf/apply_autoinstall_config
?subiquity/Kernel/apply_autoinstall_config
?subiquity/Late/apply_autoinstall_config
??
? Sorry, an unknown error occurred. ?
? Information is being collected from the system that will help the ?
? developers diagnose the report. |
It looks like there was some ascii art progress bar while data was
collected and then the dialog updated to:
? [ View full report ]?
? If you want to help improve the installer, you can send an error ?
? report. ?
? [ Send to Canonical ]?
? [ Close report ]|
Next "View full report" was selected?
ProblemType: Bug
Architecture: s390x
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
CurrentDmesg:
[0.093997] Linux version 5.15.0-43-generic (buildd@bos02-s390x-005) (gcc
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#46-Ubuntu SMP Tue Jul 12 12:40:17 UTC 2022 (Ubuntu 5.15.0-43.46-generic
5.15.39)
[0.094001] setup: Linux is running as a z/VM guest operating system in
64-bit mode
[0.360759] Kernel command line:
ip=9.11.116.213::9.11.116.1:255.255.255.0:ilabg13:ence0f:none:9.11.227.25
https://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04.1-live-
server-s39
[ 2677.003438] zfcp 0.0.100d: qdio: ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1
TDD:1 SIGA: W
[ 2677.032397] scsi host0: zfcp
[ 2677.060025] scsi 0:0:0:0: RAID IBM 2810XIV-LUN-0
PQ: 0 ANSI: 5
[ 2677.061097] scsi 0:0:0:0: alua: disable for non-disk devices
[ 2677.061134] scsi 0:0:0:0: Attached scsi generic sg0 type 12
[ 2677.062988] scsi 0:0:0:1: Direct-Access IBM 2810XIV
PQ: 0 ANSI: 5
[ 2677.064628]
[Kernel-packages] [Bug 2009142] [NEW] nvidia-dkms-390 FTBS with linux 6.2
Public bug reported: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2009142 Title: nvidia-dkms-390 FTBS with linux 6.2 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: [Impact] nvidia-dkms-390 fails to build with linux 6.2: /var/lib/dkms/nvidia/390.157/build/nvidia-drm/nvidia-drm-drv.c:244:21: error: ‘struct drm_mode_config’ has no member named ‘fb_base’ 244 | dev->mode_config.fb_base = 0; | ^ [Fix] Change the driver to support also the 6.2 kernel ABI. [Test case] With linux 6.2 installed, run: $ sudo apt install nvidia-dkms-390 [Regression potential] We may experience regressions in newer kernels (>= 6.2) that are using nvidia-dkms-390 (source code for previous kernels remain unchanged). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/2009142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009141] [NEW] [UBUNTU 22.04] OS installer exits for zfcp 32G adapter with an unknown error. An error occurred during installation
You have been subscribed to a public bug:
Bug Description:
Installation of Ubuntu 22.04 on s390x failed with an unknown error just after
having successfully activated a zfcp HBA with Fibre-Channel-attached SCSI disks.
I do see 0.0.100d successfully being online and having paths attached:
zfcp-host
0.0.100d online ?
0x500173800cef0111:0x sg16
0x500173800cef0111:0x0001 sdp sg17
0x500173800cef0111:0x0002 sdq sg18
[host.ilabg13_9.11.116.213_ubuntu-22.04_ssh_installer.txt lines 41-41/9373 byte
238696/1146881 21%]
But immediately after that, the installer reports an error:
An error occurred during installation
??
?subiquity/Early/apply_autoinstall_config
?subiquity/Reporting/apply_autoinstall_config
?subiquity/Error/apply_autoinstall_config
?subiquity/Userdata/apply_autoinstall_config
?subiquity/Package/apply_autoinstall_config
?subiquity/Debconf/apply_autoinstall_config
?subiquity/Kernel/apply_autoinstall_config
?subiquity/Late/apply_autoinstall_config
??
? Sorry, an unknown error occurred. ?
? Information is being collected from the system that will help the ?
? developers diagnose the report. |
It looks like there was some ascii art progress bar while data was
collected and then the dialog updated to:
? [ View full report ]?
? If you want to help improve the installer, you can send an error ?
? report. ?
? [ Send to Canonical ]?
? [ Close report ]|
Next "View full report" was selected?
ProblemType: Bug
Architecture: s390x
CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}
CurrentDmesg:
[0.093997] Linux version 5.15.0-43-generic (buildd@bos02-s390x-005) (gcc
(Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38)
#46-Ubuntu SMP Tue Jul 12 12:40:17 UTC 2022 (Ubuntu 5.15.0-43.46-generic
5.15.39)
[0.094001] setup: Linux is running as a z/VM guest operating system in
64-bit mode
[0.360759] Kernel command line:
ip=9.11.116.213::9.11.116.1:255.255.255.0:ilabg13:ence0f:none:9.11.227.25
https://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04.1-live-
server-s39
[ 2677.003438] zfcp 0.0.100d: qdio: ZFCP on SC 10 using AI:1 QEBSM:1 PRI:1
TDD:1 SIGA: W
[ 2677.032397] scsi host0: zfcp
[ 2677.060025] scsi 0:0:0:0: RAID IBM 2810XIV-LUN-0
PQ: 0 ANSI: 5
[ 2677.061097] scsi 0:0:0:0: alua: disable for non-disk devices
[ 2677.061134] scsi 0:0:0:0: Attached scsi generic sg0 type 12
[ 2677.062988] scsi 0:0:0:1: Direct-Access IBM 2810XIV
PQ: 0 ANSI: 5
[ 2677.064628] scsi 0:0:0:1: alua: supports implicit TPGS
[ 2677.064632] scsi 0:0:0:1: alua: device naa.6001738cfc900cef00013596
port group 0 rel port 301
[ 2677.064679] sd 0:0:0:1: Attached scsi generic sg1 type 0
==> zfcp could successfully set 0.0.100d online and automatic LUN scan
worked.
[ 2677.513028] sd 0:0:16:1074020357: [sdac] Attached SCSI disk
[ 2677.522641] sd 0:0:16:1074020356: [sdab] Attached SCSI disk
[ 2677.522677] sd 0:0:15:1074020357: [sdaa] Attached SCSI disk
[ 2677.522693] sd 0:0:15:1074020356: [sdz] Attached SCSI disk
[ 2678.660373] device-mapper: multipath service-time: version 0.3.0 loaded
Date: Wed Jan 18 21:04:03 2023
DistroRelease: Ubuntu 22.04
ExecutablePath:
/snap/subiquity/3699/lib/python3.8/site-packages/subiquity/cmd/server.py
Installe
[Kernel-packages] [Bug 2009063] 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 2009063 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/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: Incomplete Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] [NEW] No HDMI audio under 5.19.0-35 (regression from -32)
Public bug reported: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
** Attachment added: "apport-bug output as per linux kernel bug procedure requirements" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+attachment/5651265/+files/2009063.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/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: New Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009063] Re: Inconsistent autopkgtest failures in xdp-tools lunar amd64
Note that for the log references where the autopkgtest runs using a 6.1 kernel, there appears to be a regression in the kernel. I can reproduce those locally and the problem goes away when upgrading to a mainline 6.2.0-060200.202302191831 kernel. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009063 Title: Inconsistent autopkgtest failures in xdp-tools lunar amd64 Status in linux package in Ubuntu: New Status in xdp-tools package in Ubuntu: Triaged Bug description: When running autopkgtest for xdp-tools triggered by a tcpdump update, the tests seem to fail inconsistently, not related to the tcpdump update. From the logs, one can see that some of that tests that fail in one run pass on the other, and vice versa https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230301_194524_0e221@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_124005_c4f72@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230227_010012_c05ce@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230220_001928_83990@/log.gz https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/x/xdp-tools/20230217_093659_30ac7@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009044] Re: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0
** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium -- 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/2009044 Title: Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Kinetic: In Progress Bug description: [Impact] With AMD W6800, call trace will be printed during system boot kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0 [Fix] move FPU codes from dcn folder to dml folder. also clean up the FPU codes on dcn folder. [Test Case] 1. boot a machine the AMD W6800/W6400. 2. get into desktop and check the dmesg [Where problems could occur] Medium, code refactoring so may occur some codes are left in original folder. [Misc Info] all patches have been landed on Unstable/Lunar so SRU only for Kinetic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009118] Re: Fix mediatek wifi driver crash when loading wrong SAR table
** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress -- 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/2009118 Title: Fix mediatek wifi driver crash when loading wrong SAR table Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: New Status in linux source package in Kinetic: In Progress Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] Mediatek MT7922 wifi driver crashed on some laptops. [Fix] WiFi driver should not continue initializing SAR table when it's invalid. [Test] Verified on hardware and stress netword passed. [Where problems could occur] Low risk. It may cause issues on mt76 driver. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2009118/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2000947] Re: UVC Quanta 0408:4035 camera PROBLEM
@Laurent so far, uvcvideo patch seems fine & working. which kernel version will "officially" include UVC Quanta 0408:4035 ? BR Giuliano -- 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/2000947 Title: UVC Quanta 0408:4035 camera PROBLEM Status in linux package in Ubuntu: Confirmed Bug description: I bought a Acer Nitro 5 AN517-55 with Quanta ACER HD User Facing', USB 0408:4035. The camera is reported to have problems by many users: https://linux-hardware.org/?id=usb:0408-4035 The uvc camera Quanta 0408:4035 does not work with ubuntu 22,04. the camera is “recongized” but fails installation. My console commands report similar info to other users: https://unix.stackexchange.com/questions/723504/integrated-camera-not-detected-working-on-acer-nitro-5-an515-58 PROPOSED SOLUTION I got in contact with laurent.pinch...@ideasonboard.com and with riba...@chromium.org , and subscribed to https://www.linuxtv.org/lists. And me...@vger.kernel.org mailinglist. Laurent proposed me a fix and I modified the 5,15 uvc_driver.c version, and loaded it on github https://github.com/Giuliano69/uvc_driver-for-Quanta-HD-User- Facing-0x0408-0x4035-/blob/main/uvc_driver.c I offered to test the fix, so I tried to compile the module with the new source. COMPILING PROBLEMS I’m running **Ubuntu 22.04.1 LTS, with kernel giuliano@Astra2A:/usr/src$ cat /proc/version_signature Ubuntu 5.15.0-56.62-generic 5.15.64 BUT the linux-source that I found installed seems to be different tgiuliano@Astra2A:/usr/src$ ls -al linux-so* lrwxrwxrwx 1 root root 47 nov 22 16:08 linux-source-5.15.0.tar.bz2 -> linux-source-5.15.0/linux-source-5.15.0.tar.bz2 I expanded the tar file, configured the IDE and compiled without error any errors… I manually copied the uvcvideo.ko in /lib/modules/5.15.0-56- sudo cp…... then tryed to intall the new uvcvideo.ko module sudo rmmod uvcvideo && sudo modprobe uvcvideo BUT… IT FAILS giuliano@Astra2A:~$ sudo rmmod uvcvideo && sudo modprobe uvcvideo modprobe: ERROR: could not insert 'uvcvideo': Exec format error and dmesg shows [25961.151982] usbcore: registered new interface driver uvcvideo [26323.125534] usbcore: deregistering interface driver uvcvideo [26323.189294] uvcvideo: disagrees about version of symbol module_layout These are the TWO modinfo from the old and new uvcvideo modules https://pastebin.com/tSj8Exm6 Basically OLD module: vermagic: 5.15.0-56-generic SMP mod_unload modversions NEW module: vermagic: 5.15.64 SMP mod_unload modversions -kindly ASK HOW can FORCE the uvcdriver.c to match mi kernel version ? Have I got OTHER ways to make the kernel module I’m compiling, match my running system ? I would like to test the module so to confirm the patch and let it enter the kernel main stream... BR Giuliano PS btw…. to allow Eclipse to compile the kernel, I had to pass this commands scripts/config --disable CONFIG_SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_REVOCATION_KEYS scripts/config --disable SYSTEM_TRUSTED_KEYS hope that this does not affect the module layout & checking --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: giuliano 2142 F pulseaudio /dev/snd/pcmC1D0p: giuliano 2142 F...m pulseaudio /dev/snd/controlC0: giuliano 2142 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-11-03 (66 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: Acer Nitro AN517-55 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-57-generic root=UUID=f07e25f9-07e7-4a29-a15e-f481aa0ee0f2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-57.63-generic 5.15.74 RelatedPackageVersions: linux-restricted-modules-5.15.0-57-generic N/A linux-backports-modules-5.15.0-57-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 Tags: jammy Uname: Linux 5.15.0-57-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/20/2022 dmi.bios.release: 1.6 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.06 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ignis_ADH dmi.board.vendor: ADL dmi.board.version: V1.06 dmi.chassis
[Kernel-packages] [Bug 2009114] 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 2009114
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/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
Incomplete
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
[Kernel-packages] [Bug 2007308] Re: linux-tools-common: bpftool wrapper causes build failure for xdp-tools
This bug was fixed in the package xdp-tools - 1.3.0-2ubuntu2 --- xdp-tools (1.3.0-2ubuntu2) lunar; urgency=medium * d/p/lp-2008214-ppc64le-build-failure.patch: Resolve FTBFS for ppc64le on Ubuntu (LP: #2008214). -- Frode Nordahl Thu, 23 Feb 2023 14:02:56 +0100 ** Changed in: xdp-tools (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2007308 Title: linux-tools-common: bpftool wrapper causes build failure for xdp-tools Status in launchpad-buildd: New Status in linux package in Ubuntu: Confirmed Status in xdp-tools package in Ubuntu: Fix Released Bug description: The linux-tools-common package appears to provide a shell script with a wrapper that will execute the actual bpftool binary located in a location like /usr/lib/linux-tools/6.1.0-14-generic/bpftool This causes problems for Lunar builds of xdp-tools on Launchpad [0] because there we appear to be running the build in a lunar container on host with a 5.4.0 kernel. Even if we were to install the linux-tools-6.1.0-14 package directly to get the real bpftool binary, the provided wrapper would be unhelpful. 0: https://launchpad.net/ubuntu/+source/xdp-tools/1.3.0-2 For completeness/process I collected artifacts below from a Lunar LXD container running on a Focal host with a 5.4.0 kernel. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.24.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: unknown DistroRelease: Ubuntu 23.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) Package: linux-tools-common 6.1.0-14.14 PackageArchitecture: all PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-139-generic root=UUID=d7e84875-6ab0-4d9a-bd8c-8e452fa45621 ro console=tty1 console=ttyS0 ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224 RelatedPackageVersions: linux-restricted-modules-5.4.0-139-generic N/A linux-backports-modules-5.4.0-139-generic N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: lunar uec-images package-from-proposed Uname: Linux 5.4.0-139-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-02-14 (0 days ago) UserGroups: N/A WifiSyslog: Feb 14 19:24:18 kind-flea udevadm[83]: kernel: Failed to write 'add' to '/sys/module/kernel/uevent': Permission denied _MarkForUpload: True acpidump: dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.board.name: LXD dmi.board.vendor: Canonical Ltd. dmi.board.version: pc-q35-7.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-7.1 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-7.1:rvnCanonicalLtd.:rnLXD:rvrpc-q35-7.1:cvnQEMU:ct1:cvrpc-q35-7.1: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-7.1 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/2007308/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Didn't see this "udpgso_bench_tx: sendmsg: Connection refused" issue on 5.15.0-68.75 ** Tags removed: verification-needed-jammy ** Tags added: 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/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 Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed 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 1951447] Re: ubuntu_kernel_selftests: net:udpgso_bench.sh failed
Didn't see this "udpgso_bench_tx: sendmsg: Connection refused" issue on 5.4.0-145.162 ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed 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 2009065] 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 2009065
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-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Confirmed
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1&id=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(&init_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.19 in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Confirmed
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1&id=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(&init_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009065] Re: overlayfs mounts as R/O over idmapped mount
It makes no sense to run apport-collect 2009065 in this case :)
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
** Package changed: linux (Ubuntu) => linux-hwe-5.19 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009065
Title:
overlayfs mounts as R/O over idmapped mount
Status in linux package in Ubuntu:
Incomplete
Status in linux-hwe-5.19 package in Ubuntu:
Confirmed
Bug description:
Reproducer:
create unprivileged LXC container
$ lxc launch ubuntu:22.04 idmap-test
$ lxc exec idmap-test bash
check that root is idmapped by:
$ cat /proc/self/mountinfo | grep idmap
780 675 8:1 /var/snap/lxd/common/lxd/storage-
pools/default/containers/idmap-test/rootfs / rw,relatime,idmapped
shared:323 master:319 - ext4 /dev/sda1 rw,discard,errors=remount-ro
$ mkdir {work,upper,lower,ovl}
$ mount -t overlay overlay -o lowerdir=lower,upperdir=upper,workdir=work ovl
$ touch ovl/test
touch: cannot touch 'ovl/test': Read-only file system
The problem is in __vfs_removexattr_noperm() function that called from
ovl_workdir_create().
In dmesg I can see an error:
overlayfs: failed to create directory work/work (errno: 1); mounting read-only
Reproducible on:
# uname -a
Linux ubuntu 5.19.0-32-generic #33~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Mon Jan
30 17:03:34 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
# cat /etc/os-release
PRETTY_NAME="Ubuntu 22.04.1 LTS"
Suspicious commit:
https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy/commit/fs/overlayfs/overlayfs.h?h=Ubuntu-hwe-5.19-5.19.0-32.33_22.04.1&id=3418435738af5730918fafbdfe2905a98ce2ef05
Chunk:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(&init_user_ns, dentry, name, value, size,
flags);
+ inode_unlock(inode);
should be:
+ inode_lock(inode);
+ err = __vfs_setxattr_noperm(ovl_upper_mnt_userns(ofs), dentry, name,
value, size, flags);
+ inode_unlock(inode);
I'll send a patch soon.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009065/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
Also included in https://launchpad.net/~canonical-hwe- team/+archive/ubuntu/linux-firmware-staging version 20220329.git681281e4-0ubuntu3.10+exp.65. -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
SRU: https://lists.ubuntu.com/archives/kernel- team/2023-March/137477.html (linux-firmware/jammy) ** Description changed: + [SRU Justification] + + [Impact] + + backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and + -73 firmware are supported bug missing. On one user reported issue, this + fixes WiFi stability on 5G band. + + [Fix] + + New upstreamed firmware revision fixes this issue. + + [Test Case] + + 1. Boot hwe-5.19 kernel + 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded + 3. Browse the web, usually takes between 1 and 5 minutes + 4. Networking will cut out + + [Where problems could occur] + + This affects only users need both backport-iwlwifi-dkms and hwe-5.19 + kernel on WiFi stability. + + [Other Info] + + While Kinetic and above have them all, only Jammy is nominated. + + == original bug report == + I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. -- 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: [SRU Justification] [Impact] backport-iwlwifi-dkms/kinetic is being built into hwe-5.19 kernel, and -73 firmware are supported bug missing. On one user reported issue, this fixes WiFi stability on 5G band. [Fix] New upstreamed firmware revision fixes this issue. [Test Case] 1. Boot hwe-5.19 kernel 2. iwlwifi-so-a0-gf-a0-73.ucode firmware should be loaded 3. Browse the web, usually takes between 1 and 5 minutes 4. Networking will cut out [Where problems could occur] This affects only users need both backport-iwlwifi-dkms and hwe-5.19 kernel on WiFi stability. [Other Info] While Kinetic and above have them all, only Jammy is nominated. == original bug report == I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launch
[Kernel-packages] [Bug 2009114] Re: kernel crash dump caused by Google Chrome
** Package changed: ubuntu => linux (Ubuntu)
** Tags added: focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2009114
Title:
kernel crash dump caused by Google Chrome
Status in linux package in Ubuntu:
New
Bug description:
lsb_release -rd
Description: Ubuntu 20.04.5 LTS
Release: 20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30
UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in
process chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash
_clmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd8/0x2c0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882078]
do_user_addr
[Kernel-packages] [Bug 2007875] Re: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently
** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: oem-somerville-tentacool-meta (Ubuntu Lunar) Importance: Undecided Assignee: Kai-Chuan Hsieh (kchsieh) Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: oem-somerville-tentacool-meta (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: oem-somerville-tentacool-meta (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => Fix Released ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => Fix Released ** Changed in: oem-somerville-tentacool-meta (Ubuntu Kinetic) Status: New => Invalid ** Changed in: oem-somerville-tentacool-meta (Ubuntu Lunar) Status: New => Invalid ** Changed in: oem-somerville-tentacool-meta (Ubuntu Lunar) Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned) ** Changed in: oem-somerville-tentacool-meta (Ubuntu Jammy) Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Changed in: linux-firmware (Ubuntu Jammy) Status: Fix Released => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => 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/2007875 Title: Ubuntu 22.04 XPS 13 plus 9320 kernel 6.0 OEM and 5.19 breaks wifi frequently Status in linux-firmware package in Ubuntu: Fix Released Status in oem-somerville-tentacool-meta package in Ubuntu: Invalid Status in linux-firmware source package in Jammy: In Progress Status in oem-somerville-tentacool-meta source package in Jammy: New Status in linux-firmware source package in Kinetic: Fix Released Status in oem-somerville-tentacool-meta source package in Kinetic: Invalid Status in linux-firmware source package in Lunar: Fix Released Status in oem-somerville-tentacool-meta source package in Lunar: Invalid Bug description: I'm using the stock Dell Ubuntu 22.04 image on my XPS 13 Plus (9320). Recently I received some kernel updates, the 5.19 kernel used in 22.10 and a 6.0 oem kernel. Both updates break wifi. It seems to only do so on newer 5.7 GHz access points. 1. Boot latest 6.0 oem kernel 2. Browse the web, usually takes between 1 and 5 minutes. 3. Networking will cut out. Disabling networking and starting again will fix it until it happens again in a few minutes. This will repeat indefinitely, essentially making wireless useless. The attached dmesg log reliably shows up when it fails, showing iwlwifi failing and a (network?) hardware reset request. It witnessed this happen months ago on 22.10, which led me to using the Dell stock 22.04 image. But it seems even the newer OEM kernel is affected. A workaround is to select the older 5.15 kernel in grub. I find on this laptop, one must hit escape precisely 1 second after seeing the Dell logo on boot. Alternatively one could edit /etc/grub/default and set a longer timeout. Let me know if this bug report would be better to go to Dell as a support request instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2007875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009127] [NEW] Lunar update: v6.2.1 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.1 upstream stable release from git://git.kernel.org/ uaccess: Add speculation barrier to copy_from_user() x86/alternatives: Introduce int3_emulate_jcc() x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions x86/static_call: Add support for Jcc tail-calls HID: mcp-2221: prevent UAF in delayed work wifi: mwifiex: Add missing compatible string for SD8787 audit: update the mailing list in MAINTAINERS platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY platform/x86: nvidia-wmi-ec-backlight: Add force module parameter ext4: Fix function prototype mismatch for ext4_feat_ktype randstruct: disable Clang 15 support bpf: add missing header file include Linux 6.2.1 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v6.2.1 upstream stable release + from git://git.kernel.org/ -v6.2.1 upstream stable release -from git://git.kernel.org/ + uaccess: Add speculation barrier to copy_from_user() + x86/alternatives: Introduce int3_emulate_jcc() + x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions + x86/static_call: Add support for Jcc tail-calls + HID: mcp-2221: prevent UAF in delayed work + wifi: mwifiex: Add missing compatible string for SD8787 + audit: update the mailing list in MAINTAINERS + platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY + platform/x86: nvidia-wmi-ec-backlight: Add force module parameter + ext4: Fix function prototype mismatch for ext4_feat_ktype + randstruct: disable Clang 15 support + bpf: add missing header file include + Linux 6.2.1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009127 Title: Lunar update: v6.2.1 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Lunar: Confirmed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.2.1 upstream stable release from git://git.kernel.org/ uaccess: Add speculation barrier to copy_from_user() x86/alternatives: Introduce int3_emulate_jcc() x86/alternatives: Teach text_poke_bp() to patch Jcc.d32 instructions x86/static_call: Add support for Jcc tail-calls HID: mcp-2221: prevent UAF in delayed work wifi: mwifiex: Add missing compatible string for SD8787 audit: update the mailing list in MAINTAINERS platform/x86/amd/pmf: Add depends on CONFIG_POWER_SUPPLY platform/x86: nvidia-wmi-ec-backlight: Add force module parameter ext4: Fix function prototype mismatch for ext4_feat_ktype randstruct: disable Clang 15 support bpf: add missing header file include Linux 6.2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009127/+subscriptions
[Kernel-packages] [Bug 2009114] [NEW] kernel crash dump caused by Google Chrome
You have been subscribed to a public bug:
lsb_release -rd
Description:Ubuntu 20.04.5 LTS
Release:20.04
ryz:/home/tteikhua>uname -a
Linux tteikhua 5.15.0-60-generic #66~20.04.1-Ubuntu SMP Wed Jan 25 09:41:30 UTC
2023 x86_64 x86_64 x86_64 GNU/Linux
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]:
/usr/lib/ubuntu-release-upgrader/check-new-release-gtk:147:
PyGIDeprecationWarning: Using positional arguments with the GObject constructor
has been deprecated. Please specify keyword(s) for "schema" or use a class
specific constructor. See:
https://wiki.gnome.org/PyGObject/InitializerDeprecations
Mar 3 11:34:07 tteikhua check-new-release-gtk[14805]: client =
Gio.Settings("com.ubuntu.update-manager")
Mar 3 11:34:07 tteikhua systemd[2706]: update-notifier-release.service:
Succeeded.
Mar 3 11:34:07 tteikhua systemd[2706]: Finished Notification regarding a new
release of Ubuntu.
Mar 3 11:34:12 tteikhua gnome-shell[6917]:
[6910:6910:0303/113412.291622:ERROR:interface_endpoint_client.cc(695)] Message
1 rejected by interface blink.mojom.WidgetHost
Mar 3 11:34:13 tteikhua kernel: [ 6927.881982] BUG: Bad page state in process
chrome pfn:450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881987] page:52cfc54f
refcount:32768 mapcount:0 mapping: index:0x1 pfn:0x450510
Mar 3 11:34:13 tteikhua kernel: [ 6927.881990] flags:
0x17c000(node=0|zone=2|lastcpupid=0x1f)
Mar 3 11:34:13 tteikhua kernel: [ 6927.881993] raw: 0017c000
dead0100 dead0122
Mar 3 11:34:13 tteikhua kernel: [ 6927.881994] raw: 0001
8000
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] page dumped because: nonzero
_refcount
Mar 3 11:34:13 tteikhua kernel: [ 6927.881995] Modules linked in: rfcomm
input_leds xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user
xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack
nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc vmnet(OE)
vmw_vsock_vmci_transport vsock vmw_vmci vmmon(OE) aufs overlay cmac algif_hash
algif_skcipher af_alg bnep xfs libcrc32c nls_iso8859_1 snd_hda_codec_realtek
snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi binfmt_misc
snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi nouveau snd_hda_codec
intel_rapl_msr intel_rapl_common drm_ttm_helper snd_hda_core ttm iwlmvm
snd_hwdep drm_kms_helper snd_pcm mac80211 edac_mce_amd libarc4 snd_seq_midi
snd_seq_midi_event cec kvm_amd rc_core snd_rawmidi iwlwifi snd_seq btusb
fb_sys_fops syscopyarea snd_seq_device btrtl sysfillrect sysimgblt btbcm kvm
cfg80211 video btintel snd_timer snd bluetooth soundcore ecdh_generic ecc
crct10dif_pclmul k10temp ghash_c
lmulni_intel mac_hid ccp aesni_intel
Mar 3 11:34:13 tteikhua kernel: [ 6927.882031] crypto_simd gigabyte_wmi
cryptd wmi_bmof mxm_wmi rapl efi_pstore sch_fq_codel ipmi_devintf
ipmi_msghandler msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4
hid_generic usbhid hid igb atlantic crc32_pclmul nvme i2c_algo_bit ahci
xhci_pci i2c_piix4 libahci xhci_pci_renesas macsec nvme_core dca wmi
Mar 3 11:34:13 tteikhua kernel: [ 6927.882046] CPU: 9 PID: 7508 Comm: chrome
Tainted: G OE 5.15.0-60-generic #66~20.04.1-Ubuntu
Mar 3 11:34:13 tteikhua kernel: [ 6927.882048] Hardware name: Gigabyte
Technology Co., Ltd. X570 AORUS XTREME/X570 AORUS XTREME, BIOS F32 01/18/2021
Mar 3 11:34:13 tteikhua kernel: [ 6927.882049] Call Trace:
Mar 3 11:34:13 tteikhua kernel: [ 6927.882051]
Mar 3 11:34:13 tteikhua kernel: [ 6927.882053] dump_stack_lvl+0x4a/0x63
Mar 3 11:34:13 tteikhua kernel: [ 6927.882058] dump_stack+0x10/0x16
Mar 3 11:34:13 tteikhua kernel: [ 6927.882059] bad_page.cold+0x63/0x94
Mar 3 11:34:13 tteikhua kernel: [ 6927.882061] check_new_page_bad+0x6d/0x80
Mar 3 11:34:13 tteikhua kernel: [ 6927.882064] rmqueue_bulk+0x43e/0x750
Mar 3 11:34:13 tteikhua kernel: [ 6927.882065] rmqueue+0x5ae/0xba0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882066] ? __wake_up+0x13/0x20
Mar 3 11:34:13 tteikhua kernel: [ 6927.882069]
get_page_from_freelist+0xd5/0x460
Mar 3 11:34:13 tteikhua kernel: [ 6927.882070] __alloc_pages+0x17b/0x310
Mar 3 11:34:13 tteikhua kernel: [ 6927.882072] alloc_pages_vma+0x95/0x270
Mar 3 11:34:13 tteikhua kernel: [ 6927.882074] do_anonymous_page+0xf8/0x3b0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882076] __handle_mm_fault+0x804/0x840
Mar 3 11:34:13 tteikhua kernel: [ 6927.882077] handle_mm_fault+0xd8/0x2c0
Mar 3 11:34:13 tteikhua kernel: [ 6927.882078] do_user_addr_fault+0x1c2/0x660
Mar 3 11:34:13 tteikhua kernel: [ 6927.882080] exc_page_fault+0x77/0x170
Mar 3 11:34:13 tteikhua kernel: [ 6927.882083] asm_exc_page_fault+0x27/0x30
Mar 3 11:34:13 tteikhua kernel: [ 6927.882085] RIP: 0033:0x5650c5c1875a
Mar 3 11:34:13 tteikhua kernel: [ 6927.882087] Code: c0 e9 03 80 e1 07 be 01
00 00 00 d3 e6 40 0a 74 10 41 40 88 74 10 41 48
