[Kernel-packages] [Bug 2066885] Re: On Pi desktop, numerous reports of lack of landlock supported ABI
I'm going to add linux-raspi as affected here given this is (at least partially) down to a linux-raspi configuration difference. Kernel team: is there a reason landlock is disabled in the Pi kernel? Seems to work happily on a Pi 5, but perhaps there was some incompatibility with earlier models? ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2066885 Title: On Pi desktop, numerous reports of lack of landlock supported ABI Status in linux-raspi package in Ubuntu: New Status in tracker-miners package in Ubuntu: New Bug description: On the Ubuntu noble desktop for Raspberry Pi, the system journal has numerous of the following entries: May 23 10:30:29 kermit tracker-miner-f[11130]: Could not get landlock supported ABI: Operation not supported May 23 10:30:29 kermit tracker-miner-f[11130]: Refusing to extract file data since Landlock could not be enabled. Update your kernel to fix this warning. These appear to be written every time a file in my home directory is modified. The kernel is the stock noble kernel from linux-raspi, 6.8.0-1004-raspi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2066885/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861338] Re: RPI4 wifi unreliable when usb3 storage is attached
That's a different issue, LP: #2063365, which only started occurring after the recent wifi firmware bump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861338 Title: RPI4 wifi unreliable when usb3 storage is attached Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Eoan: Expired Bug description: On RPI4, if you set up netplan to use wifi, and plug in a usb3 storage device to one of the 2x usb3 ports (the ones closest to the ethernet port), wifi will sudden stop working. If you unplug the usb stick while running a ping, it will usually start working again almost instantaneously. Kernel version I have is: 5.3.0-1017-raspi2 and I've confirmed this happens on both armhf and arm64 The only thing I found in journalctl that looks suspicious is this, but it seems to have happened before plugging in the usb stick: Jan 29 20:54:59 ubuntu wpa_supplicant[1129]: random: Cannot read from /dev/random: Resource temporarily unavailable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1861338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062667] Re: Fails on (and should be removed from) raspi desktop
** Also affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: Confirmed Status in qrtr package in Ubuntu: Confirmed Status in ubuntu-meta package in Ubuntu: Confirmed Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063255] [NEW] Cannot play audio from server on older models
Public bug reported: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, now maintained by Nanakos Chrysostomos and others. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Love on a Real Train Artist : State Azure Album : Dreams A Tribute to Tangerin Year : 2020 Comment :Genre : AmbientElectronic Playing MPEG stream from test.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B and 3B+. It appears to work happily on the 4B, though. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2063255 Title: Cannot play audio from server on older models Status in linux-raspi package in Ubuntu: New Bug description: While attempting to play music as part of the ISO tests for the release, while the vc4hdmi sound card appears in /proc/asound/cards, the mpg321 player used by the tests (which has never worked *well* on the older models, but at least worked) failed with: [0.029s] ubuntu@miss-piggy:~$ mpg321 -o alsa -a hw:1,0 test.mp3 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3. Version 0.3.2-1 (2012/03/25). Written and copyrights by Joe Drew, now maintained by Nanakos Chrysostomos and others. Uses code from various people. See 'README' for more! THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK! Title : Love on a Real Train Artist : State Azure Album : Dreams A Tribute to Tangerin Year : 2020 Comment :Genre : AmbientElectronic Playing MPEG stream from test.mp3 ... MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo Can't open libao driver with device hw:1,0 (is device in use?) I also tried ffmpeg (which usually works a bit better on the older models) and that fails with a constant series of ALSA buffer xrun errors. The specific models on which this has failed so far are the 2B and 3B+. It appears to work happily on the 4B, though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2063255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2062667] [NEW] Fails on (and should be removed from) raspi desktop
Public bug reported: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 ** Affects: protection-domain-mapper (Ubuntu) Importance: Undecided Status: New ** Affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Also affects: qrtr (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Fails (and should be removed from) raspi desktop + Fails on (and should be removed from) raspi desktop -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to qrtr in Ubuntu. https://bugs.launchpad.net/bugs/2062667 Title: Fails on (and should be removed from) raspi desktop Status in protection-domain-mapper package in Ubuntu: New Status in qrtr package in Ubuntu: New Bug description: The protection-domain-mapper package (and qrtr-tools) are both installed by default on the Ubuntu Desktop for Raspberry Pi images, thanks to their inclusion in the desktop-minimal seed for arm64. However, there's no hardware that they target on these platforms, and the result is a permanently failed service (pd-mapper.service). It appears these were added to support the X13s laptop [1]. I've attempted to work around the issue by excluding these packages in the desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but this does not work (the packages still appear in the built images). Ideally, these packages should be moved into a hardware-specific seed for the X13s (and/or whatever other laptops need these things). Alternatively, at a bare minimum, the package should have some conditional that causes the service not to attempt to start when it's not on Qualcomm hardware. [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu- seeds/+git/ubuntu/commit/desktop- minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a [2]: https://git.launchpad.net/~waveform/ubuntu- seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038924] Re: No alsa sound cards on Pi 5
** Changed in: linux-raspi (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 Status in linux-raspi package in Ubuntu: Fix Released Bug description: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929791] Re: Bluetooth does not start if system boots from USB
I haven't managed to reproduce this on several systems (pi4 booting from USB, pi5 booting from NVMe, etc). Setting to incomplete until anyone can come up with a firm reproduction case. ** Changed in: pi-bluetooth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1929791 Title: Bluetooth does not start if system boots from USB Status in linux-raspi2 package in Ubuntu: Invalid Status in pi-bluetooth package in Ubuntu: Incomplete Bug description: Hello! I have a strange bug with Bluetooth on Raspberry Pi 4 8Gb and Ubuntu 21.04 (also had it on Ubuntu 20.10). It's internal Bluetooth adapder does not initialize, if I boot system from USB, wherein does not matter what I am using: 16 Gb USB Flash Drive, 2 Tb External USB HDD or 1 Tb External SSD. After system boot up, it shows me "no Bluetooth adapters found", hcidev also shows nothing. I'm getting hciuart.service error: === taras@taras-rpi:~$ systemctl status hciuart.service ● hciuart.service - Configure Bluetooth Modems connected by UART Loaded: loaded (/lib/systemd/system/hciuart.service; enabled; vendor prese> Active: failed (Result: exit-code) since Thu 2021-05-27 08:22:57 EEST; 3mi> Process: 599 ExecStart=/usr/bin/btuart (code=exited, status=1/FAILURE) тра 27 08:22:46 taras-rpi systemd[1]: Starting Configure Bluetooth Modems conne> тра 27 08:22:57 taras-rpi btuart[631]: Initialization timed out. тра 27 08:22:57 taras-rpi btuart[631]: bcm43xx_init тра 27 08:22:57 taras-rpi btuart[631]: Flash firmware /lib/firmware/brcm/BCM434> тра 27 08:22:57 taras-rpi btuart[631]: Set Controller UART speed to 300 bit> тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Control process exited, > тра 27 08:22:57 taras-rpi systemd[1]: hciuart.service: Failed with result 'exit> тра 27 08:22:57 taras-rpi systemd[1]: Failed to start Configure Bluetooth Modem> === But if I continue reboot system, it may appear in 1-2 cases from 10. It'v very strange. If I disable this service manually via: === sudo systemctl disable hciuart.service === restart the system and run: === sudo systemctl start hciuart.service === Bluetooth adapter will appear in 100% cases. And if I boot Ubuntu from microSD card, everything works properly, Bluetooth starts all times. I thought, mb here is not enougth power for USB devices. I've bought USB hub with external power, but it does not help. Must say, that I don't have this problem on Raspberry Pi OS, I have it on USB HDD too and it works without any problems. Any suggestions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1929791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060942] [NEW] Missing power LED on earlier models
Public bug reported: The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the kernel starts booting under noble (I hope this is only on noble; I only just noticed this during ISO testing and it's quite possible I missed it on earlier revisions...). Specifically, on the 2W (which only has a combined activity and power LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes it illuminate by default and blink off during mmc0 activity. This trigger setting appears to be unavailable under the Ubuntu kernel. On the 2B and 3B, the trigger is set to [none] which results in the LED initially illuminating while the bootloader is running and then disappearing. The default under RaspiOS is [input] which makes it illuminate normally, but switch off on undervolt. This trigger settging also appears unavailable under the Ubuntu kernel. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: raspi-image rls-nn-incoming ** Tags added: raspi-image ** Changed in: linux-raspi (Ubuntu) Status: New => Confirmed ** Tags added: rls-nn-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060942 Title: Missing power LED on earlier models Status in linux-raspi package in Ubuntu: Confirmed Bug description: The Pi Zero 2W, 2B, and 3B all fail to light their power LED once the kernel starts booting under noble (I hope this is only on noble; I only just noticed this during ISO testing and it's quite possible I missed it on earlier revisions...). Specifically, on the 2W (which only has a combined activity and power LED), /sys/class/leds/ACT/trigger is [actpwr] on RaspiOS, which makes it illuminate by default and blink off during mmc0 activity. This trigger setting appears to be unavailable under the Ubuntu kernel. On the 2B and 3B, the trigger is set to [none] which results in the LED initially illuminating while the bootloader is running and then disappearing. The default under RaspiOS is [input] which makes it illuminate normally, but switch off on undervolt. This trigger settging also appears unavailable under the Ubuntu kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1942260] Re: compress firmware in /lib/firmware
This was fixed with version 11 of linux-firmware-raspi in noble; I don't see a great deal of point in expending the effort to backport this to mantic, however, so I'll set that to invalid. ** Changed in: linux-firmware-raspi (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux-firmware-raspi (Ubuntu Mantic) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1942260 Title: compress firmware in /lib/firmware Status in firmware-sof package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware-raspi package in Ubuntu: Fix Released Status in firmware-sof source package in Mantic: Fix Released Status in initramfs-tools source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-firmware-raspi source package in Mantic: Won't Fix Bug description: -- initramfs-tools [Impact] * linux supports xz compressed linux-firmware which saves disk space. In focal, initramfs-tools only knows how to included uncompressed firmware files (even when kernel supports loading compressed ones). Newer releases of linux-firmware may use compressed firmware files only, in such cases it would be nice for focal's initramfs-tools to support compressed firmware files in case of partial or incomplete upgrades (i.e. linux-firmware force installed or upgraded, without newer initramfs-tools). The proposed changes to initramfs-tools are backwards and forwards compatible, they prefer to include uncompressed firmware files; and if missing, include compressed firmware files in their uncompressed form. Thus maintaining compatibility with any kernels, irrespective of compressed/uncompressed firmware inputs. [Test Plan] * Compress all files shipped by linux-firmware with xz * Rebuild initrd * Check that all the same firmware files are still included in the initramfs, in their uncompressed form as before [Where problems could occur] * This SRU is precautionary to prevent accidental installation of compressed linux-firmware from generating incorrect initramfs. It should be noted that whilst initramfs-tools would create a compatible initramfs with any kernels, pre-v5.3 kernels do not support xz compressed firmware files at runtime. Mixing this new initramfs with compressed firmwares and pre 5.3 kernels may lead to expectations of supporting compressed firmware files with them only working at initrd stage and not at runtime. [Other Info] Original bug report Some facts: - The linux kernel has supported loading xz compressed firmware since 5.3 - The size of /lib/firmware in impish is ~650Mb (and growing) - The compressed size of firmware could be ~230Mb It would be nice to install compressed firmware to save space. Here are the plans from the Fedora project: https://fedoraproject.org/wiki/Changes/CompressKernelFirmware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060677] [NEW] Consistent (zfs?) errors at shutdown
Public bug reported:
When shutting down Ubuntu noble desktop on my Pi 5, I consistently see
the following kernel errors briefly flash by before the machine shuts
down:
kernel: spl: loading out-of-tree module taints kernel.
kernel: zfs: module license 'CDDL' taints kernel.
kernel: Disabling lock debugging due to kernel taint
kernel: zfs: module license taints kernel.
kernel: warning: `sssd' uses wireless extensions which will stop working for
Wi-Fi 7 hardware; use nl80211
kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: {
3- } 21 jiffies s: 1069 root: 0x8/.
kernel: rcu: blocking rcu_node structures (internal RCU debug):
kernel: Sending NMI from CPU 0 to CPUs 3:
kernel: NMI backtrace for cpu 3
kernel: CPU: 3 PID: 2587 Comm: modprobe Tainted: P C OE
6.8.0-1002-raspi #2-Ubuntu
kernel: Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
kernel: pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
kernel: pc : sha256_generic+0x2e8/0x10f0 [zfs]
kernel: lr : sha256_generic+0x74/0x10f0 [zfs]
kernel: sp : 80008389b530
kernel: x29: 80008389b610 x28: 0020 x27: 30cb87d6
kernel: x26: 94167d04 x25: 1f181b79 x24: 744284b5
kernel: x23: d7aa2aa2 x22: 9f4c26c4 x21: 6c0c81ee
kernel: x20: 08800200 x19: 24378176 x18: 6617aa55
kernel: x17: ba448af2b8b7d59f x16: 56020089 x15: 3260389f
kernel: x14: 0b8e0f17 x13: bc12729b x12: 73d5aafc
kernel: x11: c2299b63 x10: 53710f11 x9 : 9e42204d
kernel: x8 : 4640c118 x7 : d5eb7d70 x6 : 5405775e
kernel: x5 : 0c7ffd41 x4 : b05fee52 x3 : 22c23503
kernel: x2 : a00063fc72c0 x1 : 0023 x0 : aa422449
kernel: Call trace:
kernel: sha256_generic+0x2e8/0x10f0 [zfs]
kernel: sha256_update+0x138/0x228 [zfs]
kernel: SHA2Update+0x4c/0x60 [zfs]
kernel: sha_incremental+0x2c/0x48 [zfs]
kernel: abd_iterate_func+0x104/0x150 [zfs]
kernel: abd_checksum_sha256+0x60/0xe8 [zfs]
kernel: chksum_run+0xac/0x160 [zfs]
kernel: chksum_benchit+0x140/0x198 [zfs]
kernel: chksum_benchmark+0x1ac/0x3a8 [zfs]
kernel: chksum_init+0x28/0xa8 [zfs]
kernel: spa_init+0x130/0x168 [zfs]
kernel: zfs_kmod_init+0x4c/0x108 [zfs]
kernel: openzfs_init_os+0x1c/0xc8 [zfs]
kernel: openzfs_init+0x70/0xcd0 [zfs]
kernel: do_one_initcall+0x4c/0x368
kernel: do_init_module+0xa0/0x260
kernel: load_module+0x790/0x8c8
kernel: init_module_from_file+0x94/0xf8
kernel: idempotent_init_module+0x178/0x2a8
kernel: __arm64_sys_finit_module+0x6c/0xd8
kernel: invoke_syscall+0x50/0x120
kernel: el0_svc_common.constprop.0+0x48/0xf0
kernel: do_el0_svc+0x24/0x38
kernel: el0_svc+0x48/0x178
kernel: el0t_64_sync_handler+0x120/0x130
kernel: el0t_64_sync+0x1a8/0x1b0
I'm unsure why the kernel is attempting to load zfs on shutdown, or why
this error occurs but it does seem consistent (I've got at least 5
separate backtraces similar to the above on shutdown in my kern.log).
** Affects: linux-raspi (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/2060677
Title:
Consistent (zfs?) errors at shutdown
Status in linux-raspi package in Ubuntu:
New
Bug description:
When shutting down Ubuntu noble desktop on my Pi 5, I consistently see
the following kernel errors briefly flash by before the machine shuts
down:
kernel: spl: loading out-of-tree module taints kernel.
kernel: zfs: module license 'CDDL' taints kernel.
kernel: Disabling lock debugging due to kernel taint
kernel: zfs: module license taints kernel.
kernel: warning: `sssd' uses wireless extensions which will stop working
for Wi-Fi 7 hardware; use nl80211
kernel: rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: {
3- } 21 jiffies s: 1069 root: 0x8/.
kernel: rcu: blocking rcu_node structures (internal RCU debug):
kernel: Sending NMI from CPU 0 to CPUs 3:
kernel: NMI backtrace for cpu 3
kernel: CPU: 3 PID: 2587 Comm: modprobe Tainted: P C OE
6.8.0-1002-raspi #2-Ubuntu
kernel: Hardware name: Raspberry Pi 5 Model B Rev 1.0 (DT)
kernel: pstate: 8049 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
kernel: pc : sha256_generic+0x2e8/0x10f0 [zfs]
kernel: lr : sha256_generic+0x74/0x10f0 [zfs]
kernel: sp : 80008389b530
kernel: x29: 80008389b610 x28: 0020 x27: 30cb87d6
kernel: x26: 94167d04 x25: 1f181b79 x24: 744284b5
kernel: x23: d7aa2aa2 x22: 9f4c26c4 x21: 6c0c81ee
kernel: x20: 08800200 x19: 24378176 x18: 6617aa55
kernel: x17: ba448a
[Kernel-packages] [Bug 2052861] Re: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10
I believe this is also "fixed" (or rather wasn't an issue) with the noble kernel; at least testing the current noble desktop beta image from an SD card shows an NVMe drive attached to a pimoroni base. I'll mark this as Fix Released; please feel free to re-open if this re-appears on the noble images. ** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2052861 Title: NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Mantic: Fix Released Bug description: [Impact] NVMe devices connected via PCIe are not enumerated on Raspberry Pi 5. [Fix] https://github.com/raspberrypi/linux/commit/2677529a4f8a50c7567f50d67f368f1d138fb4d2 [Test Case] Check whether NVMe devices connected via PCIe are detected with lspci/lsblk. [Where Problems Could Occur] PCIe devices might misbehave. [Original Description] NVME devices are not enumerated on Raspberry PI 5 with Ubuntu 23.10 I've got one of the PCIe NVME extension HATs for rpi 5 [1] and installed a functioning NVME drive Samsung SM961. Tried to boot it first with an image of RaspberryPI OS from sd-card. Upon boot, the nvme drive was detected and I could mount it and perform some IO: > uname -a Linux raspberrypi 6.1.0-rpi8-rpi-2712 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 0001:01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 dmesg logs of rpios will be attached, but there is nothing suspicious. Then I've tried to run Ubuntu 23.10 and reimaged the sd-card with "Ubuntu Server 23.10 (64-bit) (released 2023-10-12). Upon boot, the drive didn't show up: > lspci -nnk 00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport 01:00.0 Ethernet controller [0200]: Device [1de4:0001] Kernel driver in use: rp1 Checked for updates and there was a newer kernel available, thus I've upgraded: > apt update > apt list --upgradable ... linux-image-raspi/mantic-updates,mantic-security 6.5.0.1010.11 arm64 [upgradable from: 6.5.0.1005.6] After reboot, the nvme still didn't show up. Full dmesg log is attached, but in essence the pcie driver is having troubles to enumerate one for devices on the bus: [0.00] Booting Linux on physical CPU 0x00 [0x414fd0b1] [0.00] Linux version 6.5.0-1010-raspi (buildd@bos03-arm64-017) (aarch64-linux-gnu-gcc-13 (Ubuntu 13.2.0-4ubuntu3) 13.2.0, GNU ld (GNU Binutils for Ubuntu) 2.41) #13-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 18 09:08:04 UTC 2024 (Ubuntu 6.5.0-1010.13-raspi 6.5.8) ... [2.612956] brcm-pcie 100011.pcie: link down [2.617719] pci_bus :01: busn_res: [bus 01-ff] end is updated to 01 [2.624391] pci :00:00.0: PCI bridge to [bus 01] ... [2.876967] brcm-pcie 100012.pcie: link up, 5.0 GT/s PCIe x4 (!SSC) [2.883637] pci :01:00.0: [1de4:0001] type 00 class 0x02 ... After digging a bit, I found a discussion on the Raspberry's kernel github [2]: - a bug was introduced sometime in 6.2.x [3] - a fix landed in 6.6.x [4] - it boils down to a misused `readw_` instead of `readl_` in the pcie-brcmstb driver This made me think that given that the upcoming 24.04 is going to be on 6.7 or 6.8 kernel, the fix might be already there. So I grabbed a build of the "6.7.0-1001.1"[5] kernel from the "Noble Proposed" and installed it on the Mantic on my sd-card. After reboot, the nvme drive was discovered and proper driver was loaded: > uname -a Linux pi 6.7.0-1001-raspi #1-Ubuntu SMP PREEMPT_DYNAMIC Thu Jan 25 12:28:01 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux > lspci -nnk :00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in use: pcieport :01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961/SM963 [144d:a804] Subsystem: Samsung Electronics Co Ltd SM963 2.5" NVMe PCIe SSD [144d:a801] Kernel driver in use: nvme Kernel modules: nvme 0001:00:00.0 PCI bridge [0604]: Broadcom Inc. and subsidiaries Device [14e4:2712] (rev 21) Kernel driver in u
[Kernel-packages] [Bug 2060300] [NEW] KMS overlay causes OOM oops on 3A+
Public bug reported: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out-of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). ** Affects: linux-raspi (Ubuntu) Importance: Low Status: New ** Attachment added: "screenlog.0" https://bugs.launchpad.net/bugs/2060300/+attachment/5761694/+files/screenlog.0 ** Changed in: linux-raspi (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060300 Title: KMS overlay causes OOM oops on 3A+ Status in linux-raspi package in Ubuntu: New Bug description: Came across something bizarre when investigating the audio situation with server on the Pi 5 (LP: #2038924). Moving the server images to use the KMS overlay solves the situation, and would be preferable as it would eliminate another difference between server and desktop images. However, it also renders the 512MB 3A+ unbootable with an out- of-memory error. The reason this is strange is that the 512MB Zero 2W continues to boot quite happily. I'm attaching the serial output from the kernel up to the point of the crash (screenlog.0). The only changes made to the stock server config.txt were the addition of these lines under the final "[all]" section: [all] dtoverlay=vc4-kms-v3d disable_fw_kms_setup=1 This setup booted happily on all other boards. A trivial workaround is to manually specify a smaller CMA on the 3A+ with: dtoverlay=vc4-kms-v3d,cma-128 With this alteration, it boots happily (and I'll be using this in an appropriate [section] to work around the issue), but it might be nice to understand why this is required on this board specifically (and why the 512MB Zero 2W doesn't exhibit the same issue). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060240] [NEW] Pi DAC+ fails on Pi 5
Public bug reported: First reported on the Raspberry Pi forums (https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT, which is basically the same board) works happily under RaspiOS on the Pi 5, but not Ubuntu 23.10 or 24.04. The board *does* work on Ubuntu on prior models, including 3B+ and 4B (those are all I've tested so far), but it does require the overlay (iqaudio-dacplus or rpi-dacplus depending on the variant) to be manually specified in config.txt (RaspiOS automatically detects and loads the board; I haven't figured out why we don't yet but that's an additional data-point that may be worth exploring). Anyway, on the Pi 5 the HAT is detected (/proc/device-tree/hat/uuid is populated with the correct value, and /proc/device-tree/hat/product lists "Pi-DAC+" which is correct), but the following appears in dmesg: [7.383734] designware-i2s 1f000a.i2s: Missing dma channel for stream: 0 [7.392977] designware-i2s 1f000a.i2s: ASoC: error at snd_soc_pcm_component_new on 1f000a.i2s: -22 [7.403212] snd-rpi-iqaudio-dac soc:sound: ASoC: can't create pcm Raspberry Pi DAC+ HiFi :-22 [7.405612] rpivid 100080.codec: bcm2712_iommu_of_xlate: MMU 105100.iommu [7.416183] rpivid 100080.codec: bcm2712_iommu_probe_device: MMU 105100.iommu [7.418036] snd-rpi-iqaudio-dac soc:sound: snd_soc_register_card() failed: -22 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2060240 Title: Pi DAC+ fails on Pi 5 Status in linux-raspi package in Ubuntu: New Bug description: First reported on the Raspberry Pi forums (https://forums.raspberrypi.com/viewtopic.php?p=2162847), I've since confirmed that the Raspberry Pi DAC+ HAT (formerly the IQaudIO DAC+ HAT, which is basically the same board) works happily under RaspiOS on the Pi 5, but not Ubuntu 23.10 or 24.04. The board *does* work on Ubuntu on prior models, including 3B+ and 4B (those are all I've tested so far), but it does require the overlay (iqaudio-dacplus or rpi-dacplus depending on the variant) to be manually specified in config.txt (RaspiOS automatically detects and loads the board; I haven't figured out why we don't yet but that's an additional data-point that may be worth exploring). Anyway, on the Pi 5 the HAT is detected (/proc/device-tree/hat/uuid is populated with the correct value, and /proc/device-tree/hat/product lists "Pi-DAC+" which is correct), but the following appears in dmesg: [7.383734] designware-i2s 1f000a.i2s: Missing dma channel for stream: 0 [7.392977] designware-i2s 1f000a.i2s: ASoC: error at snd_soc_pcm_component_new on 1f000a.i2s: -22 [7.403212] snd-rpi-iqaudio-dac soc:sound: ASoC: can't create pcm Raspberry Pi DAC+ HiFi :-22 [7.405612] rpivid 100080.codec: bcm2712_iommu_of_xlate: MMU 105100.iommu [7.416183] rpivid 100080.codec: bcm2712_iommu_probe_device: MMU 105100.iommu [7.418036] snd-rpi-iqaudio-dac soc:sound: snd_soc_register_card() failed: -22 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2060240/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2048864] Re: Remove armhf support
Indeed -- the Pi isn't compatible with our generic arm64 kernel, so we'll be sticking with the flavour limit for the time being, and this does actually reduce our delta with Debian. I've got a couple of other patches to incorporate into f-k this week, so I'm going to sponsor this as part of a larger upload but that should be fine for the devel series. ** Changed in: flash-kernel (Ubuntu Noble) Status: Won't Fix => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2048864 Title: Remove armhf support Status in flash-kernel package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in flash-kernel source package in Noble: New Status in linux-raspi source package in Noble: New Bug description: Noble and newer don't support armhf for Pi anymore. We can drop the armhf specific kernel flavor raspi-nolpae from flash-kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/2048864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033348] Re: Wireless: Update RTL8852BE wifi driver
Any updates here? -- 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/2033348 Title: Wireless: Update RTL8852BE wifi driver Status in linux package in Ubuntu: Confirmed Bug description: Firmware 0.27 was added in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there has been an update submitted by Realtek which resolves crash issues of the driver related to DMA. New firmware file is up in kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1 Ideally updated for both Lunar and Jammy :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1959113] Re: missing built-in disk encryption at install time
rpi-imager currently has no facility to encrypt the image it flashes to the storage on the Pi (and making such a facility generic enough that it would fit all potentially interested distros is a daunting task to say the least), so this isn't valid for rpi-imager. I *did* add some initial steps towards this in the lunar desktop images, which preserve space at the end of the root partition for LUKS headers (by ensuring the root file-system doesn't expand *all* the way to the partition size) which should make this easier to achieve in future, but there's still plenty of work to be done here. ** Changed in: rpi-imager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1959113 Title: missing built-in disk encryption at install time Status in Ubuntu: New Status in linux-firmware-raspi package in Ubuntu: New Status in linux-raspi package in Ubuntu: New Status in rpi-imager package in Ubuntu: Invalid Bug description: Is there a simple way to install Ubuntu on SD card for Raspberry Pi4 with full disk encryption? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1959113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874354] Re: limited wireles channels on a RPi 3B
Ah, I remember this old one. We discussed this with upstream and found the issue was that for that specific firmware, the clm-blob was included in the firmware blob itself, but the code that loaded firmware blobs still warned that it couldn't find the external file. That code was eventually cleaned up so it no longer complains, so this is essentially fix released. ** Changed in: linux-meta-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1874354 Title: limited wireles channels on a RPi 3B Status in linux-meta-raspi package in Ubuntu: Fix Released Bug description: I saw the following in my dmesg: [ 13.113608] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2 [ 13.113640] cfg80211: failed to load regulatory.db [ 13.259143] brcmfmac: F1 signature read @0x1800=0x1541a9a6 [ 13.268452] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 13.279732] usbcore: registered new interface driver brcmfmac [ 13.520854] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43430-sdio for chip BCM43430/1 [ 13.532110] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available [ 13.552859] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM43430/1 wl0: Oct 23 2017 03:55:53 version 7.45.98.38 (r674442 CY) FWID 01-e58d219f I don't know if the channels are really limited. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-raspi 5.4.0.1008.8 ProcVersionSignature: User Name 5.4.0-1008.8-raspi 5.4.29 Uname: Linux 5.4.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu27 Architecture: arm64 CasperMD5CheckResult: skip Date: Thu Apr 23 00:29:47 2020 SourcePackage: linux-meta-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi/+bug/1874354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862760] Re: Unreliable 802.11ac connection on our raspi images
At this point, we've had all the necessary firmware blobs for numerous releases and I'm reasonably convinced that the remaining AC wifi issues are largely related to incorrect regulatory domain, because we don't provide a friendly way of setting this on desktop (see LP: #1951586 for more on this). I'm going to mark bionic as won't fix as it's EOL (sans ESM) anyway, focal as fix released as we did add all the relevant blobs (at the time) as a back-port to that, and the devel versions as fix released. If anyone is still have 802.11ac connectivity issues, I strongly recommend checking the wifi regulatory domain with "iw reg get". If it doesn't match your expected country, please see: * For server, see the "regulatory-domain" setting under "wifis:" in netplan -- https://netplan.readthedocs.io/en/stable/netplan- yaml/#properties-for-device-type-wifis * For desktop, add "cfg80211.ieee80211_regdom=CC" where CC is your country code to "/boot/firmware/cmdline.txt" and reboot. Urgh. ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-firmware (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-firmware-raspi2 (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: linux-firmware-raspi2 (Ubuntu Focal) Status: Triaged => Fix Released ** Changed in: linux-raspi (Ubuntu) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Focal) Status: New => Invalid ** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid ** Changed in: netplan.io (Ubuntu) Status: New => Invalid ** Changed in: netplan.io (Ubuntu Bionic) Status: New => Invalid ** Changed in: netplan.io (Ubuntu Focal) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1862760 Title: Unreliable 802.11ac connection on our raspi images Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware-raspi2 package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Invalid Status in netplan.io package in Ubuntu: Invalid Status in linux-firmware source package in Bionic: Invalid Status in linux-firmware-raspi2 source package in Bionic: Won't Fix Status in linux-raspi2-5.3 source package in Bionic: Won't Fix Status in netplan.io source package in Bionic: Invalid Status in linux-firmware source package in Eoan: Won't Fix Status in linux-firmware-raspi2 source package in Eoan: Won't Fix Status in linux-raspi2-5.3 source package in Eoan: Won't Fix Status in netplan.io source package in Eoan: Won't Fix Status in linux-firmware source package in Focal: Invalid Status in linux-firmware-raspi2 source package in Focal: Fix Released Status in linux-raspi source package in Focal: Invalid Status in netplan.io source package in Focal: Invalid Bug description: We were not able to completely pin-point the issue yet, so this is more of a blanket bug for the current issues we are seeing. We don't know where exactly the issue can be located. While preparing and testing 18.04.4, certification reported issues with our uc18 images on the pi4 with wifi ac tests. One of our engineers (Brian) confirmed it locally with a wifi access point restricted only to 802.11ac. After some additional testing, he noticed that he had the same unreliable symptoms for both the classic and core images, as well as the 19.10.1 classic images. The symptoms seem to vary, from inability to detect 802.11ac APs, inability to connect and/or receive an IP address and no traffic getting through. We will provide all the information that we have. Raspbian works better in this regard. We have pulled in the wifi firmware bits from Raspbian and using those, and that seems to resolve all flakiness. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1862760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2041741] Re: Fan speed Control not working on RASPERRY PI RUNNING UBUNTU 23.10
** Changed in: linux-raspi (Ubuntu) Importance: Undecided => High ** Also affects: linux-raspi (Ubuntu Mantic) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux-raspi (Ubuntu Mantic) Importance: Undecided => High ** Summary changed: - Fan speed Control not working on RASPERRY PI RUNNING UBUNTU 23.10 + Fan speed control not working on Pi 5 under Ubuntu 23.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2041741 Title: Fan speed control not working on Pi 5 under Ubuntu 23.10 Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Mantic: Confirmed Bug description: The fan speed control when running Ubuntu 23.10 on a Raspberry Pi 5 does not appear to be working. The fan runs at near maximum speed all the time and the cur_state in /sys/class/thermal/cooling_device0/ is stuck at the value of 4 no matter what the CPU temperature. I suspect it is related to this fault reported on Raspberry Pi OS: https://forums.raspberrypi.com/viewtopic.php?t=356881 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2041741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
** Changed in: ubuntu-release-notes Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in Release Notes for Ubuntu: Fix Released Status in libcamera package in Ubuntu: Triaged Status in linux-meta-raspi package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Invalid Status in rpi-eeprom package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037059] Re: array index out of bounds in brcmfmac driver
** Changed in: linux-raspi (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037059 Title: array index out of bounds in brcmfmac driver Status in linux-raspi package in Ubuntu: Fix Released Bug description: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2037059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038924] [NEW] No alsa sound cards on Pi 5
Public bug reported: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2038924 Title: No alsa sound cards on Pi 5 Status in linux-raspi package in Ubuntu: New Bug description: During ISO testing of the final mantic images on the Pi 5, no ALSA cards are listed under /proc/asound/cards and (predictably) none of the ALSA utilities are able to output audio. Is this a DT related issue again? (reminiscent of LP: #1991254) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2038924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038589] Re: Backport DMABUF support from Upstream to Ubuntu Jammy
The following changes since commit 294374341c622e5c2ffd15712cadabe0dd9865f1: UBUNTU: Ubuntu-5.15.0-83.92 (2023-08-14 11:05:34 +0200) are available in the Git repository at: https://github.com/tdavenvidia/ubuntu_kernel_jammy/pull/3 for you to fetch changes up to 11ef7073533e332ce5ec96ef9aa3f693e7184b49: RDMA/mlx5: Enable ATS support for MRs and umems (2023-10-05 15:55:57 -0700) Gal Pressman (3): dma-buf: Fix pin callback comment RDMA/umem: Allow pinned dmabuf umem usage RDMA/efa: Add support for dmabuf memory regions Jason Gunthorpe (3): RDMA/core: Add UVERBS_ATTR_RAW_FD RDMA/mlx5: Add support for dmabuf to devx umem RDMA/mlx5: Enable ATS support for MRs and umems drivers/infiniband/core/umem_dmabuf.c| 51 drivers/infiniband/core/uverbs_ioctl.c | 8 +++ drivers/infiniband/hw/efa/efa.h | 4 drivers/infiniband/hw/efa/efa_main.c | 1 + drivers/infiniband/hw/efa/efa_verbs.c| 127 +++--- drivers/infiniband/hw/mlx5/devx.c| 54 +-- drivers/infiniband/hw/mlx5/mlx5_ib.h | 36 +++ drivers/infiniband/hw/mlx5/mr.c | 5 - include/linux/dma-buf.h | 4 ++-- include/rdma/ib_umem.h | 11 ++ include/rdma/uverbs_ioctl.h | 13 include/uapi/rdma/mlx5_user_ioctl_cmds.h | 1 + 12 files changed, 265 insertions(+), 50 deletions(-) -- 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/2038589 Title: Backport DMABUF support from Upstream to Ubuntu Jammy Status in linux package in Ubuntu: Incomplete Bug description: DAMBUF is backported using the two series of patches: First, we need the series of 3 patches at: https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ - dma-buf: Fix pin callback comment - RDMA/umem: Allow pinned dmabuf umem usage - RDMA/efa: Add support for dmabuf memory regions Second, we need series of 4 patches at: https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ Note: The changes made by first patch in series "net/mlx5: Add IFC bits for mkey ATS" had already been there in Ubuntu jammy "master- next" - (Already there in jammy ) net/mlx5: Add IFC bits for mkey ATS - RDMA/core: Add UVERBS_ATTR_RAW_FD - RDMA/mlx5: Add support for dmabuf to devx umem - RDMA/mlx5: Enable ATS support for MRs and umems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038589] [NEW] Backport DMABUF support from Upstream to Ubuntu Jammy
Public bug reported: DAMBUF is backported using the two series of patches: First, we need the series of 3 patches at: https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ - dma-buf: Fix pin callback comment - RDMA/umem: Allow pinned dmabuf umem usage - RDMA/efa: Add support for dmabuf memory regions Second, we need series of 4 patches at: https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ Note: The changes made by first patch in series "net/mlx5: Add IFC bits for mkey ATS" had already been there in Ubuntu jammy "master-next" - (Already there in jammy ) net/mlx5: Add IFC bits for mkey ATS - RDMA/core: Add UVERBS_ATTR_RAW_FD - RDMA/mlx5: Add support for dmabuf to devx umem - RDMA/mlx5: Enable ATS support for MRs and umems ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2038589 Title: Backport DMABUF support from Upstream to Ubuntu Jammy Status in linux package in Ubuntu: New Bug description: DAMBUF is backported using the two series of patches: First, we need the series of 3 patches at: https://lore.kernel.org/all/20211012120903.96933-1-galpr...@amazon.com/ - dma-buf: Fix pin callback comment - RDMA/umem: Allow pinned dmabuf umem usage - RDMA/efa: Add support for dmabuf memory regions Second, we need series of 4 patches at: https://lore.kernel.org/all/0-v1-bd147097458e+ede-umem_dmabuf_...@nvidia.com/ Note: The changes made by first patch in series "net/mlx5: Add IFC bits for mkey ATS" had already been there in Ubuntu jammy "master- next" - (Already there in jammy ) net/mlx5: Add IFC bits for mkey ATS - RDMA/core: Add UVERBS_ATTR_RAW_FD - RDMA/mlx5: Add support for dmabuf to devx umem - RDMA/mlx5: Enable ATS support for MRs and umems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038589/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] Re: [FFe] Raspberry Pi 5 support
The rpiboot package can be skipped for now; according to upstream the updated package won't be ready at release. The separate bug LP: #2032178 will track updates if/when I can get the uploaded. ** No longer affects: rpiboot (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037059] [NEW] array index out of bounds in brcmfmac driver
Public bug reported: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037059 Title: array index out of bounds in brcmfmac driver Status in linux-raspi package in Ubuntu: New Bug description: Activating wifi on the current Mantic Beta images, on a Raspberry Pi 4B with 4GB or 8GB of RAM (the only two I've tested thus far) causes the following to show up in dmesg: [ 10.384021] [ 10.393418] UBSAN: array-index-out-of-bounds in /build/linux-raspi-dZDMS4/linux-raspi-6.5.0/drivers/net/wireless/broadcom/brcm80211/brcmfmac/cfg80211.c:1126:27 [ 10.408653] index 1 is out of range for type '__le16 [1]' [ 10.414856] CPU: 2 PID: 581 Comm: wpa_supplicant Tainted: G C E 6.5.0-1002-raspi #2-Ubuntu [ 10.414876] Hardware name: Raspberry Pi 4 Model B Rev 1.4 (DT) [ 10.414881] Call trace: [ 10.414884] dump_backtrace+0x9c/0x128 [ 10.414897] show_stack+0x20/0x38 [ 10.414903] dump_stack_lvl+0xbc/0x120 [ 10.414911] dump_stack+0x18/0x28 [ 10.414916] __ubsan_handle_out_of_bounds+0xac/0xe8 [ 10.414922] brcmf_escan_prep+0x31c/0x338 [brcmfmac] [ 10.415003] brcmf_run_escan+0xac/0x1c8 [brcmfmac] [ 10.415050] brcmf_do_escan+0x90/0x100 [brcmfmac] [ 10.415096] brcmf_cfg80211_scan+0x108/0x2b0 [brcmfmac] [ 10.415142] rdev_scan+0x38/0x158 [cfg80211] [ 10.415348] cfg80211_scan+0x134/0x178 [cfg80211] [ 10.415453] nl80211_trigger_scan+0x438/0x9d8 [cfg80211] [ 10.415557] genl_family_rcv_msg_doit.isra.0+0xc0/0x130 [ 10.415568] genl_family_rcv_msg+0x1c8/0x240 [ 10.415574] genl_rcv_msg+0x64/0xe8 [ 10.415580] netlink_rcv_skb+0x64/0x138 [ 10.415586] genl_rcv+0x40/0x60 [ 10.415592] netlink_unicast+0x2f0/0x350 [ 10.415598] netlink_sendmsg+0x26c/0x490 [ 10.415603] sock_sendmsg+0x64/0xc0 [ 10.415610] sys_sendmsg+0x260/0x318 [ 10.415615] ___sys_sendmsg+0x88/0xf0 [ 10.415621] __sys_sendmsg+0x70/0xd8 [ 10.415626] __arm64_sys_sendmsg+0x2c/0x40 [ 10.415632] invoke_syscall+0x50/0x120 [ 10.415638] el0_svc_common.constprop.0+0x6c/0x140 [ 10.415642] do_el0_svc+0x34/0x50 [ 10.415646] el0_svc+0x30/0xc8 [ 10.415654] el0t_64_sync_handler+0x120/0x130 [ 10.415659] el0t_64_sync+0x1a8/0x1b0 [ 10.415668] However, the wifi still works afterward, so it's not entirely fatal! To manage notifications about this bug g
[Kernel-packages] [Bug 2036630] [NEW] Disks Crashed; package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installatio
Public bug reported: I formatted a new Flash Drive and the process hung. So I unplugged the drive. Disks App crashed when I did. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 18 17:01:28 2023 Df: ErrorMessage: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2023-09-16 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036630 Title: Disks Crashed; package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux- image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 Status in linux-signed-hwe-6.2 package in Ubuntu: New Bug description: I formatted a new Flash Drive and the process hung. So I unplugged the drive. Disks App crashed when I did. ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 18 17:01:28 2023 Df: ErrorMessage: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 InstallationDate: Installed on 2023-09-16 (3 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-signed-hwe-6.2 Title: package linux-image-6.2.0-33-generic 6.2.0-33.33~22.04.1 failed to install/upgrade: installed linux-image-6.2.0-33-generic package post-installation script subprocess returned error exit status 143 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036630/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2035373] [NEW] Move nbd module into modules (from -extra)
Public bug reported: Would it be possible to move the "nbd" kernel module from linux-modules- extra-raspi into linux-modules-extra? This would enable NBD-based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2035373 Title: Move nbd module into modules (from -extra) Status in linux-raspi package in Ubuntu: New Bug description: Would it be possible to move the "nbd" kernel module from linux- modules-extra-raspi into linux-modules-extra? This would enable NBD- based network boot (which has certain advantages over the NFS-based network boot more traditional in the Pi world, such as permitting services that refuse to run on NFS -- like snapd). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2035373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033348] Re: Wireless: Update RTL8852BE wifi driver
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033348 Title: Wireless: Update RTL8852BE wifi driver Status in linux package in Ubuntu: Confirmed Bug description: Firmware 0.27 was added in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there has been an update submitted by Realtek which resolves crash issues of the driver related to DMA. New firmware file is up in kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1 Ideally updated for both Lunar and Jammy :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033348] Re: Wireless: Update RTL8852BE wifi driver
@kobako The full thread of the problem can be seen in https://lore.kernel.org/linux- wireless/20230421015357.13940-1-pks...@realtek.com/T/#u This bug report is mainly a preemptive request to get the latest stable driver on. A few error logs below. * Note: these were not gathered in an Ubuntu image, but rather a minimal 6.2 kernel linux one running firmware 0.27, thus cannot run "apport- collect" [Thu Feb 23 12:57:41 2023] rtw89_8852be :03:00.0: Firmware version 0.27.32.1, cmd version 0, type 1 [Thu Feb 23 12:57:41 2023] rtw89_8852be :03:00.0: Firmware version 0.27.32.1, cmd version 0, type 3 [Thu Feb 23 12:57:41 2023] rtw89_8852be :03:00.0: chip rfe_type is 1 ... [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW status = 0xb8001100 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW BADADDR = 0xee [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW EPC/RA = 0x0 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW MISC = 0xb8900635 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_HALT_C2H = 0x1000 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_SER_DBG_INFO = 0x100 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a0f3 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a023 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a01d [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a0dd [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a001 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a02b [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a0eb [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a00b [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a023 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a0df [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb8989fff [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a025 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a0fd [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a01f [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: [ERR]fw PC = 0xb898a037 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: ---> err=0x1000 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_SER_DBG_INFO =0x0100 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_DMAC_ERR_ISR=0x0040 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_DMAC_ERR_IMR=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WDE_ERR_FLAG_CFG=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PLE_ERR_FLAG_CFG=0x8319 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WDE_ERR_IMR=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WDE_ERR_ISR=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PLE_ERR_IMR=0xffdf [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PLE_ERR_FLAG_ISR=0x0200 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WD_CPUQ_OP_0=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WD_CPUQ_OP_1=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WD_CPUQ_OP_2=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_WD_CPUQ_OP_STATUS=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PL_CPUQ_OP_0=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PL_CPUQ_OP_1=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PL_CPUQ_OP_2=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_PL_CPUQ_OP_STATUS=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_RXDMA_PKT_INFO_0=0x80008075 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_RXDMA_PKT_INFO_1=0x80008000 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_RXDMA_PKT_INFO_2=0x800980b1 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_CMAC_ERR_ISR [0]=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_CMAC_FUNC_EN [0]=0xf000803f [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_CK_EN [0]=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_CMAC_ERR_IMR [0]=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_RPQ_RXBD_IDX =0x00de00de [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_DBG_ERR_FLAG=0x [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: R_AX_LBC_WATCHDOG=0x0081 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: <--- [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: SER catches error: 0x1000 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW status = 0xb8001100 [Thu Feb 23 13:22:18 2023] rtw89_8852be :03:00.0: FW BAD
[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver
Submitted request to update driver/firmware to latest v0.29 in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2002601 Title: Wireless: Enable RTL8852BE wifi driver Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Justification] Enable Realtek RLT8852BE WIFI. [Test] 1. put rtw8852b_fw.bin in /lib/firmware/rtw89/ 2. boot-up with kernel enabled RTL8852be. 3. Connect to WIFI-AP and test with ping. * ping -I wlp2s0 8.8.8.8 ~~~ PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms 64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms 64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms 64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms ~~~ * Connected to AP ~~~ u@ubuntu:~$ nmcli dev DEVICE TYPE STATE CONNECTION enp3s0 ethernet connected Wired connection 1 wlp2s0 wifi connected Canonical p2p-dev-wlp2s0 wifi-p2p disconnected -- lo loopback unmanaged -- ~~~ * lsmod | grep 8852 ~~~ lsmod | grep 8852 rtw89_8852be 16384 0 rtw89_8852b 368640 1 rtw89_8852be rtw89_pci 61440 1 rtw89_8852be rtw89_core 442368 2 rtw89_8852b,rtw89_pci cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211 ~~~ 4. cbd's built result, Lunar, ~~~ remote: Resolving deltas: 100% (391/391), completed with 118 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt remote: * For results: ssh cbd ls kobako-lunar-0e58018b43c1-ioeM remote: * 96/480 cores busy (1/5 hosts), 0 builds queued remote: 2023-01-12 03:16:35 kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK remote: 2023-01-12 03:17:47 kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK remote: 2023-01-12 03:11:36 kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK remote: 2023-01-12 03:16:30 kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK remote: 2023-01-12 03:10:24 kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK remote: To cbd:lunar.git ~~~ OEM-6.1, remote: Resolving deltas: 100% (399/399), completed with 121 local objects. remote: *** kernel-cbd * remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt remote: * For results: ssh cbd ls kobako-jammy-c1002f30ccc3-m65z remote: * 0/192 cores busy (0/2 hosts), 0 builds queued remote: 2023-01-12 05:25:23 kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK remote: To cbd:jammy.git [Where problems could occur] Medium, a new driver so the current driver may have some edge cases didn't consider. [Misc] * For generic Jammy, need more patches to enable RTL8852be so only SRU for OEM-6.1. * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on Lunar, so only SRU for Jammy. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033348] [NEW] Wireless: Update RTL8852BE wifi driver
Public bug reported: Firmware 0.27 was added in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there has been an update submitted by Realtek which resolves crash issues of the driver related to DMA. New firmware file is up in kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1 Ideally updated for both Lunar and Jammy :-) ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2033348 Title: Wireless: Update RTL8852BE wifi driver Status in linux package in Ubuntu: New Bug description: Firmware 0.27 was added in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2002601 but there has been an update submitted by Realtek which resolves crash issues of the driver related to DMA. New firmware file is up in kernel: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/log/rtw89/rtw8852b_fw-1.bin?showmsg=1 Ideally updated for both Lunar and Jammy :-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader
** Tags removed: rls-ll-incoming ** Tags added: foundations-todo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2027847 Title: Bump minimum /boot size in ubuntu-release-upgrader Status in apt package in Ubuntu: Won't Fix Status in dpkg package in Ubuntu: Invalid Status in kernel-package package in Ubuntu: Invalid Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Invalid Status in linux-kernel-headers package in Ubuntu: Invalid Status in linux-restricted-modules package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: New Bug description: System information: ubuntu 23.04 x86_64 6.2.0-24-generic Upgrading the system: $ sudo dpkg --configure -a Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ... update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic I: The initramfs will attempt to resume from /dev/dm-2 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. zstd: error 70 : Write error : cannot write block : No space left on device E: mkinitramfs failure zstd -q -1 -T0 70 Check space left (none): $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sdb2 707M 693M 0 100% /boot What is required is to remove older kernels (and purge them most likely). List all the installed kernels except the current one: $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-libc-dev:amd64 linux-libc-dev:i386 linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Is not possible to uninstall any kernel because fails: $ sudo apt purge linux-headers-6.2.0-23 E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem. Reconfigure fails again so some kernel have to be manually removed to free up space: $ sudo rm /boot/initrd.img-6.2.0-23-generic $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new Now you can reconfigure: $ Remove kernels: $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic linux-modules-extra-6.2.0-25-generic Reboot: $ sudo reboot Upgrade as usual: $ sudo apt update && sudo apt upgrade Before upgrading new kernels I need to check for free space and remove older kernels manually. Fix this so there's only one kernel left. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
Thanks. I see the same behavior (i.e. no warning) with the patch. I will add the patch 'commit f5451547b8310868f5b5acff7cd4aa7c0267edb3' to linux-nvidia-6.2 then.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
Can you try the below commit from linus's "linux" tree and see if the warning goes away? commit f5451547b8310868f5b5acff7cd4aa7c0267edb3 Author: Thomas Gleixner Date: Tue Feb 7 15:16:53 2023 +0100 mm, slab/slub: Ensure kmem_cache_alloc_bulk() is available early -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
yeah I suspect that.. there are couple of irq patches in the 6.2.0-1004-nvidia could be the cause.. I will update here shortly! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2026891] Re: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540"
** Changed in: linux-nvidia-6.2 (Ubuntu) Assignee: (unassigned) => Tushar Dave (tdavenvidia) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2026891 Title: linux-nvidia-6.2 on DGX servers: "WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540" Status in linux-nvidia-6.2 package in Ubuntu: New Bug description: We started testing the jammy/linux-nvidia-6.2 kernels on the nvidia servers (DGX-1/DGX-2/H100) and hit the following warning during boot: [7.690486] [ cut here ] [7.690487] Interrupts were enabled early [7.690490] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x4da/0x540 [7.690498] Modules linked in: [7.690501] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [7.690504] Hardware name: NVIDIA NVIDIA DGX-2/NVIDIA DGX-2, BIOS 0.29 06/07/2021 [7.690505] RIP: 0010:start_kernel+0x4da/0x540 [7.690508] Code: ff 48 c7 c7 e8 26 f0 97 e8 b3 59 a8 fd 0f 0b e9 96 fd ff ff e8 a7 1d 04 00 e9 7c fe ff ff 48 c7 c7 18 27 f0 97 e8 96 59 a8 fd <0f> 0b e9 ed fd ff ff 48 c7 c7 b0 26 f0 97 e8 83 59 a8 fd 0f 0b ff [7.690510] RSP: :98803f08 EFLAGS: 00010246 [7.690512] RAX: RBX: RCX: [7.690513] RDX: RSI: RDI: [7.690514] RBP: 98803f20 R08: R09: [7.690515] R10: R11: R12: 00e0 [7.690516] R13: 5a1ccde0 R14: 5a1c7469 R15: 5a1d7ee0 [7.690518] FS: () GS:96490060() knlGS: [7.690520] CS: 0010 DS: ES: CR0: 80050033 [7.690521] CR2: 970bf000 CR3: 00ecd7810001 CR4: 000606f0 [7.690522] DR0: DR1: DR2: [7.690523] DR3: DR6: fffe0ff0 DR7: 0400 [7.690524] Call Trace: [7.690526] [7.690529] x86_64_start_kernel+0x102/0x180 [7.690536] secondary_startup_64_no_verify+0xe5/0xeb [7.690544] [7.690544] ---[ end trace ]--- I also see pretty much the same thing on some Ampere based arm64 servers: [0.000519] [ cut here ] [0.000521] Interrupts were enabled early [0.000525] WARNING: CPU: 0 PID: 0 at init/main.c:1065 start_kernel+0x3ac/0x514 [0.000531] Modules linked in: [0.000535] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 6.2.0-1004-nvidia #4~22.04.1-Ubuntu [0.000538] pstate: 6049 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--) [0.000540] pc : start_kernel+0x3ac/0x514 [0.000543] lr : start_kernel+0x3ac/0x514 [0.000545] sp : dec5ff733e60 [0.000546] x29: dec5ff733e60 x28: 0819aa09baac x27: 403ffdd124e0 [0.000549] x26: bfdf3788 x25: 9b6fc000 x24: 001dba7b [0.000552] x23: 5ec57c98 x22: 0819ab2a x21: dec5ff749140 [0.000555] x20: dec5ff73d9c0 x19: dec5ffbe4000 x18: dec5ff74a1c8 [0.000558] x17: x16: x15: [0.000560] x14: x13: 0a796c7261652064 x12: 656c62616e652065 [0.000563] x11: 656820747563205b x10: 2d2d2d2d2d2d2d2d x9 : [0.000565] x8 : x7 : x6 : [0.000568] x5 : x4 : x3 : [0.000571] x2 : x1 : x0 : [0.000573] Call trace: [0.000574] start_kernel+0x3ac/0x514 [0.000577] __primary_switched+0xc0/0xc8 [0.000580] ---[ end trace ]--- The warning does not appear on an older thunderx2 server. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-6.2/+bug/2026891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017449] Re: Unsafe to upgrade ZFS Boot Ubuntu from Kinetic to Lunar
As stated above, Ubuntu on ZFS failed to boot after an earlier version upgrade. The Jonathon F PPA (https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) resolved this problem. If Ubuntu patches zfs to be compatible, why does this PPA exist? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/2017449 Title: Unsafe to upgrade ZFS Boot Ubuntu from Kinetic to Lunar Status in zfs-linux package in Ubuntu: Opinion Bug description: Need to know if it is safe to upgrade from Ubuntu 22.10/Kinetic to 23.04/Lunar on systems that have been installed onto the ZFS filesystem via the Ubuntu 22.10 GUI installer and selecting the ZFS filesystem option. The reason I ask is I was burned by this in the last upgrade cycle. Upgrading 21.10 to 22.03 resulted in an unbootable system with no warning, no easy recourse, very few recovery options because Ubuntu 22.03 did not ship with proper ZFS kernel support. It was very bad and I lost a week of income from the downtime. It looks like the same situation exists here. Ubuntu 23.04/Lunar ships with Kernel 6.2 but ZFS didn't release Kernel 6.2 support until very recently and from what I can tell (??) the updated ZFS packages did not make it into the Lunar installer. The last time I resolved the issue by using Jonathon F's ZFS support PPA (here https://launchpad.net/~jonathonf/+archive/ubuntu/zfs) but it looks like he no longer supports it. I've tried to contact him several times over the last week but get no response. Will the upgraded system be bootable? What is the recommended path to get onto Lunar? I have been waiting for 23.04 to resolve various issues with my MSI Z690 motherboard, etc. If this is actually an issue I recommend urgently resolving it so that others who selected ZFS are not stranded at an emergency prompt with no guidance on how to handle the problem. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: evince 43.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.23.1-0ubuntu3.2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Sun Apr 23 13:01:55 2023 InstallationDate: Installed on 2022-05-03 (354 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to kinetic on 2022-12-02 (142 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/2017449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019320] [NEW] i2c devices missing in lunar
Public bug reported: In the lunar release of linux-raspi, despite the boot configuration enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0 and /dev/i2c-1 devices are missing (they are present in jammy and kinetic). These are the I2C interfaces present on the GPIO header (and thus rather important on the raspi as without these interfaces being present, I2C devices connected to the header cannot be used). I'm guessing this is a kernel change, but it *might* be something in the udev configuration; I haven't dug that far yet. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2019320 Title: i2c devices missing in lunar Status in linux-raspi package in Ubuntu: New Bug description: In the lunar release of linux-raspi, despite the boot configuration enabling the i2c_arm parameter of the base overlay, the usual /dev/i2c-0 and /dev/i2c-1 devices are missing (they are present in jammy and kinetic). These are the I2C interfaces present on the GPIO header (and thus rather important on the raspi as without these interfaces being present, I2C devices connected to the header cannot be used). I'm guessing this is a kernel change, but it *might* be something in the udev configuration; I haven't dug that far yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2019320/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error
Was able to purge the non-working 6.2 kernels with -- sudo dpkg --purge and then list the 6.2 kernels listed after finding all the 6.2 linux kernels with sudo dpkg -l | grep "Linux kernel" Have not yet tried installing anything beyond 5.19 yet. -- 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/2017267 Title: Release upgrade to lunar lobster linux-headers-6.2.0-20 post- installation error Status in linux package in Ubuntu: Confirmed Bug description: Ended with a dialog box: Could not install 'linux-headers-6.2.0-20-generic' The upgrade will continue but the 'linux-headers-6.2.0-20-generic' package may not be in a working state. Please consider submitting a bug report about it. installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash 644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 08:09:44 2023 InstallationDate: Installed on 2021-01-04 (836 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-kitty XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2017267] Re: Release upgrade to lunar lobster linux-headers-6.2.0-20 post-installation error
Same issue here though I don't have any displaylink drivers installed. Seemed that my upgrade install was interrupted perhaps and no amount of installing a new kernel either by download and with dpkg -i or using Ubuntu's mainline yield any success. 6.2 Kernel still shows up when I reboot and is the default, but that reboot always ends in a kernel panic and needs to be manually rebooted and then I have to choose 5.19 Kernel. -- 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/2017267 Title: Release upgrade to lunar lobster linux-headers-6.2.0-20 post- installation error Status in linux package in Ubuntu: Confirmed Bug description: Ended with a dialog box: Could not install 'linux-headers-6.2.0-20-generic' The upgrade will continue but the 'linux-headers-6.2.0-20-generic' package may not be in a working state. Please consider submitting a bug report about it. installed linux-headers-6.2.0-20-generic package post-installation script subprocess returned error exit status 1 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: ubuntu-release-upgrader-core 1:23.04.6 ProcVersionSignature: Ubuntu 5.19.0-40.41-generic 5.19.17 Uname: Linux 5.19.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CrashDB: ubuntu CrashReports: 600:0:125:674842:2023-04-21 08:04:24.525593724 -0500:2023-04-21 08:04:24.613596272 -0500:/var/crash/linux-headers-6.2.0-20-generic.0.crash 644:0:125:1078246:2023-04-21 08:04:24.461591872 -0500:2023-04-21 08:04:24.869603682 -0500:/var/crash/nvidia-dkms-520.0.crash CurrentDesktop: ubuntu:GNOME Date: Fri Apr 21 08:09:44 2023 InstallationDate: Installed on 2021-01-04 (836 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) PackageArchitecture: all ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/usr/bin/zsh TERM=xterm-kitty XDG_RUNTIME_DIR= RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to lunar on 2023-04-21 (0 days ago) VarLogDistupgradeTermlog: modified.conffile..etc.apport.report-ignore.README.denylist: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2017267/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970603] Re: DSI touchscreen not working with KMS under 5.15
Under lunar's 6.2 kernel the situation is the same as kinetic's 5.19
kernel: display output works, but rotation is ignored and touchscreen
input doesn't work.
** Also affects: linux-raspi (Ubuntu Lunar)
Importance: Undecided
Status: Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1970603
Title:
DSI touchscreen not working with KMS under 5.15
Status in linux-raspi package in Ubuntu:
Confirmed
Status in linux-raspi source package in Jammy:
New
Status in linux-raspi source package in Kinetic:
New
Status in linux-raspi source package in Lunar:
Confirmed
Bug description:
The official Raspberry Pi touchscreen (the 7" model connected via the
DSI port) does not operate when the KMS overlay is applied (as is the
default on the Ubuntu Desktop for Raspberry Pi images). The display
does operate on RaspiOS Bullseye, also running kernel 5.15, when the
KMS overlay is used. Notably, the display does work on Ubuntu with no
KMS overlay (legacy framebuffer), or with the FKMS ("fake" KMS)
overlay.
The symptom is simply no output at all on the display. Sometimes there
is the initial "rainbow" screen of the start4.elf bootloader, but then
nothing. Notably this is *slightly* different to the Impish 5.13
kernel. On thata version, the DSI display also failed with the KMS
overlay, but in that case there was an initial flashing cursor
(presumably at the start of the initrd, perhaps on a leftover
framebuffer?) which then disappears before anything is printed. On
5.15 there's nothing after the "rainbow".
The symptoms are the same on both armhf and arm64 images.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-raspi 5.15.0.1005.5
ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
Uname: Linux 5.15.0-1005-raspi armv7l
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.15.0-1005-raspi.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu82
Architecture: armhf
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer']
failed with exit code 1:
CRDA: N/A
Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
CasperMD5CheckResult: unknown
Date: Wed Apr 27 10:04:10 2022
ImageMediaBuild: 20220419
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806
xHCI USB 3.0 Controller
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04d9:0006 Holtek Semiconductor, Inc. Wired Keyboard
(78/79 key) [RPI Wired Keyboard 5]
Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1
snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1
smsc95xx.macaddr=DC:A6:32:33:F5:57 vc_mem.mem_base=0x3ec0
vc_mem.mem_size=0x4000 console=ttyS0,115200 dwc_otg.lpm_enable=0
console=tty1 root=LABEL=writable rootfstype=ext4 rootwait
video=DSI-1:800x480@60,rotate=180 fixrtc quiet splash
RelatedPackageVersions:
linux-restricted-modules-5.15.0-1005-raspi N/A
linux-backports-modules-5.15.0-1005-raspi N/A
linux-firmware 20220329.git681281e4-0ubuntu1
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux-raspi
StagingDrivers: bcm2835_v4l2 bcm2835_isp vc_sm_cma bcm2835_codec
bcm2835_mmal_vchiq snd_bcm2835
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1970603/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
As a workaround until the fix lands (and is subsequently back-ported to the jammy HWE kernel), Koba's test-kernel in comment 36 works nicely. However, please note that the test kernel is not signed and will require that you disable secure boot to try it (if it's enabled on your machine), which may or may not fit your circumstances. If you require secure boot to be enabled I'm afraid you'll need to wait a bit longer. If you don't require secure boot, then: * disable secure boot * grab all files from the link in comment 36 to a clean directory * sudo dpkg -i *.deb (from that directory) * (you likely don't actually need *all* of the packages, but rather than sorting out which you do / don't need it's easier to simply install the lot) * sudo reboot -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: [Impact] For amdgpu/i915, hdmi audio output device has disappeared. [Fix] The latest fix for the non-contiguous memalloc helper changed the allocation method for a non-IOMMU system to use only the fallback allocator. This should have worked, but it caused a problem sometimes when too many non-contiguous pages are allocated that can't be treated by HD-audio controller. As a quirk workaround, go back to the original strategy: use dma_alloc_noncontiguous() at first, and apply the fallback only when it fails, but only for non-IOMMU case [Test Case] 1. boot with kernel applied the patches. 2. check the cards in /proc/asound/cards. Get the hdmi cards. 0 [PCH ]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xe232 irq 137 1 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xe226 irq 134 [Where problems could occur] Low, this is just workaround and may have a better solution in the future. [Misc] All patches has been landed on OEM-6.1 and lunar. ~~ CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Koba I can confirm the 5.19.9000-37-generic kernel from comment 36 fixes the issue for me as well, congratulations! I agree the 60Hz audio issue ought to be a separate report, but until that appears a quick side note to this one: my refresh rate is 60Hz and I have no issues with my audio but I wonder if that's also related to resolution. Specifically I'm on an old 1080p monitor so the lowest refresh rate I can drop to is 50Hz (and the highest ~72Hz), and neither seems to have any particularly noticeable effect on the audio output. I wonder if those having audio issues are running at a higher resolution, presumably 4K? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
** Description changed: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. + + Currently known affected cards: + + * HD 7700 (comment 8) + * R9 290 (comment 21) + * RX 550 (LP: #2012141, and comment 27) + * RX 570 (mine) + * RX 580 (LP: #2009276, and comment 28) + * WX 3200 (comment 29) + * RX 6600 (LP: #2009542) + * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. Currently known affected cards: * HD 7700 (comment 8) * R9 290 (comment 21) * RX 550 (LP: #2012141, and comment 27) * RX 570 (mine) * RX 580 (LP: #2009276, and comment 28) * WX 3200 (comment 29) * RX 6600 (LP: #2009542) * RX 6700 (LP: #2009275) [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@duxeu To fill in a bit of background here, the AMD folks were emailed in the background and are of the same opinion. Personally, I'm not sure the bisect *did* identify that as the commit, but unfortunately bisection isn't an entirely straight-forward process when dealing with packages that have a ton of Ubuntu-specific patches on top of them (as the kernel naturally does). @kobako Are there any further test kernels to try? In the meantime I'll stick the currently affected list of cards at the top so new people coming to the bug can easily check against the list (though I have a feeling, looking at the list, it could be summarised as "pretty much all AMD GPUs"). -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2012141] Re: [22.04] After upgrade to 22.04.2, hdmi audio output is no longer detected
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 >From lspci.txt it appears your GPU is a Radeon RX 550, so this is almost certainly a duplicate of LP: #2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2012141 Title: [22.04] After upgrade to 22.04.2, hdmi audio output is no longer detected Status in linux package in Ubuntu: Confirmed Bug description: Hi, since upgrade to Ubuntu 22.04.2, I have no longer HDMI audio input being detected. It doesn't show as an option in Sound settings and thus doesn't output audio to a monitor attached via HDMI. I noticed the following logs in dmesg: [5.466172] snd_hda_intel :08:00.1: Handle vga_switcheroo audio client [5.466174] snd_hda_intel :08:00.1: Force to non-snoop mode [5.466399] snd_hda_intel :0a:00.4: enabling device ( -> 0002) [5.468656] hdaudio hdaudioC0D0: no AFG or MFG node found [5.468672] snd_hda_intel :08:00.1: no codecs initialized The reason might be the same as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993884 I'm using AMD Ryzen 3900X. $ uname -a Linux adrian-desktop 5.19.0-35-generic #36~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Feb 17 15:17:25 UTC 2 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; UBUNTU_CODENAME=jammy Please let me know if I need to provide more information. Thanks, Adi --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: adrian14268 F pulseaudio /dev/snd/pcmC1D1p: adrian14268 F...m pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-02-06 (39 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp4s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. X570 AORUS ELITE Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=ce95ca9b-9845-4bf9-9323-5ed5327454d5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: jammy wayland-session Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/26/2022 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F37 dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS ELITE dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF37:bd12/26/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSELITE:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 AORUS ELITE dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2012141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@koba I've tried each of the kernels in comment 25 and I'm afraid it rather refutes the theory that fdcc4c22b is the culprit: The latest vanilla kernel (#1) is "good"; HDMI audio works happily. That suggests (although not conclusively) that fdcc4c22b isn't the culprit as it presumably includes that commit. The latest vanilla kernel with fdcc4c22b reverted (#2) is also "good"; HDMI audio works, although I did note dmesg had an awful lot of preempt errors reported in it (which did not appear with the vanilla kernel above). Finally, just to put the nail in the coffin of fdcc4c22b being the faulty commit, the 5.19.0-35 kernel with fdcc4c22b reverted (#3) is "bad"; exhibits the original failure with HDMI audio being unavailable. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
** Description changed: + CLARIFICATION: Just to avoid any confusion for those coming to this bug + report; the "Jammy: invalid" status above does *not* mean that this bug + doesn't affect jammy -- it does, and the kernel team is aware of this. + All it reflects is that the fix has to go into the kinetic kernel + package which will then flow into the kernel-hwe package implicitly. + + [ Original Description ] + After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009815] Re: No HDMI audio anymore
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2009815 Title: No HDMI audio anymore Status in linux package in Ubuntu: Confirmed Bug description: lsb_release -rd Description: Ubuntu 22.10 Release: 22.10 Wayland 5.19.0-35-generic does not work 5.19.0-32-generic does work If following messages occures during boot, no HDMI audio : hdaudio hdaudioC1D0: no AFG or MFG node found snd_hda_intel :01:00.1: no codecs initialized No HDMI Audio does mean : Via lspci -nnk I get the following device : 01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1002:aae0] Subsystem: ASUSTeK Computer Inc. Baffin HDMI/DP Audio [Radeon RX 550 640SP / RX 560/560X] [1043:aae0] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel But this device will neither be indicated via pavucontrol nor via audio settings (mainsettings). Before I did installed the Ubuntu 22.10 on my system, I did test the live system. It did work without problems. And two audio devices, that is what I expect, will be indicated in the audio settings (one of them, the given above via lspci -nnk, is necessary to have audio via HDMI) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: richard1402 F wireplumber /dev/snd/seq:richard1399 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Mar 9 10:11:41 2023 InstallationDate: Installed on 2023-03-04 (4 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=df59b1c2-c5b9-483d-b033-7c6b2264dc75 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4802 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M PRO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev x.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4802:bd09/18/2013:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MPRO:rvrRevx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2011334] Re: amdgpu HDMI audio device missing on kernel 5.15.0-35 / 5.19.0-35
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 I'm *reasonably* certain this is a duplicate of LP: #2009136 as that covers kernel 5.19.0-35. I don't think there *is* a 5.15.0-35, and the "reversion to 5.15.0-67" (which is the current 5.15 release) also suggests that this is limited to affecting the 5.19 releases, not the 5.15 releases. Anyway, marking this as a duplicate of the aforementioned bug for now but please do correct me if I'm wrong! ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 & -37 (regression from -32) -- 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/2011334 Title: amdgpu HDMI audio device missing on kernel 5.15.0-35 / 5.19.0-35 Status in linux package in Ubuntu: Incomplete Bug description: Multiple reports of amdgpu HDMI audio device becomes missing and the issue got fixed by reverting to 5.15.0-67 kernel https://askubuntu.com/questions/1457524/hdmi-audio-not-detected-after-update-for-amd-graphics https://askubuntu.com/questions/1457893/my-hdmi-display-port-audio-stopped-working-on-ubuntu-22-10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: unm2638 F pulseaudio /dev/snd/controlC0: unm2638 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2020-04-23 (1053 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200422) MachineType: Gigabyte Technology Co., Ltd. Z97X-SLI Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic root=UUID=1db4cc4a-3e35-473c-9a5e-4b36d3282c60 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 Tags: jammy wayland-session Uname: Linux 5.19.0-35-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-05-05 (310 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo wireshark _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F8 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97X-SLI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF8:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnZ97X-SLI:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97X-SLI-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97X-SLI dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2011334/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 & -37 (regression from -32)
@Timo ah I see, sorry for the noise! -- 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/2009136 Title: No HDMI audio under 5.19.0-35 & -37 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux source package in Kinetic: In Progress Bug description: CLARIFICATION: Just to avoid any confusion for those coming to this bug report; the "Jammy: invalid" status above does *not* mean that this bug doesn't affect jammy -- it does, and the kernel team is aware of this. All it reflects is that the fix has to go into the kinetic kernel package which will then flow into the kernel-hwe package implicitly. [ Original Description ] After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@bpl indeed -- I asked Timo if the targeting should be adjusted in comment 9 as I wasn't sure if the kernel team wanted to track this separately over in the hwe package, but given this bug was moved from that package this one I may as well just add jammy to the affected set. ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Errr, let me try that again from root so it's actually got the caps output! ** Attachment added: "lspci.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653114/+files/lspci.out -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.15.9003-68-generic kernel in comment 16 is "good"; HDMI audio detected and working happily. I'm attaching the requested lspci output. ** Attachment added: "lspci.out" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+attachment/5653113/+files/lspci.out -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9002-34-generic kernel in comment 14 is also "bad" -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9001-34-generic kernel provided in comment 12 is also "bad" (same symptoms, same dmesg lines as seen in the -35 kernel) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009032] Re: Kernel 5.19.0-35 killed HDMI audio for me
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 My apologies; I'm going to mark this as a duplicate of LP: #2009136 even though that bug was reported later as it's very likely the same issue (AMD-based card with HDMI audio output), and that seems to be where the kernel team are currently bisecting the issue. Sorry I didn't spot this one when reporting 2009136! ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009032 Title: Kernel 5.19.0-35 killed HDMI audio for me Status in linux package in Ubuntu: Incomplete Bug description: On Kernel 5.19.0-32 everything is working fine. But when updating to Kernel 5.19.0-35, HDMI audio is no longer listed/working. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009032/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009287] Re: When using this kernel, the HDMI audio output dissapears
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- 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/2009287 Title: When using this kernel, the HDMI audio output dissapears Status in linux package in Ubuntu: Confirmed Bug description: I saw this bug with incomplete status already, because of missing logs. Tryed to attach the logs to that report, but it apport wont allow and suggested me to create a new bug report. The automated way with apport-bug doesn't help because it will not find the HDMI audio hardware (thats precisely the bug). So if I boot with this kernel, HDMI video output still works, but HDMI audio output dissapears from the sound manager If I boot with Kernel 5.19.0-32 everything works back as expected. I'm in a Ubuntu 22.04 derivate: Linux Mint 21.1 Included lspci-vnvn.log in attach. Its not possible to attach a second file so here is the output of cat version.log Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 OS Info: lsb_release -rd Description: Linux Mint 21.1 Release: 21.1 cat /etc/upstream-release/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu Jammy Jellyfish" uname -r 5.19.0-35-generic What I expected to happen: To have access to the audio hardware provided by the HDMI port What happened instead I only was able to access the main audio hardware of the motherboard --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rodolfo1805 F pulseaudio /dev/snd/controlC2: rodolfo1805 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: MATE DistroRelease: Linux Mint 21.1 InstallationDate: Installed on 2023-01-29 (34 days ago) InstallationMedia: Linux Mint 21.1 "Vera" - Release amd64 20221217 MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: root=UUID=497c97d4-1df7-456f-a954-3a7035c795fa ro rootflags=subvol=@ quiet splash initrd=@\boot\initrd.img-5.19.0-35-generic ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.10 RfKill: Tags: vera Uname: Linux 5.19.0-35-generic x86_64 UnreportableReason: Este informe es sobre un paquete que no se encuentra instalado. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: False dmi.bios.date: 03/04/2016 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0309 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A/USB 3.1 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0309:bd03/04/2016:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A/USB3.1:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
@kobako the 5.19.9000-34-generic kernel provided in comment 10 is "bad" (no HDMI audio present, same dmesg lines as seen in the -35 kernel) -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Hi Timo, this also affects jammy -- should I add that to the targeting, or is that to be handled separately? -- 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/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: In Progress Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
Looking through the growing list of duplicates, everyone has an AMD GPU so this is almost certainly an issue in that driver. The list of cards affected so far: * RX570 (mine) * RX6700 XT (from LP: #2009275) * RX580 (from LP: #2009276) * RX6600 (from LP: #2009542) I'm happy to post any additional logs / traces that would help debug this and/or test patched kernels (worth looking at the duplicates for additional logs too). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009276] Re: Audio Hdmi (Radeon rx580) not recognized
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009276 Title: Audio Hdmi (Radeon rx580) not recognized Status in linux-signed-hwe-5.19 package in Ubuntu: Confirmed Bug description: After kernel upgrade, from 5.19.0-32 to 5.19.0-35 the audio don't work. At boot appears the message: hdaudio_hdaudioC0D0: no AFG or MFG node found snd_hda-intel :26:00.1: no codecs initialized Processor: AMD® Ryzen 5 3600 6-core processor × 12 Graphic: AMD® Radeon rx 580 series OS Name: Ubuntu 22.04.2 LTS 64-bit GNOME version: 42.5 Graphic System: Wayland ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-35-generic 5.19.0-35.36~22.04.1 ProcVersionSignature: Ubuntu 5.19.0-32.33~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 4 19:17:19 2023 InstallationDate: Installed on 2022-05-07 (301 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009276/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009542] Re: Can not select HDMI or Displayport as audio output device.
*** This bug is a duplicate of bug 2009136 *** https://bugs.launchpad.net/bugs/2009136 ** This bug has been marked a duplicate of bug 2009136 No HDMI audio under 5.19.0-35 (regression from -32) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009542 Title: Can not select HDMI or Displayport as audio output device. Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After I installed "linux-image-5.19.0-35-generic" package, I can not select HDMI or Displayport as audio output device in gnome setting. When I am using "linux-image-5.19.0-32-generic" package, I can select that. My PC also have S/PDIF as audio output device, I can select it. My environment is follows. Description: Ubuntu 22.04.2 LTS Release: 22.04 Graphics board: Radeon RX6600 Graphics driver: amdgpu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009542/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651269/+files/pactl-list-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "pactl-list-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651268/+files/pactl-list-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-35" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651267/+files/dmesg-5.19.0-35 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] Re: No HDMI audio under 5.19.0-35 (regression from -32)
** Attachment added: "dmesg-5.19.0-32" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+attachment/5651266/+files/dmesg-5.19.0-32 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2009136] [NEW] No HDMI audio under 5.19.0-35 (regression from -32)
Public bug reported: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2009136 Title: No HDMI audio under 5.19.0-35 (regression from -32) Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: After upgrading my Ubuntu jammy (22.04) desktop to the -35 release of the kernel, I found my HDMI audio output device had disappeared. Reverting to the -32 release caused it to appear again (hence why I'm filing the bug against the kernel rather than pulseaudio). I'm attaching the dmesg output from immediately after booting each kernel, but after a bit of trimming and diffing I *think* the following lines are the salient ones: input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input12 input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input13 input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input14 input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input15 input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input16 input: HDA ATI HDMI HDMI/DP,pcm=11 as /devices/pci:00/:00:03.1/:2b:00.1/sound/card0/input17 snd_hda_intel :2b:00.1: bound :2b:00.0 (ops amdgpu_dm_audio_component_bind_ops [amdgpu]) These lines appear in the dmesg of the -32 kernel, but not in the -35 kernel's log. Meanwhile, the following lines appear in the -35 kernel's log but not in the -32: hdaudio hdaudioC0D0: no AFG or MFG node found snd_hda_intel :2b:00.1: no codecs initialized I'll also attach the output of "pactl list" under each kernel (this shows the HDMI audio sink showing up under -32, but not -35) just in case that helps shed any light on things. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2009136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1436945] Re: devel: consider fq_codel as the default qdisc for networking
Just to point out here that fq_codel is not enabled properly in 22.10 https://bugs.launchpad.net/ubuntu/+bug/2003027 -- 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/1436945 Title: devel: consider fq_codel as the default qdisc for networking Status in linux package in Ubuntu: Fix Released Status in linux package in Debian: Fix Released Bug description: This was raised on the kernel-team@ mailing list, we should look at this if other distros are starting to move. === Date: Tue, 24 Mar 2015 10:54:37 -0700 From: Dave Taht To: Joseph Salisbury Cc: Kernel Team , ubuntu-de...@lists.ubuntu.com Subject: Re: Minutes from the Ubuntu Kernel Team meeting, 2015-03-24 I must confess I had hoped ubuntu would adopt fq_codel as the default qdisc in this go-around. It is still not quite part of fedora´s default either, but is now in arch, (and nearly everyone else downstream from systemd), and has long been the default in openwrt, and at this point, just requires a single sysctl to enable. It certainly could use more widespread testing, perhaps in the next release? d@nuc-client:~$ cat /etc/sysctl.d/10-bufferbloat.conf net.core.default_qdisc=fq_codel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436945/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999970] Re: Plasma notification setting not honoured
command ran ** Package changed: linux (Ubuntu) => spectacle (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/170 Title: Plasma notification setting not honoured Status in spectacle package in Ubuntu: Confirmed Bug description: My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference System Information: Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy apt search spectacle Sorting... Done Full Text Search... Done kde-spectacle/jammy,now 21.12.3-0ubuntu1 amd64 [installed,automatic] Screenshot capture utility Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 17415 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-06 (10 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ProBook 430 G8 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=98d30782-7dc6-42a3-9d7f-f9e0e38bdad1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.7 Tags: jammy Uname: Linux 5.15.0-56-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/05/2022 dmi.bios.release: 9.1 dmi.bios.vendor: HP dmi.bios.version: T70 Ver. 01.09.01 dmi.board.name: 87DF dmi.board.vendor: HP dmi.board.version: KBC Version 33.1C.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 51.28 dmi.modalias: dmi:bvnHP:bvrT70Ver.01.09.01:bd05/05/2022:br9.1:efr51.28:svnHP:pnHPProBook430G8NotebookPC:pvr:rvnHP:rn87DF:rvrKBCVersion33.1C.00:cvnHP:ct10:cvr:sku2V656AV: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 430 G8 Notebook PC dmi.product.sku: 2V656AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spectacle/+bug/170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1999970] Re: Plasma notification setting not honoured
apport information ** Tags added: apport-collected jammy ** Description changed: My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference System Information: Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy apt search spectacle Sorting... Done Full Text Search... Done kde-spectacle/jammy,now 21.12.3-0ubuntu1 amd64 [installed,automatic] Screenshot capture utility Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.2 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: greg 17415 F pulseaudio + CRDA: N/A + CasperMD5CheckResult: pass + CurrentDesktop: KDE + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-12-06 (10 days ago) + InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) + MachineType: HP HP ProBook 430 G8 Notebook PC + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=98d30782-7dc6-42a3-9d7f-f9e0e38bdad1 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-56-generic N/A + linux-backports-modules-5.15.0-56-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.7 + Tags: jammy + Uname: Linux 5.15.0-56-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 05/05/2022 + dmi.bios.release: 9.1 + dmi.bios.vendor: HP + dmi.bios.version: T70 Ver. 01.09.01 + dmi.board.name: 87DF + dmi.board.vendor: HP + dmi.board.version: KBC Version 33.1C.00 + dmi.chassis.type: 10 + dmi.chassis.vendor: HP + dmi.ec.firmware.release: 51.28 + dmi.modalias: dmi:bvnHP:bvrT70Ver.01.09.01:bd05/05/2022:br9.1:efr51.28:svnHP:pnHPProBook430G8NotebookPC:pvr:rvnHP:rn87DF:rvrKBCVersion33.1C.00:cvnHP:ct10:cvr:sku2V656AV: + dmi.product.family: 103C_5336AN HP ProBook + dmi.product.name: HP ProBook 430 G8 Notebook PC + dmi.product.sku: 2V656AV + dmi.sys.vendor: HP ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/170/+attachment/5636165/+files/AlsaInfo.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/170 Title: Plasma notification setting not honoured Status in spectacle package in Ubuntu: Confirmed Bug description: My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference System Information: Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy apt search spectacle Sorting... Done Full Text Search... Done kde-spectacle/jammy,now 21.12.3-0ubuntu1 amd64 [installed,automatic] Screenshot capture utility Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: greg 17415 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: KDE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-12-06 (10 days ago) InstallationMedia: Kubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) MachineType: HP HP ProBook 430 G8 Notebook PC Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic root=UUID=98d30782-7dc6-42a3-9d7f-f9e0e38bdad1 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-56-generic N/A linux-backports-modules-5.15.0-56-generic N/A linux-firmware
[Kernel-packages] [Bug 1999970] [NEW] Plasma notification setting not honoured
Public bug reported: My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference System Information: Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy apt search spectacle Sorting... Done Full Text Search... Done kde-spectacle/jammy,now 21.12.3-0ubuntu1 amd64 [installed,automatic] Screenshot capture utility Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot-HP 2022-12-17 at 10.28.47.jpg" https://bugs.launchpad.net/bugs/170/+attachment/5636161/+files/Screenshot-HP%202022-12-17%20at%2010.28.47.jpg -- 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/170 Title: Plasma notification setting not honoured Status in linux package in Ubuntu: New Bug description: My notification pop-up timeout is set for 1second. Taking a screenshot with spectacle I expect the pop up to be removed after 1 second. The pop up stays for 5 seconds which is the default for the notification. reboot/restart of KDE/Plasma makes no difference System Information: Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy apt search spectacle Sorting... Done Full Text Search... Done kde-spectacle/jammy,now 21.12.3-0ubuntu1 amd64 [installed,automatic] Screenshot capture utility Operating System: Kubuntu 22.04 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 Kernel Version: 5.15.0-56-generic (64-bit) Graphics Platform: X11 Processors: 8 × 11th Gen Intel® Core™ i5-1135G7 @ 2.40GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/170/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1958918] Re: dependency on crda obsolete according to Debian
@vorlon, I just found this ticket, and would like to report that my Intel AX211 wifi card no longer connects via 6ghz with the linux-oem-22.04b. It was working fine with the 5.15 kernel. I suspect regulatory compliance to be the issue as all of the 6ghz channels show disabled when running $ sudo iw phy0 channels. They also are unlisted when running $ sudo iw reg get I haven't figured out how to manually fix this yet. I have tried adding the missing iwlwifi-so-a0-gf-a0-72.ucode to /lib/firmware and it loads, but this did not fix the issue as I expected. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/1958918 Title: dependency on crda obsolete according to Debian Status in crda package in Ubuntu: New Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: Fix Released Status in linux-lowlatency package in Ubuntu: Fix Released Status in linux-oracle package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Status in crda source package in Jammy: New Status in linux source package in Jammy: Fix Released Status in linux-aws source package in Jammy: Fix Released Status in linux-azure source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Released Status in linux-lowlatency source package in Jammy: Fix Released Status in linux-oracle source package in Jammy: Fix Released Status in linux-raspi source package in Jammy: Fix Released Status in crda package in Debian: Fix Released Bug description: Debian has just removed the crda package from the archive, stating that it is obsolete with current kernels: https://bugs.debian.org/1003903 We need someone to determine if this is accurate for Ubuntu as well, and if so, update the kernel packaging to not depend on crda anymore so it can be removed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crda/+bug/1958918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993120] Re: armhf kernel compiled with gcc-12 fails to boot on pi 3/2
Is there actually an issue in gcc-12 here? Looking at the patch Juerg linked to, it appears to be a kernel issue only? -- 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/1993120 Title: armhf kernel compiled with gcc-12 fails to boot on pi 3/2 Status in gcc-12 package in Ubuntu: Incomplete Status in linux package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Fix Released Status in gcc-12 source package in Kinetic: New Status in linux source package in Kinetic: Fix Committed Status in linux-raspi source package in Kinetic: Invalid Bug description: Kinetic 5.19 kernels compiled with gcc-12 for armhf don't boot or hang on Pi 3 and 2. Seems to work fine on Pi 4. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-12/+bug/1993120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1989713] Re: Old start4.elf / fixup4.dat in 22.04
Marking linux-firmware-raspi2 invalid for now; will be used if we decide to backport to focal. Currently prepping an upload for ppa:waveform/firmware with a test updated firmware. If that works well, will upload to lunar then start SRU to kinetic and jammy. ** Also affects: linux-firmware-raspi2 (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi2 (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-raspi (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided Status: Confirmed ** Also affects: linux-firmware-raspi2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-raspi (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Lunar) Status: Confirmed => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-firmware-raspi2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Assignee: (unassigned) => Dave Jones (waveform) ** Changed in: linux-firmware-raspi (Ubuntu Jammy) Milestone: None => ubuntu-22.04.2 ** Changed in: linux-firmware-raspi (Ubuntu Lunar) Milestone: None => ubuntu-23.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1989713 Title: Old start4.elf / fixup4.dat in 22.04 Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-firmware-raspi2 package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: Invalid Status in linux-firmware-raspi source package in Jammy: Confirmed Status in linux-firmware-raspi2 source package in Jammy: Invalid Status in linux-raspi source package in Jammy: Invalid Status in linux-firmware-raspi source package in Kinetic: Confirmed Status in linux-firmware-raspi2 source package in Kinetic: Invalid Status in linux-raspi source package in Kinetic: Invalid Status in linux-firmware-raspi source package in Lunar: Confirmed Status in linux-firmware-raspi2 source package in Lunar: Invalid Status in linux-raspi source package in Lunar: Invalid Bug description: Hi there, there is the issue connected with "Initramfs unpacking failed: Decoding failed" error during Ubuntu boot. See https://github.com/raspberrypi/firmware/issues/1746 and https://github.com/raspberrypi/firmware/issues/1731. The Raspberry Pi have the update for start4.elf / fixup4.dat with fix it. Could you please include update for these files in new ubuntu release ASAP? Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi/+bug/1989713/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
So where are we on this folks? -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Invalid Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
Alright so that means we either need to push a change to remove noexec from the kernel init code, or we go ahead with noexec, and give people on option to remount with exec should they want sgx functionality. I do think the nosuid flag does still provide some benefit even if we decide not to include the noexec flag by default until 5.17+. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: In Progress Status in systemd source package in Focal: Invalid Status in linux source package in Jammy: In Progress Status in systemd source package in Jammy: Invalid Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-p
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
In case anyone is curious conversation is on-going on the kernel-team mailing list https://lists.ubuntu.com/archives/kernel-team/2022-October/133764.html -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
@juliank, is this an aws system? If not there's a good chance that you are using an initramfs to mount the filesystems. That's definited in either /etc/init.d/udev or directly out of the init that lives in the initramfs. -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid or noexec
Here is a workaround for this issue in case anyone finds this in the future. Copy remount_dev.service to /etc/systemd/system sudo chown root:root /etc/systemd/system/remount_dev.service sudo systemctl daemon-reload sudo systemctl enable remount_dev.service Still I think the kernel patch should be applied, but at least there's a workaround for now. ** Attachment added: "Systemd unit file as workaround" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+attachment/5622080/+files/remount_dev.service -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linu
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Information type changed from Private Security to Public Security ** Summary changed: - dev file system is mounted without nosuid + dev file system is mounted without nosuid or noexec -- 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/1991975 Title: dev file system is mounted without nosuid or noexec Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: [ SRU TEMPLATE ] [ Impact ] * nosuid, and noexec bits are not set on /dev * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. * It is not best security practice. [ Test Plan ] 1.Boot a Canonical Supplied EC2 instance 2.Check the mount options for /dev. 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] * As of 2022/10/06, I need to test this, but don't know how to build -aws flavored ubuntu kernels. Instructions welcome. I'm holding off on adding SRU tags until I can actually get this tested. * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ * Low risk if a driver depends on /dev allowing suid or exec this might prevent boot. That being said, all kernels that have been booting with an initramfs have been getting nosuid, and noexec set so hopefully we can consider that risk fairly well tested. [ Other Info ] * Patch is accepted into 5.17, and will drop out quickly * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully <<< ORIGINAL TEXT This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Description changed: + [ SRU TEMPLATE ] + [ Impact ] + + * nosuid, and noexec bits are not set on /dev + * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. + * It is not best security practice. + + [ Test Plan ] + +1.Boot a Canonical Supplied EC2 instance +2.Check the mount options for /dev. +3.You will notice the lack of nosuid and noexec on /dev. + + [ Where problems could occur ] + + * As of 2022/10/06, I need to test this, but don't know how to build + -aws flavored ubuntu kernels. Instructions welcome. + + * If this is applied to non initramfs-less kernels it could potentially cause a regression for very old hardware that does nefarious things with memory. For a larger discussion about that see: + https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ + + * Low risk if a driver depends on /dev allowing suid or exec this might + prevent boot. That being said, all kernels that have been booting with + an initramfs have been getting nosuid, and noexec set so hopefully we + can consider that risk fairly well tested. + + [ Other Info ] + + * Patch is accepted into 5.17, and will drop out quickly + * Any server booting with an initramfs already has nosuid, and noexec set, so hopefully + + + <<< ORIGINAL TEXT + This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen ** Description changed: [ SRU TEMPLATE ] - [ Impact ] + [ Impact ] - * nosuid, and noexec bits are not set on /dev - * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. - * It is not best security practice. + * nosuid, and noexec bits are not set on /dev + * This has the potential for nefarious actors to use this as an avenue for attack. see https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 for more discussion around this. + * It is not best security practice. [ Test Plan ] -1.Boot a Canonical Supplied EC2 instance -2.Check the mount options for /dev. -3.You will notice the lack of nosuid and noexec on /dev. + 1.Boot a Canonical Supplied EC2 instance + 2.Check the mount options for /dev. + 3.You will notice the lack of nosuid and noexec on /dev. [ Where problems could occur ] - * As of 2022/10/06, I need to test this, but don't know how to build - -aws flavored ubuntu kernels. Instructions welcome. + * As of 2022/10/06, I need to test this, but don't know how to build +
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: systemd (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: Confirmed Status in systemd source package in Jammy: Confirmed Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: New Status in systemd source package in Jammy: New Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
Looks like Kees already found this years ago. https://lore.kernel.org/lkml/YcMfDOyrg647RCmd@debian-BULLSEYE-live-builder-AMD64/T/ Looks like it was accepted as commit 28f0c335dd4a1 in 5.17. So I think we should apply this patch and the corresponding set CONFIG_DEVTMPFS_SAFE=y at least for the aws kernel and preferably all the 5.15 kernels. -- 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/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in linux source package in Jammy: New Status in systemd source package in Jammy: New Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
I was hoping to work around this in /etc/init.d/udev, but it looks like that gets redirected to systemctl via . lib/lsb/init-functions ** Description changed: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. - $ mount | grep devtmpfs - nosuid found in the options list. + $ mount | grep devtmpfs + nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: - + Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen -- 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/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: New Status in systemd source package in Focal: New Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid is not found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
So far I've only tested focal AWS images, but this may likely exist elsewhere as well. ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Status in linux source package in Focal: New Status in systemd source package in Focal: New Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991975] Re: dev file system is mounted without nosuid
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1991975 Title: dev file system is mounted without nosuid Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: This is similar to https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1450960 but new. I discovered that my ec2 instances based off of Canonical supplied AMI ami-0a23d90349664c6ee *(us-east-2), have dev mounted mounted without the nosuid option. https://us-east-2.console.aws.amazon.com/ec2/home?region=us- east-2#Images:visibility=public-images;imageId=ami-0a23d90349664c6ee My usb installed 20.04.4 home machine does not have this problem, but it has been installed for quite some time. My 22.04 laptop machine also does not have this issue. Reproduce. Start an ec2 instance based off of ami-0a23d90349664c6ee. $ mount | grep devtmpfs nosuid found in the options list. I've checked the initrd, and /etc/init.d/udev script and all places I know of where dev gets mounted set nosuid, so it's non-obvious what boot code-path is being taken that results in nosuid missing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: udev 245.4-4ubuntu3.18 ProcVersionSignature: Ubuntu 5.15.0-1020.24~20.04.1-aws 5.15.53 Uname: Linux 5.15.0-1020-aws x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 CasperMD5CheckResult: skip CustomUdevRuleFiles: 60-cdrom_id.rules 70-snap.snapd.rules Date: Thu Oct 6 17:39:42 2022 Ec2AMI: ami-0a23d90349664c6ee Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-east-2c Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: Xen HVM domU ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1020-aws root=PARTUUID=5bb90437-9efc-421d-aa94-c512c3b666a3 ro console=tty1 console=ttyS0 nvme_core.io_timeout=4294967295 panic=-1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/24/2006 dmi.bios.release: 4.2 dmi.bios.vendor: Xen dmi.bios.version: 4.2.amazon dmi.chassis.type: 1 dmi.chassis.vendor: Xen dmi.modalias: dmi:bvnXen:bvr4.2.amazon:bd08/24/2006:br4.2:svnXen:pnHVMdomU:pvr4.2.amazon:cvnXen:ct1:cvr:sku: dmi.product.name: HVM domU dmi.product.version: 4.2.amazon dmi.sys.vendor: Xen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1991975/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
** Tags added: foundations-todo -- 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/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990964] Re: FTBFS on kinetic
** Tags added: foundations-todo -- 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/1990964 Title: FTBFS on kinetic Status in linux package in Ubuntu: In Progress Status in strace package in Ubuntu: New Bug description: As can be seen in [1], strace FTBFS in kinetic: this is caused by the kernel headers (linux-libc-dev) which do not define F_GETLK64 and other on 64b builds because the kernel contains a bogus commit (306f7cc1e906 "uapi: always define F_GETLK64/F_SETLK64/F_SETLKW64 in fcntl.h"). This commit actually did the opposite of what it was supposed to do, namely defining those macros even on 64b builds. There is an attempt here to fix this which was not merged yet: https://lore.kernel.org/lkml/cajf2gtqtnmoeb62-63ou8y4dbrdym7iztdtfluxx9u0ltwu...@mail.gmail.com/T/ [1]: https://launchpadlibrarian.net/625441996/buildlog_ubuntu-kinetic- amd64.strace_5.16-0ubuntu4_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991254] [NEW] No HDMI sound output from alsa in server (no KMS)
Public bug reported: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Summary changed: - No HDMI sound output from alsa + No HDMI sound output from alsa in server (no KMS) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1991254 Title: No HDMI sound output from alsa in server (no KMS) Status in linux-raspi package in Ubuntu: New Bug description: During ISO testing of the beta Ubuntu Server 22.10 for Raspberry Pi armhf image, on a Raspberry Pi 4B, I noted that the HDMI "sound card" no longer appears in /proc/asound/cards; only the Headphones output (from the AUX socket on the board) appears. I checked with the current linux-raspi in the release pocket (5.19.0-1001-raspi), and the new one in proposed (5.19.0-1002-raspi), and both exhibit the same issue. On Kinetic: $ cat /proc/asound/cards 0 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones On Jammy: $ cat /proc/asound/cards 0 [b1 ]: bcm2835_hdmi - bcm2835 HDMI 1 bcm2835 HDMI 1 1 [Headphones ]: bcm2835_headpho - bcm2835 Headphones bcm2835 Headphones To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1991254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826228] Re: api3a+ hang when reading /sys/devices/platform/soc/driver_override
** Changed in: linux-raspi2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1826228 Title: api3a+ hang when reading /sys/devices/platform/soc/driver_override Status in linux-raspi2 package in Ubuntu: Invalid Bug description: I discovered this when running some tests on a core16 image with various rpi3 devices. Rpi3b, b+, cm3, rpi2, etc... don't have this problem, only rpi3a+. Kernel version: Linux localhost 4.4.0-1107-raspi2 #115-Ubuntu SMP Wed Apr 10 18:06:42 UTC 2019 armv7l armv7l armv7l GNU/Linux To reproduce, simply 'cat /sys/devices/platform/soc/driver_override' The process just hangs and cannot be killed. On other rpi devices, I just get this output immediately: (null) There was nothing in dmesg or syslog when it happened, no kernel crash, and I can still ssh into the system. The process that ran that command just silently hangs and can't be killed even with sudo kill -9. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1826228/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1988838] [NEW] No console output on kinetic pi server images
Public bug reported: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu- release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1988838 Title: No console output on kinetic pi server images Status in linux-raspi package in Ubuntu: New Bug description: On kinetic pi server daily images with the 5.19 linux-raspi kernel (e.g. from http://cdimage.ubuntu.com/ubuntu-server/daily- preinstalled/current/) there is no console output over HDMI. The "rainbow" boot screen appears as usual, but then remains while the system continues to boot and never switches to display the console. The system does still boot successfully, I can SSH into it, and console over serial still works but not over HDMI (testing on a Pi 3, and two revisions of the Pi 4). Adding either kms overlay (vc4-fkms-v3d or vc4-kms-v3d) to the boot configuration resolves this. Is it simply the case that future kernels are going to require a KMS overlay of some flavour or other to operate the console? If so, that's probably a good thing to some degree (it'll remove another difference between the pi server and desktop images), but ubuntu-release-upgrader will need to work to enforce that in the boot configuration for upgraders (and I'll need to tweak the gadget to ensure it's always included from now on). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1988838/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1982627] Re: MT7612u wireless chipset not working on Raspberry Pi 400
Looks like this is one of the ones moved to the modules-extra package (this split is kernel specific, and wasn't done on the PC kernel which probably explains why this adapter works on your PC installation of Ubuntu Server). If you do the following: $ sudo apt install linux-modules-extra-raspi You should then be able to modprobe usbmon. I'll move the bug over to linux-raspi as it's technically a kernel issue. ** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1982627 Title: MT7612u wireless chipset not working on Raspberry Pi 400 Status in linux-firmware package in Ubuntu: Invalid Status in linux-raspi package in Ubuntu: New Bug description: I purchased the Alfa AWUS036ACM wireless adapter to use with my Raspberry Pi 400. The adapter works when using Raspberry Pi OS, but not when using "Ubuntu for Raspberry Pi" release 22.04. I have tested 64-bit variants for Ubuntu Desktop and Ubuntu Server, and the results are the same. I followed the Kernel Firmware Debugging steps, and included its output below. The LinuxWireless Debugging steps seem to only be appropriate if the wireless adapter is working to some capacity so the below output does not include those steps. I also attempted to follow the Kernel USB Debugging steps, but the commands do not seem appropriate for the Raspberry Pi 400. For example, `/proc/bus/usb` and `/sys/kernel/debug/usb/usbmon/` do not exist on the filesystem. As part of troubleshooting, I updated the bootloader for the Raspberry Pi 400 to version 507b2360 which was built on 2022-04-26. I also ran `sudo apt update` and `sudo apt full-upgrade`. Neither of these troubleshooting steps resolved the problem. On a separate note, I have another Ubuntu Server release 22.04 that is installed on dedicated hardware (not the "Ubuntu for Raspberry Pi" variant), and the wireless adapter does work on this machine. Raspberry Pi 400 Output $ sudo modprobe usbmon modprobe: FATAL: Module usbmon not found in directory /lib/modules/5.15.0-1012-raspi $ lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 $ apt-cache policy linux-firmware linux-firmware: Installed: 20220329.git681281e4-0ubuntu3.2 Candidate: 20220329.git681281e4-0ubuntu3.2 Version table: *** 20220329.git681281e4-0ubuntu3.2 500 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages 100 /var/lib/dpkg/status 20220329.git681281e4-0ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages $ sudo udevadm control --log-priority debug $ tail -f /var/log/syslog Jul 22 20:56:03 ubuntu kernel: [ 533.687623] usb 2-1: new SuperSpeed USB device number 3 using xhci_hcd Jul 22 20:56:03 ubuntu kernel: [ 533.709177] usb 2-1: New USB device found, idVendor=0e8d, idProduct=7612, bcdDevice= 1.00 Jul 22 20:56:03 ubuntu kernel: [ 533.709203] usb 2-1: New USB device strings: Mfr=2, Product=3, SerialNumber=4 Jul 22 20:56:03 ubuntu kernel: [ 533.709214] usb 2-1: Product: Wireless Jul 22 20:56:03 ubuntu kernel: [ 533.709222] usb 2-1: Manufacturer: MediaTek Inc. Jul 22 20:56:03 ubuntu kernel: [ 533.709230] usb 2-1: SerialNumber: 0 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Validate module index Jul 22 20:56:03 ubuntu systemd-udevd[451]: Check if link configuration needs reloading. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device ready for processing (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: Successfully forked off 'n/a' as PID 1330. Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Worker [1330] is forked for processing SEQNUM=4179. Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Processing device (SEQNUM=4179, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: Failed to get watch handle, ignoring: No such file or directory Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'usb_id' Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: Device is queued (SEQNUM=4180, ACTION=add) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1:1.0: SEQNUM=4180 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: Device is queued (SEQNUM=4181, ACTION=bind) Jul 22 20:56:03 ubuntu systemd-udevd[451]: 2-1: SEQNUM=4181 blocked by SEQNUM=4179 Jul 22 20:56:03 ubuntu systemd-udevd[1330]: 2-1: /usr/lib/udev/rules.d/50-udev-default.rules:13 Importing properties from results of builtin command 'hwdb --subsystem=usb' J
[Kernel-packages] [Bug 1977764] Re: kernel modules "zstd" and "z3fold" missing.
** Also affects: ubuntu-seeds Importance: Undecided Status: New ** Changed in: ubuntu-seeds Assignee: (unassigned) => Dave Jones (waveform) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1977764 Title: kernel modules "zstd" and "z3fold" missing. Status in Ubuntu Seeds: New Status in linux-raspi package in Ubuntu: Invalid Status in ubuntu-settings package in Ubuntu: New Status in linux-raspi source package in Jammy: Invalid Status in ubuntu-settings source package in Jammy: New Status in linux-raspi source package in Kinetic: Invalid Status in ubuntu-settings source package in Kinetic: New Bug description: The modules "zstd" and "z3fold" are missing despite being configured for zswap in "/boot/firmware/cmdline.txt." Messages appear on boot display that state they do not exist and so instead use compressor "lzo" and pool "zbud". Ubuntu version is 22.04 LTS flashed from the official image. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-1008-raspi 5.15.0-1008.8 ProcVersionSignature: Ubuntu 5.15.0-1008.8-raspi 5.15.30 Uname: Linux 5.15.0-1008-raspi aarch64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: arm64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jun 6 17:29:00 2022 ImageMediaBuild: 20220419 SourcePackage: linux-raspi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-seeds/+bug/1977764/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
I've finished some research with this on one of the larger Pis (a 400) for performance measurements, and a memory limited Pi (Zero 2W) for an idea of the impact on memory usage. First the performance side of things: the good news is it doesn't make anything worse, the bad news is it doesn't make them *much* better (unlike on the PC where it apparently makes a substantial difference). The biggest difference on the Pi 400 was a drop from 16s to 13s in the jammy release of Firefox's cold startup time. However, there was no difference at all in the warm startup time, and the difference in the cold startup time disappeared almost entirely when using the candidate version of Firefox with the lang pack fix (diff was 0.3s -- which I'd assume is essentially nothing given I was doing manual timing and thus the times are subject to my reaction time of ~0.2s). On the memory side of things I used a selection of 6 snaps installed on the Pi Zero 2W: mosquitto, node-red, micropython, node, ruby, and lxd (a combination of relatively common and fairly IoT specific snaps) which is probably about as much as anyone could reasonably expect to install and run on a half-gig system. I measured the system after a fresh boot running only default services, and otherwise idle on the Raspberry Pi jammy (22.04 LTS) arm64 server image. The arm64 architecture was selected partly for the wider availability of snaps (there are very few built for armhf) and partly because memory effects were more likely to be pronounced on this architecture. Over the course of 30 minutes, everything from /proc/meminfo was dumped to an SQLite database, first under the current release of the kernel (5.15.0-1011-raspi), then under a re-built version with CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU enabled (and CONFIG_SQUASHFS_DECOMP_SINGLE disabled). MemAvailable stayed reasonably stable across each run, and showed a median ~12MB less on the MULTI_PERCPU kernel than on the SINGLE kernel, suggesting that each snap's mount occupied somewhere in the region of 2MB more memory under the MULTI_PERCPU kernel. Other statistics were less clear cut: no significant difference in kernel stack, and MemFree actually showed the opposite (but this should probably be ignored as it doesn't exclude evictable pages like the disk cache, and the kernel has a duty to minimize it so it will typically fall predictably on a freshly booted system meaning that differences in the start time of a measurement run will lead to an irrelevant delta). The kernel slab measure showed a interesting (stable, median) 6MB increase from the SINGLE to MULTI_PERCPU which may account for some of the extra memory being used. Conclusion: * There's some memory loss but it's small enough that it shouldn't significantly impact even tightly constrained systems like the Zero 2W * The performance gains are likely minimal under ARM. As such, were ARM the only set of architectures being considered I'd probably recommend against this * However, the performance gains on the x86 family are significant so for me this comes down to a "lack of harm" judgment: If this can be enabled on amd64 and disabled on armhf+arm64 then that would probably be the ideal situation. However, I'm mindful that any delta means extra maintenance work, and an extra chance for errors. Given the mixed situation on ARM (minor performance gain, minor memory loss), I'd recommend simply enabling this option across the board. -- 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/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1980861] Re: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU
I'm hoping to look into the effects of MULTI_PERCPU on the smaller Pi platforms (in particular the Pi Zero 2 and 3A+ which each have 512MB of RAM and, with the arm64 arch, typically have ~250MB free at runtime). Unfortunately building a local version of the linux-raspi package (just naively with sbuild) has thus far defeated me, but if I can get a version with the relevant config I'll run through some tests. -- 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/1980861 Title: Please enable CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU Status in Snappy: New Status in linux package in Ubuntu: Incomplete Bug description: The snapd/desktop/advocacy team are investigating the startup performance of running snaps. While doing this and comparing various distros (fedora, opensuse, ubuntu) on Igors reference hardware we noticed that fedora is substantially faster at starting snaps. After some research it turns out that they use the CONFIG_SQUASHFS_DECOMP_MULTI_PERCPU=y option when we use CONFIG_SQUASHFS_DECOMP_SINGLE. I build^Whacked a test kernel in my ppa:mvo/tmp PPA that just changes this one option (https://paste.ubuntu.com/p/NvS4GQjnSp/) and with that the first run firefox startup went from 15s to 6s (!) on Igors reference hardware. Given the dramatic performance improvements we would like to get this option switched. However we need to be careful and double check that the results from https://bugs.launchpad.net/snappy/+bug/1636847 are no longer an issue - back in 2016 the kernel team swtich to _DECOMP_SINGLE because just mounting a snap would use up 131Mb or memory(!). To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1980861/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead
I'm having a similar issue in Jammy again with an HDMI connected 2k monitor. The issue here being that the monitor works on boot up, but experiences this problem after a few hot plugs. Has someone found a follow-on ticket similar to this? -- 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/1901470 Title: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsyn
[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead
** Tags added: indeed jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901470 Title: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1080p instead Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline
