[Kernel-packages] [Bug 2071698] Re: Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1005.5
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-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.11'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.11' to 'verification-failed-
noble-linux-oem-6.11'.
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-noble-linux-oem-6.11-v2
verification-needed-noble-linux-oem-6.11
--
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/2071698
Title:
Integrated Sensor Hub (ISH) support for Intel Lunar Lake platform
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-firmware source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
In Progress
Status in linux source package in Oracular:
Fix Committed
Status in linux-firmware source package in Oracular:
Fix Released
Status in linux-oem-6.11 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Starting from Intel Lunar Lake, the ISH firmware will reside in system
root as separated blobs, and the kernel driver is responsible for
loading a preferred one based on DMI info.
[Fix]
Kernel fixes in linux-next:
* aa4674c525e1e hid: intel-ish-hid: Add support for vendor customized
firmware loading
* 641361538b68d HID: intel-ish-hid: Use CPU generation string in driver_data
* 87de1615194ee Documentation: hid: intel-ish-hid: Add vendor custom firmware
loading
linux-firmware in upstream tag 20240709:
* 33a8b2a7f604 linux-firmware: Add ISH firmware file for Intel Lunar Lake
platform
[Test Case]
dmesg dumps:
```
intel_ish_ipc :00:12.0: ISH loader: firmware loaded. size:748032
ish-hid {33AECD58-B679-4E54-9BD9-A04D34F0C226}: [hid-ish]: enum_devices_done
OK, num_hid_devices=2
hid-generic 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-generic 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0005: hidraw4: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
hid-sensor-hub 001F:8087:0AC2.0006: hidraw5: SENSOR HUB HID v2.00 Device
[hid-ishtp 8087:0AC2] on
```
[Where problems could occur]
This is to include generic blob provided by Intel for all Lunar Lake
platforms. It may not be stable, may not be functional, and may have
various problems until the hardware vendor submit their own.
[Other Info]
Nominated for linux/oracular, linux-oem-6.11/noble, linux-
firmware/oracular and linux-firmware/noble.
== original bug report ==
* kernel
-
https://patchwork.kernel.org/project/linux-input/cover/20240813034736.812475-1-lixu.zh...@intel.com/
* linux-firmware
- generic
* commit 33a8b2a7f604 ("linux-firmware: Add ISH firmware file for Intel
Lunar Lake platform")
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2071698/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2080190] Re: Soundwire support for Dell SKU0CDC devices
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1005.5
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-noble-linux-oem-6.11' to 'verification-done-
noble-linux-oem-6.11'. If the problem still exists, change the tag
'verification-needed-noble-linux-oem-6.11' to 'verification-failed-
noble-linux-oem-6.11'.
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-noble-linux-oem-6.11-v2
verification-needed-noble-linux-oem-6.11
--
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/2080190
Title:
Soundwire support for Dell SKU0CDC devices
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
In Progress
Status in linux-oem-6.11 source package in Noble:
New
Status in linux source package in Oracular:
New
Status in linux-oem-6.11 source package in Oracular:
Invalid
Bug description:
[SRU Justification]
[Impact]
Missing soundwire support for Dell SKU0CDC deivces.
[Fix]
The upstream fix 9307694f340e ("ASoC: Intel: sof_sdw: Add quirks from some
new Dell laptops") and its dependency are required.
[Test Case]
1. Install linux-firmware proposed in
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/2077829
2. Install the firmware-sof w/ sof-lnl-cs42l43-l0.tplg
3. Test audio functions on Taroko LNL platforms.
[Where problems could occur]
New devices, may need further polishments.
== original bug description ==
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
Topology: ABI 3:29:0 Kernel ABI 3:23:0
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: can't connect DAI alh-copier.Playback-SmartAmp.0 stream Playback-SmartAmp
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
failed to add widget type 27 name : alh-copier.Playback-SmartAmp.0 stream
Playback-SmartAmp
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: failed to load
widget alh-copier.Playback-SmartAmp.0
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: topology: could not
load header: -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: tplg component load failed -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3:
error: failed to load DSP topology -22
Sep 05 04:57:35 localhost kernel: sof-audio-pci-intel-lnl :00:1f.3: ASoC:
error at snd_soc_component_probe on :00:1f.3: -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: ASoC: failed to
instantiate card -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: error -EINVAL:
snd_soc_register_card failed -22
Sep 05 04:57:35 localhost kernel: sof_sdw sof_sdw: probe with driver sof_sdw
failed with error -22
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2080190/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2077306] Re: Remove obsolete build flags in derivative kernels
This bug is awaiting verification that the linux-oem-6.11/6.11.0-1005.5 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-noble-linux-oem-6.11' to 'verification-done- noble-linux-oem-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-failed- noble-linux-oem-6.11'. 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-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11 -- 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/2077306 Title: Remove obsolete build flags in derivative kernels Status in linux package in Ubuntu: Invalid Status in linux-ibm package in Ubuntu: New Bug description: [Impact] Note: This impacts derivative kernel packages only. Old and obsolete build flags in derivative kernel packages might result in unexpected packaging behavior, like broken builds, building of unwanted packages, ... [Fix] Remove old and obsolete build flags: do_enforce_all do_tools_host do_tools_common do_libc_dev_package do_doc_package [Test Case] Build packages and verify that the resulting set of binary packages is as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2077306/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2076174] Re: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker
*** This bug is a duplicate of bug 2080236 *** https://bugs.launchpad.net/bugs/2080236 ** This bug is no longer a duplicate of bug 2079016 noble/linux-oem-6.11: 6.11.0-1004.4 -proposed tracker ** This bug has been marked a duplicate of bug 2080236 noble/linux-oem-6.11: 6.11.0-1005.5 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.11 in Ubuntu. https://bugs.launchpad.net/bugs/2076174 Title: noble/linux-oem-6.11: 6.11.0-1001.1 -proposed tracker Status in canonical-signing-jobs task00 series: Fix Released Status in Kernel SRU Workflow: Fix Released Status in Kernel SRU Workflow abi-testing series: Invalid Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow boot-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow new-review series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-generate series: Fix Released Status in Kernel SRU Workflow prepare-package-lrg series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-lrs series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow signing-signoff series: Fix Released Status in Kernel SRU Workflow sru-review series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem-6.11 package in Ubuntu: Invalid Status in linux-oem-6.11 source package in Noble: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- built: from: aa77570705065ac8 route-entry: 1 delta: promote-to-proposed: [lrm, lrs, main, meta, signed, lrg, generate] flag: boot-testing-requested: true bugs-spammed: true proposed-testing-requested: true packages: generate: linux-generate-oem-6.11 lrg: linux-restricted-generate-oem-6.11 lrm: linux-restricted-modules-oem-6.11 lrs: linux-restricted-signatures-oem-6.11 main: linux-oem-6.11 meta: linux-meta-oem-6.11 signed: linux-signed-oem-6.11 phase: Testing phase-changed: Tuesday, 13. August 2024 08:35 UTC reason: regression-testing: Stalled -s testing FAILED synthetic: :promote-to-as-proposed: Fix Released variant: debs versions: lrm: 6.11.0-1001.1 main: 6.11.0-1001.1 meta: 6.11.0-1001.1 signed: 6.11.0-1001.1 ~~: clamps: new-review: aa77570705065ac8 promote-to-proposed: aa77570705065ac8 self: 6.11.0-1001.1 sru-review: aa77570705065ac8 tracker: last-message: '2024-08-13 07:48:49.587999+00:00' To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-signing-jobs/task00/+bug/2076174/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-jammy-linux-
realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'.
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-realtime-6.8-v2
verification-needed-jammy-linux-realtime-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lis
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (P
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_del
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the
problem. Please test the kernel and update this bug with the results. If
the problem is solved, change the tag 'verification-needed-jammy-linux-
realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'.
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-realtime-6.8-v2
verification-needed-jammy-linux-realtime-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073926] Re: [SRU] Add support for intel trace hub for last platforms
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2073926 Title: [SRU] Add support for intel trace hub for last platforms Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: This is a public version of: - https://bugs.launchpad.net/bugs/2028492 - https://bugs.launchpad.net/bugs/2044682 [ Impact ] Enable Intel trace hub for Granite Rapids, Sapphire Rapids and Lunar Lake. [ Test Plan ] Compiled. [ Fix ] Clean cherry pick from upstream. [ Where problems could occur ] Intel thermal tracing regression with other intel platform or issue with these specifics platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073961] Re: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2073961 Title: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: This is a public version of: https://bugs.launchpad.net/bugs/2044673 [ Impact ] Add Lunar Lake-M PCI ID for processor thermal device. [ Fix ] Clean cherry pick from upstream. [ Test Plan ] Compiled. [ Where problems could occur ] Bad thermal management for Lunar Lake CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2074372] Re: [SRU] Turbostat support for Arrow Lake H
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2074372 Title: [SRU] Turbostat support for Arrow Lake H Status in linux package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Bug description: This is a public version of: https://bugs.launchpad.net/bugs/2044459 [ Impact ] Enable Turbostat on Arrow Lake H platform. [ Fix ] Cherry pick two commits from upstream: 196eca020600 - tools/power turbostat: Enhance ARL/LNL support f04fcc7ac8ce - tools/power turbostat: Add ARL-H support [ Test Plan ] Compiled. [ Where problems could occur ] Regression for Arrow lake on Turbostat. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2074372/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedul
[Kernel-packages] [Bug 2074376] Re: Disable PCI_DYNAMIC_OF_NODES in Ubuntu
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2074376 Title: Disable PCI_DYNAMIC_OF_NODES in Ubuntu Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Noble: Fix Released Status in linux source package in Oracular: Fix Committed Bug description: This came in via KTML from upstream. It is part of a discussion between upstream and IBM reporting a bug which occurs in KVM: Rob Herring writes: >> On 2024/07/11 06:20 AM, Rob Herring wrote: >>> On Wed, Jul 3, 2024 at 8:17 AM Amit Machhiwal wrote: With CONFIG_PCI_DYNAMIC_OF_NODES [1], a hot-plug and hot-unplug sequence of a PCI device attached to a PCI-bridge causes following kernel Oops on a pseries KVM guest: >>> >>> Can I ask why you have this option on in the first place? Do you have >>> a use for it or it's just a case of distros turn on every kconfig >>> option. >> >> Yes, this option is turned on in Ubuntu's distro kernel config where the issue >> was originally reported, while Fedora is keeping this turned off. >> >> root@ubuntu:~# cat /boot/config-6.8.0-38-generic | grep PCI_DYN >> CONFIG_PCI_DYNAMIC_OF_NODES=y > > Ubuntu should turn off this option. For starters, it is not complete > to be usable. Eventually, it should get removed in favor of some TBD > runtime option. > > (And we should fix the crash too) This option is described in the config system as: This option enables support for generating device tree nodes for some PCI devices. Thus, the driver of this kind can load and overlay flattened device tree for its downstream devices. . Once this option is selected, the device tree nodes will be generated for all PCI bridges. Open Firmware (OF) would be used for KVM for UEFI mode. The reported bug was related to hot-unplugging PCI devices. My guess would be that this probably is not of much use to the majority of users and might even go away. So it should really be disabled in Ubuntu, too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/2074376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2075110] Re: md: nvme over tcp with a striped underlying md raid device leads to data corruption
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2075110 Title: md: nvme over tcp with a striped underlying md raid device leads to data corruption Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2075110 [Impact] There is a fault in the md subsystem where __write_sb_page() will round the io size up to the optimal size, but it doesn't check to see if the final io size exceeds the bitmap length. This gets us into a situation where if we have 256K of io to submit, 64 pages are needed. md_bitmap_storage_alloc() allocates 1 page, and 63 are allocated afterward. When we send md writes over the network, e.g. with nvme over tcp, the network subsystem checks the first page which is sendpage_ok(), but not the other 63, which might not be sendpage_ok(), and will get stuck, causing a hang and data corruption. If you trigger the issue, you get the following oops in dmesg: WARNING: CPU: 0 PID: 83 at net/core/skbuff.c:6995 skb_splice_from_iter+0x139/0x370 CPU: 0 PID: 83 Comm: kworker/0:1H Not tainted 6.8.0-39-generic #39-Ubuntu Workqueue: nvme_tcp_wq nvme_tcp_io_work [nvme_tcp] RIP: 0010:skb_splice_from_iter+0x139/0x370 CR2: 72dab83e5f84 Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? skb_splice_from_iter+0x139/0x370 ? report_bug+0x17e/0x1b0 ? handle_bug+0x51/0xa0 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? skb_splice_from_iter+0x139/0x370 tcp_sendmsg_locked+0x352/0xd70 ? tcp_push+0x159/0x190 ? tcp_sendmsg_locked+0x9c4/0xd70 tcp_sendmsg+0x2c/0x50 inet_sendmsg+0x42/0x80 sock_sendmsg+0x118/0x150 nvme_tcp_try_send_data+0x18b/0x4c0 [nvme_tcp] ? __tcp_cleanup_rbuf+0xc5/0xe0 nvme_tcp_try_send+0x23c/0x300 [nvme_tcp] nvme_tcp_io_work+0x40/0xe0 [nvme_tcp] process_one_work+0x16c/0x350 worker_thread+0x306/0x440 ? _raw_spin_unlock_irqrestore+0x11/0x60 ? __pfx_worker_thread+0x10/0x10 kthread+0xef/0x120 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x44/0x70 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1b/0x30 nvme nvme1: failed to send request -5 nvme nvme1: I/O tag 125 (307d) type 4 opcode 0x0 (I/O Cmd) QID 1 timeout nvme nvme1: starting error recovery block nvme1n1: no usable path - requeuing I/O nvme nvme1: Reconnecting in 10 seconds... There is no workaround. [Fix] This was fixed in the below commit in 6.11-rc1: commit ab99a87542f194f28e2364a42afbf9fb48b1c724 Author: Ofir Gal Date: Fri Jun 7 10:27:44 2024 +0300 Subject: md/md-bitmap: fix writing non bitmap pages Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ab99a87542f194f28e2364a42afbf9fb48b1c724 This is a clean cherry-pick to the Noble tree. [Testcase] This can be reproduced by running blktests md/001 [1], which the author of the fix created to act as a regression test for this issue. [1] https://github.com/osandov/blktests/commit/a24a7b462816fbad7dc6c175e53fcc764ad0a822 Deploy a fresh Noble VM, that has a scratch NVME disk. $ sudo apt install build-essential fio $ git clone https://github.com/osandov/blktests.git $ cd blktests $ make $ echo "TEST_DEVS=(/dev/nvme0n1)" > config $ sudo ./check md/001 The md/001 test will hang an affected system, and the above oops message will be visible in dmesg. A test kernel is available in the following ppa: https://launchpad.net/~mruffell/+archive/ubuntu/sf390669-test If you install the test kernel, the md/001 test will complete successfully, and the issue will no longer appear. [Where problems could occur] We are changing how the md subsystem calculates final IO sizes, and taking the smaller value of the size or the bitmap_limit. This makes sure we don't leak the final page and corrupt data. If a regression were to occur, it would likely affect all md users, but would be more obvious to md users over the network, like nv
[Kernel-packages] [Bug 2076650] Re: Reenable CONFIG_UBSAN for noble
This bug is awaiting verification that the linux- realtime-6.8/6.8.1-1008.8~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-done-jammy-linux-realtime-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- realtime-6.8' to 'verification-failed-jammy-linux-realtime-6.8'. 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-realtime-6.8-v2 verification-needed-jammy-linux-realtime-6.8 -- 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/2076650 Title: Reenable CONFIG_UBSAN for noble Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: It was disabled by mistake due to a missing dependency. Commit "ubsan: Restore dependency on ARCH_HAS_UBSAN" was applied without "ubsan: Remove CONFIG_UBSAN_SANITIZE_ALL", resulting in CONFIG_UBSAN being dependant on a config option that does not exist. Fix this by cherry-picking ubsan: Remove CONFIG_UBSAN_SANITIZE_ALL. The reason the dependency is missing: From 6.8.12, 6.9.4 was picked up. The commit "Remove CONFIG_UBSAN_SANITIZE_ALL" was introduced in 6.9.0 I believe, that's why it was not picked up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2076650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8'
to 'verification-failed-jammy-linux-ibm-6.8'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2
verification-needed-jammy-linux-aws-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 board with Noble,
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsu
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kern
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsu
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https:
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : http
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'.
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-oracle-6.8-v2
verification-needed-jammy-linux-oracle-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal AR
[Kernel-packages] [Bug 2033007] Re: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2033007 Title: kdump doesn't work with UEFI secure boot and kernel lockdown enabled on ARM64 Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Noble: Fix Released Bug description: [Impact] The kdump service operates by utilizing the kexec_file_load system call, which loads a new kernel image intended for subsequent execution. However, this process encounters a hindrance if the CONFIG_KEXEC_IMAGE_VERIFY_SIG option isn't enabled to facilitate signature verification. In addition, a noteworthy point is that if the kernel image is signed with a MOK, it will face rejection due to ARM64's reliance solely on the .builtin_trusted_keys for verification purposes. To enhance flexibility, it's suggested that we align the behavior on x86 platforms. This alignment could potentially involve expanding the scope to encompass more keyrings, such as .secondary_trusted_keys and platform keyrings, thereby broadening the options available for verification mechanisms. [Fix] Enabling the CONFIG_KEXEC_IMAGE_VERIFY_SIG option is necessary, along with the incorporation of two specific commits, in order to enhance the capabilities of the kexec_file_load system call on ARM64. The commits that need to be applied are as follows: c903dae8941d kexec, KEYS: make the code in bzImage64_verify_sig generic 0d519cadf751 arm64: kexec_file: use more system keyrings to verify kernel image signature [Test Plan] 1. Set up a VM with UEFI secure boot and enabled kernel lockdown on ARM64 2. Install 'kdump-tools' sudo apt install linux-crashdump 3. Reboot and verify kdump status with 'kdump-config show' root@ubuntu:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_COREDIR:/var/crash crashkernel addr: 0xde00 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.15.0-78-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.15.0-78-generic current state:Not ready to kdump kexec command: /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-79-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz 4. Check the log using 'systemctl status kdump-tools' Aug 24 06:08:39 ubuntu systemd[1]: Starting Kernel crash dump capture service... Aug 24 06:08:39 ubuntu kdump-tools[1750]: Starting kdump-tools: Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/vmlinuz Aug 24 06:08:39 ubuntu kdump-tools[1755]: * Creating symlink /var/lib/kdump/initrd.img Aug 24 06:08:39 ubuntu kdump-tools[1755]: * /sbin/kexec -p -s --command-line="BOOT_IMAGE=/boot/vmlinuz-5.15.0-78-generic root=UUID=63e4c69f-fb47-4a54-8ef1-c955ae9a9a50 ro console=tty1 console=ttyS0 reset_devices systemd.unit=kdump-tools-dump.service nr_cpus=1" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz Aug 24 06:08:41 ubuntu kernel: [ 403.301008] Lockdown: kexec: kexec of unsigned images is restricted; see man kernel_lockdown.7 Aug 24 06:08:41 ubuntu kdump-tools[1755]: * failed to load kdump kernel Aug 24 06:08:41 ubuntu kdump-tools: failed to load kdump kernel Aug 24 06:08:41 ubuntu systemd[1]: Finished Kernel crash dump capture service. [Where problems could occur] The problem is specific to kexec image signature verification on ARM64. This change allows additional keyrings and impacts only the ARM64 kexec_file_load system call. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033007/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~ker
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8'
to 'verification-failed-jammy-linux-riscv-6.8'.
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-riscv-6.8-v2
verification-needed-jammy-linux-riscv-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 boar
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8'
to 'verification-failed-jammy-linux-ibm-6.8'.
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-ibm-6.8-v2
verification-needed-jammy-linux-ibm-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 board with Noble,
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.8'
to 'verification-failed-jammy-linux-aws-6.8'.
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!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 board with Noble, running 6.8.
2) Edit /boot/grub/grub.cfg and add the following param to any boot entry with
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-
azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-azure-6.8'
to 'verification-failed-jammy-linux-azure-6.8'.
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-azure-6.8-v2
verification-needed-jammy-linux-azure-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 boar
[Kernel-packages] [Bug 2069534] Re: Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12
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-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.
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-noble-linux-raspi-v2
verification-needed-noble-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2069534
Title:
Linux 6.8 fails to boot on ARM64 if any param is more than 146 chars
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-6.8 package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Invalid
Status in linux-hwe-6.8 source package in Jammy:
Fix Released
Status in linux source package in Noble:
Fix Released
Status in linux-hwe-6.8 source package in Noble:
Invalid
Bug description:
BugLink: https://bugs.launchpad.net/bugs/2069534
[Impact]
Linux 6.8 kernel fails to boot on ARM64 when any Linux command line
param is more than 146 characters.
This most notably affects MAAS deployments, as MAAS generates very
long command line parameters for ARM64, e.g.:
nomodeset
root=squash:http://10.254.131.130:5248/images/3b08252fa962c37a47d890fb5fe182b631a0c0478d758bf4573efa859cc2c548/ubuntu/arm64/ga-24.04/noble/stable/squashfs
ip=sjc01-2b16-u07-mgx01b:BOOTIF ip6=off cc:\{'datasource_list':
['MAAS']\}end_cc cloud-config-url=http://10-254-131-128--25.maas-
internal:5248/MAAS/metadata/latest/by-id/de6dn3/?op=get_preseed ro
overlayroot=tmpfs overlayroot_cfgdisk=disabled log_host=10.254.131.130
log_port=5247 --- BOOTIF=01-${net_default_mac}
This was introduced in 6.8-rc1 by:
commit dc3f5aae06381b43bc9d0d416bd15ee1682940e9
Author: Ard Biesheuvel
Date: Wed Nov 29 12:16:12 2023 +0100
Subject: arm64: idreg-override: Avoid parameq() and parameqn()
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=dc3f5aae06381b43bc9d0d416bd15ee1682940e9
There is no workaround, other than using command line parameters less
than 146 characters. This is not tenable for MAAS users.
[Fix]
The fix arrived in a major refactor of early ARM64 init, where they
moved from assembly to the pi mini c library. The specific commit that
fixed the issue is:
commit e223a449125571daa62debd8249fa4fc2da0a961
Author: Ard Biesheuvel
Date: Wed Feb 14 13:28:50 2024 +0100
Subject: arm64: idreg-override: Move to early mini C runtime
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e223a449125571daa62debd8249fa4fc2da0a961
However, this needs a lot of dependencies, mostly all the "mini c
runtime" commits in the below merge commit:
commit 6d75c6f40a03c97e1ecd683ae54e249abb9d922b
Merge: fe46a7dd189e 1ef21fcd6a50
Author: Linus Torvalds
Date: Thu Mar 14 15:35:42 2024 -0700
Subject: Merge tag 'arm64-upstream' of
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux
Link:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d75c6f40a03c97e1ecd683ae54e249abb9d922b
The amount of code is generally unacceptable for an SRU due to
regression risk. I also don't think that reverting "arm64: idreg-
override: Avoid parameq() and parameqn()" is the right solution
either.
Thankfully, Tj did some debugging of the root cause in comment #20
[1], and found the issue occurs because of memcmp() in
include/linux/fortify-string.h detecting an attempted out-of-bounds
read when comparing buf and aliases[i].alias.
That triggers the fortified memcmp()'s:
if (p_size < size || q_size < size)
fortify_panic(__func__);
where q_size == 146, size == 147, and it crashes the kernel.
[1]
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069534/comments/20
I know SAUCE patches are to be avoided if possible, but Tj's solution
is minimal and fixes the root cause without the regression risk of
backporting the entire mini C runtime, so I suggest we go with Tj's
patch.
commit a4c616d2156c9c4cf7c91e6983c8bf0d51985df1
Author: Tj
Date: Fri Jul 26 13:48:44 2024 +
Subject: UBUNTU: SAUCE: arm64: v6.8: cmdline param >= 146 chars kills kernel
Link:
https://lore.kernel.org/stable/JsQ4W_o2R1NfPFTCCJjjksPED-8TuWGr796GMNeUMAdCh-2NSB_16x6TXcEecXwIfgzVxHzeB_-PMQnvQuDo0gmYE_lye0rC5KkbkDgkUqM=@proton.me/T/#u
[Testcase]
1) Deploy an ARM64 VM or use a bare metal ARM64 board with Noble, running 6.8.
2) Edit
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptab
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilte
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': re
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, ipt
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, ipt
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptab
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address exten
[Kernel-packages] [Bug 2070358] Re: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- 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/2070358 Title: [Ubuntu 24.04] FW1060.00 (NH1060_026) sosreport is running to Kernel OOPS crash Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Invalid Status in sosreport package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in sosreport source package in Noble: Invalid Bug description: SRU Justification: [Impact] * When the sosreport command is executed, a kernel OOPS happens and the system is crashing, depending on the configuration (but default) the system/LPAR is rebooting. [Fix] * e0011bca603c101f2a3c007bdb77f7006fa78fb1 e0011bca603c "nfsd: initialise nfsd_info.mutex early" [Test Case] * Have a Ubuntu Server 24.04 LTS installation on ppc64el. * one option is only running sosreport on the system - and the crash is seen when the sosreport is starting to capture dump * second option (without sosreport) is: * CONFIG_NFSD=m (or y) must be set * mount nfsd if not already, using "$ mount -t nfsd nfsd /proc/fs/nfsd" command * The kernel oops will happen and the logs will show: ... BUG: Kernel NULL pointer dereference on read at 0x Faulting instruction address: 0xc16ff114 Oops: Kernel access of bad area, sig: 11 [#1] ... * On a system with that kernel that incl. the above patch no oops will occur and the sosreport command will execute normally. [Regression Potential] * There is a certain risk of a regression, with any code modification, and here because the mutex handling in nfsd is modified. * But the changes are pretty traceable. * On top the commit is already upstream reviewed and accepted. * The modifications were done by the NFSD maintainer and also tested by IBM. [Other] * The fix/commit got upstream accepted with kernel v6.10-rc7, hence Oracular (with a planned kernel of >=6.10) is not affected. == Comment: #0 - Tasmiya Nalatwad - 2024-05-28 04:35:50 == --- Description --- When sosreport command is executed the kernel OOPS crash is happening and lpar is rebooting. As kdump was enabled the dump is captured. Note : The bug looks similar Bug 206504 Which is seen on z lpars. --- Lpar Details --- 1. PowerVM 2. FW: FW1060.00 (NH1060_026) 3. OS: Ubuntu 24.04 4. Kernel: 6.8.0-31-generic 5. Mem (free -mh): 47Gi 6. cpus: 40 --- Steps to reproduce --- 1. run sosreport command on the lpar and the crash is seen when the sosreport is starting to capture dump. --- Traces --- root@ubuntulp2host:~# sosreport Please note the 'sosreport' command has been deprecated in favor of the new 'sos' command, E.G. 'sos report'. Redirecting to 'sos report ' sosreport (version 4.5.6) This command will collect system configuration and diagnostic information from this Ubuntu system. For more information on Canonical visit: Community Website : https://www.ubuntu.com/ Commercial Support : https://www.canonical.com The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration. Press ENTER to continue, or CTRL-C to quit. Optionally, please enter the case id that you are generating this report for []: Setting up archive ... Setting up plugins ... [plugin:lxd] skipped command 'lxc image list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptable_filter, iptable_raw, ebtable_filter, ip6table_mangle, ebtables, iptable_nat, ip6_tables, ip6table_filter. [plugin:lxd] skipped command 'lxc network list': required kmods missing: ip6table_nat, ip6table_raw, bpfilter, iptable_mangle, iptab
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter)
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical addre
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address exten
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack] tcf_ct_ac
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (M
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE (Machine check exception)
[Kernel-packages] [Bug 2072428] Re: 6.8 generic & amdpgu / polaris
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2072428 Title: 6.8 generic & amdpgu / polaris Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: The amdgpu driver fails to initialise properly due to a bug introduced when trying to fix another bug (https://gitlab.freedesktop.org/drm/amd/-/issues/2925). This bug is already being tracked on freedesktop, and I tripped over it today when rebooting a machine that hadn't been rebooted in a while. The bug on freedesktop is https://gitlab.freedesktop.org/drm/amd/-/issues/3289 (it also affects some Fedora and other Linux distros). The bug is tagged with "Polaris" but the machine that is affected here is a RX 5500. The commit that introduced the bug is https://gitlab.freedesktop.org/agd5f/linux/-/commit/466a7d115326ece682c2b60d1c77d1d0b9010b4f I got a copy of linux-source-6.8.0 and confirmed that the offending line in the code is present. The issue was not present when using the linux-image- unsigned-6.10.0-061000rc4-generic deb from kernel.ubuntu.com Here's the details of the machine in question (I've attached complete logs to not fill up the text). # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 24.04 LTS Release: 24.04 Codename: noble boot line: Linux version 6.8.0-36-generic (buildd@lcy02-amd64-077) (x86_64-linux-gnu-gcc-13 (Ubuntu 13.2.0-23ubuntu4) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.42) #36-Ubuntu SMP PREEMPT_DYNAMIC Mon Jun 10 10:49:14 UTC 2024 (Ubuntu 6.8.0-36.36-generic 6.8.4) command line: BOOT_IMAGE=/boot/vmlinuz-6.8.0-36-generic root=UUID=2a38795c-259e-455e-aa40-29b51fb6dd29 ro quiet splash vt.handoff=7 subset of dmidecode: Handle 0x, DMI type 0, 26 bytes BIOS Information Vendor: American Megatrends Inc. Version: A.C0 Release Date: 04/24/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 16 MB Characteristics: PCI is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported BIOS ROM is socketed EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported BIOS boot specification is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 5.13 Handle 0x0002, DMI type 2, 15 bytes Base Board Information Manufacturer: Micro-Star International Co., Ltd. Product Name: B350M PRO-VDH (MS-7A38) Version: 2.0 Serial Number: XXX Asset Tag: To be filled by O.E.M. Features: Board is a hosting board Board is replaceable Location In Chassis: To be filled by O.E.M. Chassis Handle: 0x0003 Type: Motherboard Contained Object Handles: 0 Handle 0x0004, DMI type 9, 17 bytes System Slot Information Designation: J6B2 Type: x16 PCI Express Current Usage: In Use Length: Long ID: 0 Characteristics: 3.3 V is provided Opening is shared PME signal is supported Bus Address: :00:01.0 Handle 0x0014, DMI type 4, 48 bytes Processor Information Socket Designation: AM4 Type: Central Processor Family: Zen Manufacturer: Advanced Micro Devices, Inc. ID: 82 0F 80 00 FF FB 8B 17 Signature: Family 23, Model 8, Stepping 2 Flags: FPU (Floating-point unit on-chip) VME (Virtual mode extension) DE (Debugging extension) PSE (Page size extension) TSC (Time stamp counter) MSR (Model specific registers) PAE (Physical address extension) MCE
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x80 Jul 17 10:02:20 m
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8'
to 'verification-failed-jammy-linux-riscv-6.8'.
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-riscv-6.8-v2
verification-needed-jammy-linux-riscv-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072592] Re: Dangling symlink to linux-lib-rust when Rust is disabled
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2072592 Title: Dangling symlink to linux-lib-rust when Rust is disabled Status in linux package in Ubuntu: Triaged Status in linux source package in Noble: Fix Released Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2072592 [Impact] Commit: "UBUNTU: [Packaging] introduce do_lib_rust and enable it only on generic amd64" introduces the "do_lib_rust" variable in rules.d/ that avoids generating the extra rust package when unset/false. However, this is not checked when inserting a symlink to the linux-lib-rust package directory in the headers, resulting in a dangling symlink when rust is turned off. This can cause issues when e.g. building dkms modules against the headers, where the build will fail due to not finding the directory. [How to reproduce it] 1. Build linux-headers-* package for kernel with rust disabled (e.g. realtime) 2. Install (or extract) the package 3. View corresponding /usr/src/linux-headers-*/ directory 4. Observe /usr/src/linux-headers-*/rust -> ../linux-lib-rust-* but linux-lib-rust is never built and installed [Fix] Check the existing do_lib_rust variable is true before trying to symlink the linux-lib-rust files. [Test plan] 1. Apply the fix and rebuild the kernel headers packages 2. Install or inspect the headers 3. Ensure /usr/src/linux-headers-*/rust points to an existing directory [Regression potential] Very low. This is a simple fix, and it only impacts rust packaging for kernels with do_lib_rust unset/false so the visibility is low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2072592/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_time 3 -hls_segme
[Kernel-packages] [Bug 2073961] Re: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2073961 Title: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: This is a public version of: https://bugs.launchpad.net/bugs/2044673 [ Impact ] Add Lunar Lake-M PCI ID for processor thermal device. [ Fix ] Clean cherry pick from upstream. [ Test Plan ] Compiled. [ Where problems could occur ] Bad thermal management for Lunar Lake CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_tim
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disable
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500
[Kernel-packages] [Bug 2073961] Re: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2073961 Title: [SRU] Add Dynamic Tuning Technology (DTT) support for Lunar Lake Status in linux package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Bug description: This is a public version of: https://bugs.launchpad.net/bugs/2044673 [ Impact ] Add Lunar Lake-M PCI ID for processor thermal device. [ Fix ] Clean cherry pick from upstream. [ Test Plan ] Compiled. [ Where problems could occur ] Bad thermal management for Lunar Lake CPU. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_tim
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_time 3 -hls_segme
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_time 3 -hls_segment_type fmp4 -hls_fmp4
[Kernel-packages] [Bug 2072755] Re: i915: Fixup regressions introduced with enabling single CCS engine
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- 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/2072755 Title: i915: Fixup regressions introduced with enabling single CCS engine Status in linux package in Ubuntu: Fix Released Status in linux source package in Noble: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/2072755 [Impact] Recently, the Intel i915 susbsystem underwent a change that limited the number of CCS engines that were initialised by default, and exposed to the user. Different chipsets have differing amounts of CCS engines, but most available in the market have 4 CCS engines. The new change just starts a single engine only, and allocates all CCS slices to this single engine. This single engine is then exposed to userspace. This effort is to workaround a hardware bug. This all happened in: commit 6db31251bb265813994bfb104eb4b4d0f44d64fb Author: Andi Shyti Date: Thu Mar 28 08:34:05 2024 +0100 Subject: drm/i915/gt: Enable only one CCS for compute workload Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6db31251bb265813994bfb104eb4b4d0f44d64fb which landed in: $ git describe --contains 67f164e8510b16bda18642464863dba87a33d8cb Ubuntu-6.8.0-38.38~525 There have been some side effects as a result of these changes, leading to failure of userspace applications, namely in video transcoding with ffmepg, resulting in fence expiration errors in dmesg like: [ 81.026591] Fence expiration time out i915-:01:00.0:ffmpeg[521]:2! There has also been a performance impact introduced by this change, which dropped performance of the GPU to 1/4 of what it was previously. This is likely due to most ARC GPUs usually having 4 CCS engines, and going down to 1 only without actually allocating the other three. There are no workarounds. Users are suggested to downgrade to 6.8.0-36-generic while the fix is coming. [Fix] The regression was fixed by these two commits: commit aee54e282002a127612b71255bbe879ec0103afd Author: Andi Shyti Date: Fri Apr 26 02:07:23 2024 +0200 Subject: drm/i915/gt: Automate CCS Mode setting during engine resets Link: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/noble/commit/?id=aee54e282002a127612b71255bbe879ec0103afd commit ee01b6a386eaf9984b58a2476e8f531149679da9 Author: Andi Shyti Date: Fri May 17 11:06:16 2024 +0200 Subject: drm/i915/gt: Fix CCS id's calculation for CCS mode setting Link: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ee01b6a386eaf9984b58a2476e8f531149679da9 "drm/i915/gt: Automate CCS Mode setting during engine resets" is already applied to noble/master-next through upstream stable v6.8.10. We just need "drm/i915/gt: Fix CCS id's calculation for CCS mode setting". It is queued up for v6.9.4, but that could still be another SRU cycle or two away. So send it now. "drm/i915/gt: Fix CCS id's calculation for CCS mode setting" restores another 1/4 performance, but some performance issues still remain, and will hopefully be addressed in a future patch. [Testcase] This affects video transcoding with ffmpeg, on machines equipped with Intel ARC GPUs. An example ffmpeg command might be: /usr/lib/jellyfin-ffmpeg/ffmpeg -analyzeduration 200M -probesize 1G -ss 00:00:03.000 -noaccurate_seek -init_hw_device vaapi=va:,kernel_driver=i915,driver=iHD -init_hw_device qsv=qs@va -filter_hw_device qs -hwaccel vaapi -hwaccel_output_format vaapi -noautorotate -i file:"/path/to/1080_video.mkv" -noautoscale -map_metadata -1 -map_chapters -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 av1_qsv -preset veryfast -b:v 3616000 -maxrate 3616000 -bufsize 7232000 -g:v:0 72 -keyint_min:v:0 72 -vf "setparams=color_primaries=bt709:color_trc=bt709:colorspace=bt709,scale_vaapi=w=1280:h=720:format=nv12:extra_hw_frames=24,hwmap=derive_device=qsv,format=qsv" -codec:a:0 libfdk_aac -ac 2 -vbr:a 5 -copyts -avoid_negative_ts disabled -max_muxing_queue_size 2048 -f hls -max_delay 500 -hls_time 3 -hls_segment
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux- hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8' to 'verification-failed-jammy-linux-hwe-6.8'. 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-hwe-6.8-v2 verification-needed-jammy-linux-hwe-6.8 -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2072858] Re: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- 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/2072858 Title: Fix L2CAP/LE/CPU/BV-02-C bluetooth certification failure Status in OEM Priority Project: New Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux source package in Noble: Fix Released Bug description: SRU Jusitification for Kernel [Impact] Noble failed the L2CAP/LE/CPU/BV-02-C test in the Porfile Tuning Suite (PTS), which Jammy previously could pass. This is due to new behavior introduced in e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). The kernel only accept Connection Parameter Update Requests whose incoming conn_max_interval are lower than the current conn_max_interval, and adjust the newer conn_max_interval to that received max value. However, this behavior means that conn_max_interval can only decrease, but never increase. This could potentially make the conditions for connection parameters narrower over time, causing subsequent connections failed on some devices. See the issue 847 in bluez upstream[1]. The patch 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ) in the linux-next fixed this by accepting connection parameter unconditionally. The relavent test procedure is also on the mailing list[2]. [1] https://github.com/bluez/bluez/issues/847 [2] https://linuxlists.cc/l/15/linux-bluetooth/t/5350289/(patch_v3)_bluetooth:_l2cap:_fix_rejecting_l2cap_conn_param_update_req#post5352326 [Fix] Backport the from commit 806a5198c05987b748b50f3d0c0cfb3d417381a4 (Bluetooth: L2CAP: Fix rejecting L2CAP_CONN_PARAM_UPDATE_REQ), which currently is in the linux-next. [1] https://patchwork.kernel.org/project/bluetooth/patch/20240521143521.1568672-1-luiz.de...@gmail.com/ [Test Case] 1. Install the kernel with the backported patch 2. Run the following test case in the PTS: L2CAP/LE/CPU/BV-02-C GAP/CONN/CPUP/BV-05-C [Where problems could occur] This essentially revert the behavior of accepting L2CAP connection parameters back to its original state before e4b019515f950b4e6e5b74b2e1bb03a90cb33039 (Bluetooth: Enforce validation on max value of connection interval). Note that implementing restriction to the conenction parameters may take greater effort than just adding a few checks in the kernel. The user space, notably the bluetoothd may also need adjustments[1]. So in this case, removing the half-done boundary checks in kernel may still do greater good if there's no plan to make those additional changes. [1] https://github.com/bluez/bluez/issues/717#issuecomment-1885719058 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2072858/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-lowlatency-
hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency-
hwe-6.8'. If the problem still exists, change the tag 'verification-
needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy-
linux-lowlatency-hwe-6.8'.
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-lowlatency-hwe-6.8-v2
verification-needed-jammy-linux-lowlatency-hwe-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the
problem still exists, change the tag 'verification-needed-jammy-linux-
oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'.
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-oracle-6.8-v2
verification-needed-jammy-linux-oracle-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.8'
to 'verification-failed-jammy-linux-aws-6.8'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2
verification-needed-jammy-linux-aws-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8'
to 'verification-failed-jammy-linux-ibm-6.8'.
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-ibm-6.8-v2
verification-needed-jammy-linux-ibm-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-azure-6.8'
to 'verification-failed-jammy-linux-azure-6.8'.
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!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-aws-6.8'
to 'verification-failed-jammy-linux-aws-6.8'.
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-azure-6.8-v2
verification-needed-jammy-linux-azure-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-
hwe-6.8/6.8.0-44.44~22.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-jammy-linux-
hwe-6.8' to 'verification-done-jammy-linux-hwe-6.8'. If the problem
still exists, change the tag 'verification-needed-jammy-linux-hwe-6.8'
to 'verification-failed-jammy-linux-hwe-6.8'.
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-hwe-6.8-v2
verification-needed-jammy-linux-hwe-6.8
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073049] Re: No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12
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-noble-linux-raspi' to 'verification-done-noble-
linux-raspi'. If the problem still exists, change the tag 'verification-
needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'.
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-noble-linux-raspi-v2
verification-needed-noble-linux-raspi
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.8 in Ubuntu.
https://bugs.launchpad.net/bugs/2073049
Title:
No sound on Huawei Matebook D14 AMD since Linux 6.8.0-38 [regression]
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.8 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Fix Released
Status in linux-oem-6.8 source package in Noble:
Fix Released
Bug description:
This laptop has had non-functioning internal sound (based on AMD
Renoir) until Ubuntu 24.04, which made it work thanks to a bugfix in
the kernel.
Unfortunately, the sound is completely broken with kernel from package
"linux-image-6.8.0-38-generic" (6.8.0-38.38): the internal speakers
are not even listed in the sound GUI (I am using "mate-volume-
control", with Ubuntu-Mate.
When I boot the laptop on Linux 6.8.0-36-generic, the speakers are
listed and the sound works normally.
This might be related to this bug in Linux kernel:
https://bugzilla.kernel.org/show_bug.cgi?id=218959
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: linux-image-6.8.0-38-generic 6.8.0-38.38
ProcVersionSignature: Ubuntu 6.8.0-38.38-generic 6.8.8
Uname: Linux 6.8.0-38-generic x86_64
ApportVersion: 2.28.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/seq:julier 2643 F pipewire
/dev/snd/pcmC0D3p: julier 2643 F...m pipewire
/dev/snd/controlC0: julier 2645 F wireplumber
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Sun Jul 14 11:03:18 2024
InstallationDate: Installed on 2022-04-18 (818 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Daily amd64
(20220418)
MachineType: HUAWEI HVY-WXX9
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-38-generic
root=UUID=e5259488-061f-48f2-b6ca-9ebd58053ca3 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.8.0-38-generic N/A
linux-backports-modules-6.8.0-38-generic N/A
linux-firmware20240318.git3b128b60-0ubuntu2.1
SourcePackage: linux
UpgradeStatus: Upgraded to noble on 2024-04-28 (76 days ago)
dmi.bios.date: 03/17/2023
dmi.bios.release: 2.17
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.17
dmi.board.asset.tag: N/A
dmi.board.name: HVY-WXX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.17
dmi.modalias:
dmi:bvnHUAWEI:bvr2.17:bd03/17/2023:br2.17:efr2.17:svnHUAWEI:pnHVY-WXX9:pvrM1010:rvnHUAWEI:rnHVY-WXX9-PCB-B1:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: HVY-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI
[Impact]
Huawei MateBook D14 AMD got no sound after commit:
4af565de9f8c ("ASoC: amd: acp: fix for acp pdm configuration check")
which is introduced in v6.8.5 stable updates.
[Fix]
Invokes platform specific acp pin configuration check functions.
Upstream fix:
09068d624c490 ("ASoC: amd: acp: fix for acp platform device creation failure")
[Test]
Bug reporter tested on hardware, sound output OK.
Also verified on ThinkPad T14 AMD, sound output OK too.
[Where problems could occur]
It may break sound output of AMD platforms.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2073049/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrac
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- ibm-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- ibm-6.8' to 'verification-done-jammy-linux-ibm-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-ibm-6.8' to 'verification-failed-jammy-linux-ibm-6.8'. 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-ibm-6.8-v2 verification-needed-jammy-linux-ibm-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack] tcf_ct_ac
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x49
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrac
[Kernel-packages] [Bug 2073092] Re: net/sched: Fix conntrack use-after-free
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073092 Title: net/sched: Fix conntrack use-after-free Status in linux package in Ubuntu: Invalid Status in linux-hwe-6.8 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-hwe-6.8 source package in Jammy: Fix Released Status in linux source package in Noble: Fix Released Status in linux-hwe-6.8 source package in Noble: Invalid Status in linux source package in Oracular: Invalid Status in linux-hwe-6.8 source package in Oracular: Invalid Bug description: BugLink: https://bugs.launchpad.net/bugs/2073092 [Impact] Hit conntrack refcount use-after-free issue: refcount_t: addition on 0; use-after-free. Call Trace: ? show_regs+0x6d/0x80 ? __warn+0x89/0x160 ? refcount_warn_saturate+0x12e/0x150 ? report_bug+0x17e/0x1b0 ? handle_bug+0x46/0x90 ? exc_invalid_op+0x18/0x80 ? asm_exc_invalid_op+0x1b/0x20 ? refcount_warn_saturate+0x12e/0x150 flow_offload_alloc+0xe5/0xf0 [nf_flow_table] tcf_ct_flow_table_process_conn+0xc2/0x1e0 [act_ct] tcf_ct_act+0x6c8/0xaa0 [act_ct] tcf_action_exec+0xbc/0x1a0 fl_classify+0x1f8/0x200 [cls_flower] __tcf_classify+0x169/0x200 tcf_classify+0xff/0x250 sch_handle_ingress.constprop.0+0x11f/0x290 ? srso_alias_return_thunk+0x5/0x7f __netif_receive_skb_core.constprop.0+0x60b/0xd70 ? __udp4_lib_lookup+0x25f/0x2a0 __netif_receive_skb_list_core+0xfd/0x250 netif_receive_skb_list_internal+0x1a3/0x2d0 ? srso_alias_return_thunk+0x5/0x7f ? dev_gro_receive+0x196/0x350 napi_complete_done+0x74/0x1c0 gro_cell_poll+0x7c/0xb0 __napi_poll+0x33/0x1f0 net_rx_action+0x181/0x2e0 __do_softirq+0xdc/0x349 ? srso_alias_return_thunk+0x5/0x7f ? handle_irq_event+0x52/0x80 ? handle_edge_irq+0xda/0x250 __irq_exit_rcu+0x75/0xa0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa4/0xb0 [Fix] I enabled kasan and get: BUG: KASAN: slab-use-after-free in tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] Read of size 1 at addr 888c07603600 by task handler130/6469 Call Trace: dump_stack_lvl+0x48/0x70 print_address_description.constprop.0+0x33/0x3d0 print_report+0xc0/0x2b0 kasan_report+0xd0/0x120 __asan_load1+0x6c/0x80 tcf_ct_flow_table_process_conn+0x12b/0x380 [act_ct] tcf_ct_act+0x886/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 __irq_exit_rcu+0x82/0xc0 irq_exit_rcu+0xe/0x20 common_interrupt+0xa1/0xb0 Allocated by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_alloc_info+0x1e/0x40 __kasan_krealloc+0x133/0x190 krealloc+0xaa/0x130 nf_ct_ext_add+0xed/0x230 [nf_conntrack] tcf_ct_act+0x1095/0x1350 [act_ct] tcf_action_exec+0xf8/0x1f0 fl_classify+0x355/0x360 [cls_flower] __tcf_classify+0x1fd/0x330 tcf_classify+0x21c/0x3c0 sch_handle_ingress.constprop.0+0x2c5/0x500 __netif_receive_skb_core.constprop.0+0xb25/0x1510 __netif_receive_skb_list_core+0x220/0x4c0 netif_receive_skb_list_internal+0x446/0x620 napi_complete_done+0x157/0x3d0 gro_cell_poll+0xcf/0x100 __napi_poll+0x65/0x310 net_rx_action+0x30c/0x5c0 __do_softirq+0x14f/0x491 Freed by task 6469: kasan_save_stack+0x38/0x70 kasan_set_track+0x25/0x40 kasan_save_free_info+0x2b/0x60 kasan_slab_free+0x180/0x1f0 __kasan_slab_free+0x12/0x30 slab_free_freelist_hook+0xd2/0x1a0 __kmem_cache_free+0x1a2/0x2f0 kfree+0x78/0x120 nf_conntrack_free+0x74/0x130 [nf_conntrack] nf_ct_destroy+0xb2/0x140 [nf_conntrack] __nf_ct_resolve_clash+0x529/0x5d0 [nf_conntrack] nf_ct_resolve_clash+0xf6/0x490 [nf_conntrack] __nf_conntrack_confirm+0x2c6/0x770 [nf_conntrack] tcf_ct_act+0x12ad/0x1350 [act_c
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- riscv-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- riscv-6.8' to 'verification-done-jammy-linux-riscv-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-riscv-6.8' to 'verification-failed-jammy-linux-riscv-6.8'. 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-riscv-6.8-v2 verification-needed-jammy-linux-riscv-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x80 Jul
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- oracle-6.8/6.8.0-1012.12~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-done-jammy-linux-oracle-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux- oracle-6.8' to 'verification-failed-jammy-linux-oracle-6.8'. 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-oracle-6.8-v2 verification-needed-jammy-linux-oracle-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux-lowlatency- hwe-6.8/6.8.0-44.44.1~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- lowlatency-hwe-6.8' to 'verification-done-jammy-linux-lowlatency- hwe-6.8'. If the problem still exists, change the tag 'verification- needed-jammy-linux-lowlatency-hwe-6.8' to 'verification-failed-jammy- linux-lowlatency-hwe-6.8'. 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-lowlatency-hwe-6.8-v2 verification-needed-jammy-linux-lowlatency-hwe-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- aws-6.8/6.8.0-1015.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- aws-6.8' to 'verification-done-jammy-linux-aws-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.8' to 'verification-failed-jammy-linux-aws-6.8'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux-aws-6.8-v2 verification-needed-jammy-linux-aws-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x80 Jul 17 10:02:20 m
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux- azure-6.8/6.8.0-1014.16~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux- azure-6.8' to 'verification-done-jammy-linux-azure-6.8'. If the problem still exists, change the tag 'verification-needed-jammy-linux-azure-6.8' to 'verification-failed-jammy-linux-azure-6.8'. 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-azure-6.8-v2 verification-needed-jammy-linux-azure-6.8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x80 Jul
[Kernel-packages] [Bug 2073358] Re: Kubuntu 24.04 freezes after plugging in ethernet cable
This bug is awaiting verification that the linux-raspi/6.8.0-1011.12 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-noble-linux-raspi' to 'verification-done-noble- linux-raspi'. If the problem still exists, change the tag 'verification- needed-noble-linux-raspi' to 'verification-failed-noble-linux-raspi'. 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-noble-linux-raspi-v2 verification-needed-noble-linux-raspi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.8 in Ubuntu. https://bugs.launchpad.net/bugs/2073358 Title: Kubuntu 24.04 freezes after plugging in ethernet cable Status in linux package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: Invalid Status in linux source package in Noble: Fix Released Status in linux-oem-6.8 source package in Noble: Fix Released Bug description: I can reliably reproduce this freeze by: 1. Waking my Thinkpad T490 from suspend 2. Plugging in the ethernet cable The result is a total system freeze; it's not possible to do anything, neither mouse nor keyboard work - the only way to shutdown is via REISUB. I've attached a dmesg log, starting at the time I plugged in the cable. It starts with: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: e1000e :00:1f.6 enp0s31f6: NIC Link is Up 1000 Mbps Half Duplex, Flow Control: None Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: BUG: scheduling while atomic: kworker/7:4/23723/0x0002 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Modules linked in: bnep snd_seq_dummy snd_hrtimer snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device cmac ccm nf_tables libcrc32c qrtr snd_sof_pci_intel_cnl snd_sof_intel_hda_common soundwire_intel snd_sof_intel_hda_mlink soundwire_cadence snd_sof_intel_hda snd_sof_pci snd_hda_codec_hdmi snd_sof_xtensa_dsp snd_sof snd_sof_utils snd_soc_hdac_hda snd_hda_ext_core snd_ctl_led snd_soc_acpi_intel_match snd_soc_acpi snd_hda_codec_realtek soundwire_generic_allocation snd_hda_codec_generic soundwire_bus snd_soc_core intel_uncore_frequency snd_compress ac97_bus intel_uncore_frequency_common snd_pcm_dmaengine intel_pmc_core_pltdrv intel_pmc_core snd_hda_intel binfmt_misc btusb intel_vsec uvcvideo btrtl snd_intel_dspcfg pmt_telemetry cmdlinepart videobuf2_vmalloc pmt_class snd_intel_sdw_acpi btintel iwlmvm processor_thermal_device_pci_legacy uvc spi_nor intel_tcc_cooling snd_hda_codec btbcm processor_thermal_device videobuf2_memops processor_thermal_wt_hint x86_pkg_temp_thermal nls_iso8859_1 mtd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: mei_hdcp mei_pxp ee1004 intel_rapl_msr mac80211 videobuf2_v4l2 btmtk snd_hda_core intel_powerclamp videodev snd_hwdep processor_thermal_rfim i915 libarc4 bluetooth coretemp processor_thermal_rapl iwlwifi snd_pcm drm_buddy videobuf2_common spi_intel_pci think_lmi rapl intel_rapl_common ecdh_generic ttm processor_thermal_wt_req intel_cstate drm_display_helper i2c_i801 firmware_attributes_class intel_wmi_thunderbolt mc wmi_bmof ecc processor_thermal_power_floor spi_intel mei_me snd_timer cec cfg80211 i2c_smbus processor_thermal_mbox rc_core intel_soc_dts_iosf mei i2c_algo_bit intel_pch_thermal thinkpad_acpi int3403_thermal nvram int340x_thermal_zone int3400_thermal acpi_thermal_rel acpi_pad joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore nfnetlink dmi_sysfs ip_tables x_tables autofs4 hid_generic usbhid hid dm_crypt rtsx_pci_sdmmc crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic nvme ghash_clmulni_intel snd sha256_ssse3 intel_lpss_pci ucsi_acpi nvme_core soundcore Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: typec_ucsi sha1_ssse3 intel_lpss xhci_pci video psmouse e1000e rtsx_pci nvme_auth idma64 typec xhci_pci_renesas ledtrig_audio platform_profile wmi pinctrl_cannonlake aesni_intel crypto_simd cryptd Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: CPU: 7 PID: 23723 Comm: kworker/7:4 Not tainted 6.8.0-38-generic #38-Ubuntu Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Hardware name: LENOVO 20N3S7BC02/20N3S7BC02, BIOS N2IETA4W (1.82 ) 02/22/2024 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Workqueue: events e1000_watchdog_task [e1000e] Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Call Trace: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack_lvl+0x76/0xa0 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: dump_stack+0x10/0x20 Jul 17 10:02:20 matthias-ThinkPad-T490 kernel: __schedule_bug+0x64/0x80 Jul 17 10:02:20 matthias-ThinkPad-T490
