I upgraded to 7.0.0.22 kernel, and the stuttering might be worse than before -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
суббота
[Bug 2152124] Re: Sudden loss of session (back to login/initramfs screen)
Quick follow-up confirming the GTK hypothesis: I just performed an isolated test. I downloaded the exact same PDF file from the exact same portal, but this time using Google Chrome (with a User-Agent switcher to bypass portal restrictions). The result: No crash. Chrome downloaded and saved the file perfectly, and the system remained completely stable. This definitively proves that the hard lockup is not related to general I/O, filesystem, or the PDF file itself. The i915 crash is strictly and exclusively triggered by GTK applications (like Firefox or Remmina) updating their UI or handling file dialogs under Wayland. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152124 Title: Sudden loss of session (back to login/initramfs screen) Status in linux package in Ubuntu: New Bug description: When using Thunderbird under Wayland on Ubuntu 26.04 (Intel GPU, ASUS Zenbook UX310UA), pressing the Up/Down arrow keys to scroll through emails causes an immediate and hard crash of the GNOME Shell / Wayland compositor. The system drops connection to xwayland and crashes back to the disk decryption/login screen. The issue is 100% reproducible on Wayland. Workaround: Switching the session to "Ubuntu on Xorg" completely resolves the issue and Thunderbird works normally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-shell 50.1-0ubuntu1 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:32:06 2026 DisplayManager: gdm3 InstallationDate: Installed on 2025-05-25 (350 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 50.1-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to resolute on 2026-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152124/+subscriptions
[Bug 2150410] Re: APC UPS throws error on USB device
Ok - after some fiddeling (not being able to live without UPS stats ;-) ) I switched to NUTS (dumped apcupsd). After some cleaning apcsupsd (including removing libusb-0.1-4 and reinstalling libusb-1.0-0) I got NUTS up and running with no USB errors... (2 linux systems - same distro & kernel - different APC UPSes) Even after kernel upgrade from 7.0.0-15-generic to 7.0.0-22-generic everything works fine! This makes me think that the issue is either libusb-0.1-4 (prereq for apcupsd) OR apcupsd related. Just to give you guys a quick heads up! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2150410 Title: APC UPS throws error on USB device Status in linux package in Ubuntu: New Bug description: ERROR: kernel: hid-generic 0003:051D:0002.0006: Event data for report 22 was too short (4 vs 2) APCUPSd states UPS is disconnected apcaccess able to communicated I have to systems just upgraded from 25.10 -> 26.04 LTS (kernel 6.17.x -> 7.0.y) I supposed there is a bug in USB driver in Kernel 7 Please advice on next steps! Thanks Christian ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-14-generic 7.0.0-14.14 ProcVersionSignature: Ubuntu 7.0.0-14.14-generic 7.0.0 Uname: Linux 7.0.0-14-generic x86_64 NonfreeKernelModules: zfs AlsaDevices: total 0 crw-rw---- 1 root audio 116, 1 Apr 26 09:52 seq crw-rw---- 1 root audio 116, 33 Apr 26 09:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Mon Apr 27 08:19:01 2026 InstallationDate: Installed on 2023-08-20 (981 days ago) InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 (20230415) MachineType: ASUSTeK COMPUTER INC. P11C-C Series PciMultimedia: ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-14-generic root=UUID=37bd1ec3-9961-4cef-9b45-c8c23548bf56 ro libata.noacpi=1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-04-24 (3 days ago) acpidump: dmi.bios.date: 08/02/2024 dmi.bios.release: 65.1 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6501 dmi.board.asset.tag: Default string dmi.board.name: P11C-C Series dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6501:bd08/02/2024:br65.1:svnASUSTeKCOMPUTERINC.:pnP11C-CSeries:pvr6501:rvnASUSTeKCOMPUTERINC.:rnP11C-CSeries:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:sku:pfaServer: dmi.product.family: Server dmi.product.name: P11C-C Series dmi.product.version: 6501 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2150410/+subscriptions
[Bug 2152124] Re: Sudden loss of session (back to login/initramfs screen)
Hi Daniel, I have a critical update regarding the i915 Wayland crashes. I have managed to find a 100% reproducible trigger for the hard lockup, and I also discovered a severe UX bug in Plymouth that occurs immediately after this crash. Environment: Hardware: ASUS Zenbook UX331UA (Intel graphics) OS/Kernels tested: Ubuntu 26.04, kernels 7.0.0-15-generic and the latest 7.0.0-22-generic Session: Wayland Bug 1: Reproducible Hard Lockup (GTK / Wayland / i915 regression) The regression is still fully present in the new 7.0.0-22 kernel. The system suffers a hard lockup exactly at the moment specific GTK applications trigger a UI change (such as opening a save dialog or rendering a download completion notification). 100% Reproducible triggers: Firefox: Downloading and saving a PDF file. The system locks up the exact moment the download finishes and the UI attempts to update. Remmina: Exporting to PDF. Thunderbird: Launching the app (happened frequently, though might be partially mitigated in recent TB updates). The Crucial Clue: Google Chrome works perfectly and never crashes. It can download files and run for hours without issues. This strongly suggests the bug is strictly tied to how native GTK interacts with Wayland and the i915 driver. Chrome's Aura/Ozone engine bypasses the faulty calls entirely. Bug 2: LUKS / Plymouth Alt key trapping after the crash After the system hard-reboots from the crash mentioned above, the LUKS decryption screen (Plymouth) behaves erratically regarding keyboard input. The Right Alt (AltGr) key is intercepted by Plymouth and acts as a display switch. Pressing Right Alt + X or Right Alt + 3 (which is required to type the # character on a CZ keyboard layout) does not output the character into the password field. Instead, it forcefully switches Plymouth to the raw text tty console (and back to GUI on the next press). Result: It becomes physically impossible to unlock the encrypted drive if the password contains characters requiring the AltGr modifier. The only workaround is to forcefully power off the machine and do a cold boot, after which Plymouth behaves normally and accepts the # character. Let me know if you need any specific logs, though the hard lockup happens so fast that journalctl usually doesn't have time to flush the exact crash trace to the disk. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2152124 Title: Sudden loss of session (back to login/initramfs screen) Status in linux package in Ubuntu: New Bug description: When using Thunderbird under Wayland on Ubuntu 26.04 (Intel GPU, ASUS Zenbook UX310UA), pressing the Up/Down arrow keys to scroll through emails causes an immediate and hard crash of the GNOME Shell / Wayland compositor. The system drops connection to xwayland and crashes back to the disk decryption/login screen. The issue is 100% reproducible on Wayland. Workaround: Switching the session to "Ubuntu on Xorg" completely resolves the issue and Thunderbird works normally. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: gnome-shell 50.1-0ubuntu1 ProcVersionSignature: Ubuntu 7.0.0-15.15-generic 7.0.0 Uname: Linux 7.0.0-15-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:32:06 2026 DisplayManager: gdm3 InstallationDate: Installed on 2025-05-25 (350 days ago) InstallationMedia: Ubuntu 25.04 "Plucky Puffin" - Release amd64 (20250415.3) ProcEnviron: LANG=cs_CZ.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> RelatedPackageVersions: mutter-common 50.1-0ubuntu2 SourcePackage: gnome-shell UpgradeStatus: Upgraded to resolute on 2026-05-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2152124/+subscriptions
пятница
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
I am on 26.04 and I am experiencing this issue in games. Is there a *easy* fix for this right now? or do i just have to wait for the system to send an update? -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
Stuttering issues came back on the "22" kernel, have to stay on 17 for now! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2154558] Re: wrong signature in the kernel 7.0.0-22
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154558 Title: wrong signature in the kernel 7.0.0-22 Status in linux package in Ubuntu: New Bug description: I noticed something interesting in the latest kernel version, 7.0.0-22: The signature for the kernel, got from /boot/config-7.0.0-22-generic, is: CONFIG_VERSION_SIGNATURE="Ubuntu 7.0.0-22.22-generic 7.0.0" Notice that it says the version is 7.0.0. Thought the signature for the older version 7.0.0-17 is: CONFIG_VERSION_SIGNATURE="Ubuntu 7.0.0-17.17-generic 7.0.2" It says it's using version 7.0.2 as base. I understand that Ubuntu doesn't follow the official kernel versioning, but I usually use this information to know how much the Ubuntu kernel is updated. For instance, in this release, 7.0.0-22, I tested against Dirty Frag and Fragnesia, and both were fixed, so I think it should be 7.0.10 and not 7.0.0. ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-generic 7.0.0-22.22 ProcVersionSignature: Ubuntu 7.0.0-22.22-generic 7.0.0 Uname: Linux 7.0.0-22-generic x86_64 ApportVersion: 2.34.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 29 06:39:41 2026 InstallationDate: Installed on 2021-11-26 (1645 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IwDevWlp47s0f0Link: Not connected. MachineType: Dell Inc. Dell G15 5511 ProcFB: 0 nvidia-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-22-generic root=UUID=a15c1e1a-d162-4e98-98e6-bbc6e85a39c3 ro intel_iommu=on iommu=pt quiet splash crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-02-28 (90 days ago) dmi.bios.date: 03/31/2026 dmi.bios.release: 1.42 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.42.0 dmi.board.name: 0836K6 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.42.0:bd03/31/2026:br1.42:svnDellInc.:pnDellG155511:pvr:rvnDellInc.:rn0836K6:rvrA00:cvnDellInc.:ct10:cvr:sku0A70:pfaGSeries: dmi.product.family: GSeries dmi.product.name: Dell G15 5511 dmi.product.sku: 0A70 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154558/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
So is 7.0.0.22 based on the original kernel that shipped, but now with all the mitigations for "Dirty Frag" and the like? I would have thought it would be re-based to the v7.0.3 main-line kernel or higher. Bearing in mind the rate of CVEs that have been published over the last three weeks, I would imagine the goalposts are constantly shifting. It would be make any kernel testing extremely difficult. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
[Bug 2149877] Re: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system
7.0.0-22 doesn't include the bug fix for this issue, as 7.0.0-17 does. We'll have to wait until late June for another kernel upgrade, typically 7.0.0-23 or 24 to get that bug fix. Until then, we have to keep using 7.0.0-17. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2149877 Title: Intermittent micro‑stutters affecting mouse and audio after updating to Linux 7.0.0‑14‑generic on AMD system Status in linux package in Ubuntu: Confirmed Status in linux source package in Resolute: Confirmed Bug description: For the past few days I have been experiencing intermittent micro‑stutters in Ubuntu 26.04. The mouse cursor freezes for about half a second, and occasionally the system audio also cuts out briefly. This happens irregularly but repeatedly. The issue started after updating to Linux 7.0.0‑14‑generic. Around the same time, linux‑firmware was also updated, so I cannot determine which change might be responsible. On my laptop (Intel + Nvidia) I cannot reproduce the issue, but another user with AMD hardware reported similar symptoms on Discourse. Affected hardware: · CPU: AMD Ryzen 5 9600X (12) @ 5.49 GHz · GPU: AMD Radeon RX 9060 XT · OS: Ubuntu 26.04 Observed behaviour: · Mouse cursor freezes for ~0.5 seconds (“micro‑stutter”). · Occasional short audio dropouts. · I have not noticed the issue while gaming, although another user claims it also happens there. I would appreciate guidance on additional tools or diagnostics that could help identify the root cause. At the moment, the only evidence I can provide is the observed behaviour described above. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2149877/+subscriptions
четверг
[Bug 2154523] Re: [26.04] BCM57708 (Thor3) Hangs on Linux 7.0
** Tags added: kernel-daily-bug -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2154523 Title: [26.04] BCM57708 (Thor3) Hangs on Linux 7.0 Status in linux package in Ubuntu: New Bug description: Broadcom BCM57708 Thor Ultra (Thor3) drivers are present in Linux 7.0 kernel released with Ubuntu Resolute (26.04 LTS), however they hang on load: [ 1.496333] bng_en 0000:01:00.0: Broadcom BCM57708 ThorUltra 50Gb/100Gb/200Gb/400Gb/800Gb Ethernet found at mem 18018010000 [ 1.496341] bng_en 0000:01:00.0: 1024.000 Gb/s available PCIe bandwidth (64.0 GT/s PCIe x16 link), in Flit mode [ 1.498568] bng_en 0000:01:00.0: Default HWRM commands max timeout increased to 60 seconds [ 1.508703] bng_en 0000:01:00.0: Failed to allocate ctx mem rc: -22 [ 1.514563] bng_en 0000:01:00.0: Failed to register with firmware rc = -22 [ 1.514712] bng_en 0000:01:00.0: probe with driver bng_en failed with error -22 [ 1.525193] bng_en 0000:01:00.1: Broadcom BCM57708 ThorUltra 50Gb/100Gb/200Gb/400Gb/800Gb Ethernet found at mem 18018000000 [ 1.525199] bng_en 0000:01:00.1: 1024.000 Gb/s available PCIe bandwidth (64.0 GT/s PCIe x16 link), in Flit mode [ 1.527128] bng_en 0000:01:00.1: Default HWRM commands max timeout increased to 60 seconds [ 1.536024] bng_en 0000:01:00.1: Failed to allocate ctx mem rc: -22 [ 1.541309] bng_en 0000:01:00.1: Failed to register with firmware rc = -22 [ 1.546011] bng_en 0000:01:00.1: probe with driver bng_en failed with error -22 The issue appears to be already fixed upstream in the 7.1 tree via the following commits (1),(2). We need to include this fix in the Ubuntu 2.6.04 LTS kernel to properly enable these devices. I tested and both of them do apply to the 7.0 in-tree drivers. Thank you, Alan (1) https://github.com/torvalds/linux/commit/c6b34add67a5402f53359580956b5c318965a893.patch (2) https://github.com/torvalds/linux/commit/70d7c905a07ae8415b955569620bf2bf77423553.patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2154523/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-restricted-modules-nvidia-bos-7.0/7.0.0-2007.7~24.04.1)
All autopkgtests for the newly accepted linux-restricted-modules-nvidia-bos-7.0 (7.0.0-2007.7~24.04.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-470/470.256.02-0ubuntu0.24.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-restricted-modules-nvidia- bos-7.0 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-7.0/7.0.0-1008.8~24.04.1)
All autopkgtests for the newly accepted linux-meta-nvidia-7.0 (7.0.0-1008.8~24.04.1) for noble have finished running. The following regressions have been reported in tests triggered by the package: linux-nvidia-7.0/7.0.0-1008.8~24.04.1 (amd64, arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta-nvidia-7.0 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions
[Bug 1786013] Autopkgtest regression report (linux-meta-nvidia-6.17/6.17.0-1019.19)
All autopkgtests for the newly accepted linux-meta-nvidia-6.17 (6.17.0-1019.19) for noble have finished running. The following regressions have been reported in tests triggered by the package: dkms/3.0.11-1ubuntu13 (amd64) dpdk-kmods/0~20230205+git-1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://ubuntu-archive-team.ubuntu.com/proposed- migration/noble/update_excuses.html#linux-meta-nvidia-6.17 [1] https://documentation.ubuntu.com/project/SRU/howto/autopkgtest- failure/ Thank you! -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packaging resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions