[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
Sorry, just trying to help by providing reports an following the rules. I'll refrain from posting moving forward. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: In Progress Status in linux-meta-oem-6.8 package in Ubuntu: In Progress Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: In Progress Status in linux-meta-oem-6.8 source package in Noble: In Progress Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 == linux-meta, linux-meta-unstable, linux-meta-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The main fixes are in kernel & dkms packages. This adds ivsc-modules to Provides list of linux-image-generic as other built-in linux-modules-foo packages do. [Test Case] The generated meta package linux-image-generic should then provides "ivsc-modules". [Where problems could occur] Meta package changes only. No real effect but in package dependency. [Other Info] While the ivsc-dkms obsoletion only happens for kernel >= 6.8, this will only be nominated for Unstable/Noble/OEM-6.8. == ipu6-drivers, linux, linux-oem-6.8 == [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
Thanks, I tried the NVidia kernel 6.8.0-1005.5+1 from noble-proposed; still no detection. Could be that this predates that patch series? Not sure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
** Tags removed: verification-needed-noble ** Tags added: verification-failed-noble -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061747] Re: obsolete out-of-tree ivsc dkms in favor of in-tree one
I did the followings steps: - Added the noble-proposed repo - Installed the driver(s) using: `sudo apt install intel-ipu6-dkms/noble-proposed` - Confirmed that the correct package was installed: ``` $ apt policy intel-ipu6-dkms intel-ipu6-dkms: Installed: 0~git202404110253.97c94720-0ubuntu1 Candidate: 0~git202404110253.97c94720-0ubuntu1 Version table: *** 0~git202404110253.97c94720-0ubuntu1 100 100 http://us.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 Packages 100 /var/lib/dpkg/status 0~git202311240921.07f0612e-0ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu noble/universe amd64 Packages ``` - Rebooted I see no evidence that a ipu6 device was detected. E.g. nothing in kern.log from intel-ipu6 after the new driver package installed. Perhaps I'm I missed something important here? LMK if there's another test I can perform. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/2061747 Title: obsolete out-of-tree ivsc dkms in favor of in-tree one Status in ipu6-drivers package in Ubuntu: Fix Committed Status in ivsc-driver package in Ubuntu: Invalid Status in linux package in Ubuntu: In Progress Status in linux-meta package in Ubuntu: Triaged Status in linux-meta-oem-6.8 package in Ubuntu: Triaged Status in linux-oem-6.8 package in Ubuntu: In Progress Status in ipu6-drivers source package in Noble: Fix Committed Status in ivsc-driver source package in Noble: Invalid Status in linux source package in Noble: In Progress Status in linux-meta source package in Noble: Triaged Status in linux-meta-oem-6.8 source package in Noble: Triaged Status in linux-oem-6.8 source package in Noble: In Progress Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2061747 [Impact] Starting from kernel v6.8, Intel demands the use of in-tree VSC driver instead of the out-of-tree dkms originated from https://github.com/intel/ivsc-driver. [Fix] The in-tree vsc driver as of v6.8 still needs a few fixes to achieve the same support level to launch Intel IPU6 Camera devices. Commit 1,3, and 4 are to add supported devices and platforms. Commit 2 resolves an issue after resumed. [Test Case] This is supposed to work together with the updated dkms, which shall also be built along with the kernel itself as linux-modules- ipu6-. Install the corresponding kernel/modules packages and test camera functions. [Where problems could occur] While this is the first time we switch to in-tree VSC driver, and the out-of-tree driver is not aligned at the time of transition and probably never will, the provided functions and verified stability issues may vary. [Other Info] The dkms is created to be compatible of multiple kernel versions, yet the in-tree vsc driver transitioning should only happen for kernel >= v6.8. That is, oem-6.8, noble and linux-unstable will be nominated. == original bug description == Starting from kernel v6.8 (yet from the code diff it's v6.6), Intel demands the use of in-tree IVSC drivers instead of out-of-tree dkms from https://github.com/intel/ivsc-driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipu6-drivers/+bug/2061747/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063497] Re: MIPI camera on Lenovo Carbon X1 will not work
I moved the driver file up a directory from /lib/firmware/intel/ipu to /lib/firmware/intel and now the firmware appears to be loaded. But something else is still wrong here: [ 19.220279] intel-ipu6 :00:05.0: Device 0xa75d (rev: 0x0) [ 19.220291] intel-ipu6 :00:05.0: physical base address 0x603c00 [ 19.220292] intel-ipu6 :00:05.0: mapped as: 0x9d0decc9 [ 19.220340] intel-ipu6 :00:05.0: IPU in secure mode [ 19.220341] intel-ipu6 :00:05.0: IPU secure touch = 0x0 [ 19.220342] intel-ipu6 :00:05.0: IPU camera mask = 0xff [ 19.222151] intel-ipu6 :00:05.0: IPC reset done [ 19.222152] intel-ipu6 :00:05.0: cpd file name: intel/ipu6ep_fw.bin [ 19.223266] intel-ipu6 :00:05.0: FW version: 20230925 [ 19.226903] int3472-discrete INT3472:05: cannot find GPIO chip INTC1096:00, deferring -- 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/2063497 Title: MIPI camera on Lenovo Carbon X1 will not work Status in linux package in Ubuntu: New Bug description: I followed the suggestions here for handling the Intel MIPI camera replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo Perhaps I should have installed 22.04? Anyway, this is a new laptop so I went with the new release. I tried both the generic and oem kernel. Same. The pertinent message seems to be: [ 18.420012] intel-ipu6 :00:05.0: Direct firmware load for intel/ipu6ep_fw.bin failed with error -2 [ 18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed [ 18.420023] intel-ipu6: probe of :00:05.0 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2063497] [NEW] MIPI camera on Lenovo Carbon X1 will not work
Public bug reported: I followed the suggestions here for handling the Intel MIPI camera replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo Perhaps I should have installed 22.04? Anyway, this is a new laptop so I went with the new release. I tried both the generic and oem kernel. Same. The pertinent message seems to be: [ 18.420012] intel-ipu6 :00:05.0: Direct firmware load for intel/ipu6ep_fw.bin failed with error -2 [ 18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed [ 18.420023] intel-ipu6: probe of :00:05.0 failed with error -2 ** 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/2063497 Title: MIPI camera on Lenovo Carbon X1 will not work Status in linux package in Ubuntu: New Bug description: I followed the suggestions here for handling the Intel MIPI camera replacing 22.04 for 24.04: https://wiki.ubuntu.com/Lenovo Perhaps I should have installed 22.04? Anyway, this is a new laptop so I went with the new release. I tried both the generic and oem kernel. Same. The pertinent message seems to be: [ 18.420012] intel-ipu6 :00:05.0: Direct firmware load for intel/ipu6ep_fw.bin failed with error -2 [ 18.420017] intel-ipu6 :00:05.0: Requesting signed firmware failed [ 18.420023] intel-ipu6: probe of :00:05.0 failed with error -2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2063497/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060071] Re: Add initial r36.3 out-of-tree module meta packages
** Also affects: linux-meta-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2060071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060071] Re: Add initial r36.3 out-of-tree module meta packages
** Description changed: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: - * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and iGPU display drivers - * linux-nvidia-tegra-igx-rt-r36.3-igpu: for realtime kernel, R36.3 OOTM, and iGPU display drivers - * linux-nvidia-tegra-igx-r36.3-dgpu: for non-realtime kernel, R36.3 OOTM, and dGPU display drivers + * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM + * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx-modules-signed in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3: for non-realtime kernel, R36.3 OOTM * linux-nvidia-tegra-igx-rt-r36.3: for realtime kernel, R36.3 OOTM To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx-modules-signed/+bug/2060071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2060071] [NEW] Add initial r36.3 out-of-tree module meta packages
Public bug reported: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-rt-r36.3-igpu: for realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-r36.3-dgpu: for non-realtime kernel, R36.3 OOTM, and dGPU display drivers ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx-modules-signed in Ubuntu. https://bugs.launchpad.net/bugs/2060071 Title: Add initial r36.3 out-of-tree module meta packages Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: We want to enable tracks for different versions of the out-of-tree modules. For now we only have R36.3, so create the meta packages for that version. These meta packages include: * linux-nvidia-tegra-igx-r36.3-igpu: for non-realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-rt-r36.3-igpu: for realtime kernel, R36.3 OOTM, and iGPU display drivers * linux-nvidia-tegra-igx-r36.3-dgpu: for non-realtime kernel, R36.3 OOTM, and dGPU display drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx-modules-signed/+bug/2060071/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059738] Re: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04
It happens about every other shutdown/reboot. I'm having occasional problems with suspend as well, which works fine 50% of the time or else freezes. -- 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/2059738 Title: Kernel 6.8 - Shutdown/Reboot hangs on Noble 24.04 Status in snapd: Confirmed Status in linux package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: [Overview] I have been testing installations of a number of Lubuntu and Xubuntu Noble Numbat 24.04 Daily builds since Feb 2024 on a DELL Wyse 3040 (UEFI bios), more latterly focused on Lubuntu. It would appear that since introduction of Kernel 6.8 into the daily builds, the installed system fails to carry out a successful reboot or power off when commanded from the desktop or the command line [Symptoms] When selecting either Leave-->Shutdown or Leave-->Reboot from the control panel, the process starts shutting down processes in an orderly fashion, until it gets to the part where it needs to power off hardware, where it hangs. shutdown -H now also fails in the same manner shutdown -r now also fails in the same manner With quiet bootflag disabled, the last system message on display before the hang is "Starting reboot..." or "Starting power-off..." [Workaround] The power button must be pressed for 5 secs to power down the hardware [Possibly related bugs] #1594023 Poweroff or reboot hangs. Laptop won't shutdown. 16.04 #2036987 Laptop Does Not Power Off After Installing Daily Build Of 23.10 [Unsuccessful Workarounds] Tried boot flags acpi=force acpi=nocrq reboot=pci suggested in #1594023 - No effect [Observations] I do believe that shutdown/reboot was working correctly on a live USB Lubuntu Noble Numbat Alpha build on the same hardware downloaded 22-Feb-2024. This release had an earlier kernel than 6.8. Sadly i no longer have the .iso to confirm this. All Lubuntu Noble daily builds since kernel 6.8 was introduced appear to exhibit the symptoms as above [System info] Operating System: Ubuntu Noble Numbat (development branch) Kernel: Linux 6.8.0-11-generic Architecture: x86-64 Hardware Vendor: Dell Inc. Hardware Model: Wyse 3040 Thin Client Firmware Version: 1.2.5 Firmware Date: Mon 2018-08-20 To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/2059738/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059968] Re: Produce kernel snaps for linux-nvidia-tegra-igx
** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) ** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Noah Wager (nwager) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059968] [NEW] Produce kernel snaps for linux-nvidia-tegra-igx
Public bug reported: We plan on producing Ubuntu Core images with the linux-nvidia-tegra-igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. ** Affects: linux-meta-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Affects: linux-signed-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Noah Wager (nwager) Status: Fix Committed ** Also affects: linux-meta-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-signed-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-meta-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: New => Fix Committed ** Changed in: linux-signed-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2059968 Title: Produce kernel snaps for linux-nvidia-tegra-igx Status in linux-meta-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Status in linux-signed-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: We plan on producing Ubuntu Core images with the linux-nvidia-tegra- igx kernel. To support this, add support for producing kernel snaps to our kernel source packaging. This requires changes to linux-meta-nvidia-tegra-igx, linux-signed-nvidia-tegra-igx, and linux-nvidia-tegra-igx-modules-signed, which include: * Adding uc meta packages for the -rt and non-rt kernel flavours. * Generating signed kernel.efi images. * Adding ubuntu-core-initramfs config to include modules unique to Tegra platforms. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-tegra-igx/+bug/2059968/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2059958] [NEW] Include networking drivers used on Tegra platforms in initrd.img
Public bug reported: A race occurs between the probing of network devices and systemd- networkd detecting network devices to enable. This can be avoided by loading networking drivers earlier in the boot process, which we accomplish by including them in the initramfs. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Also affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx-modules-signed in Ubuntu. https://bugs.launchpad.net/bugs/2059958 Title: Include networking drivers used on Tegra platforms in initrd.img Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: A race occurs between the probing of network devices and systemd- networkd detecting network devices to enable. This can be avoided by loading networking drivers earlier in the boot process, which we accomplish by including them in the initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2059958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2055468] Re: apply nvidia-tegra patches 2024 Feb 6-29
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2055468 Title: apply nvidia-tegra patches 2024 Feb 6-29 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2055468/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056486] Re: apply nvidia-tegra patches 2024 Mar 1-7
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056486 Title: apply nvidia-tegra patches 2024 Mar 1-7 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2056594] Re: apply nvidia-tegra patches 2024 Mar 8
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2056594 Title: apply nvidia-tegra patches 2024 Mar 8 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2056594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2058550] Re: apply nvidia-tegra patches 2024 Mar 9-20
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2058550 Title: apply nvidia-tegra patches 2024 Mar 9-20 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2058550/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054483] Re: Add headers package for IGX out-of-tree modules
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Released Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2054483] [NEW] Add headers package for IGX out-of-tree modules
Public bug reported: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Assignee: Jacob Martin (jacobmartin) Status: Fix Committed ** Also affects: linux-nvidia-tegra-igx-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx-modules (Ubuntu) Status: New => Fix Committed ** Also affects: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx-modules (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) ** Changed in: linux-nvidia-tegra-igx-modules-signed (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2054483 Title: Add headers package for IGX out-of-tree modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx-modules-signed package in Ubuntu: Fix Committed Bug description: [Impact] The out-of-tree kernel modules include headers that are needed to properly support CUDA RDMA and likely other applications. These need to be packaged for use with Ubuntu kernel builds. [Fix] Add packaging to provide the described headers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2054483/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2052479] Re: apply nvidia-tegra patches 2024 Jan 16-Feb 5
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2052479 Title: apply nvidia-tegra patches 2024 Jan 16-Feb 5 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra and linux-nvida-tegra-igx. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2052479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2051942] Re: autopkgtest fails: EE Missing modules
Prior to version 5.15.0-1008.8, the Tegra out-of-tree modules were built as part of the main kernel build. This caused the module ABI check to fail when the out-of-tree modules were not built in the case where the DKMS package containing these modules is missing. As of version 5.15.0-1008.8, the out-of-tree modules are built in a separate source package (linux-nvidia-tegra-igx-modules), so the main package build should no longer fail if the out-of-tree modules are not available. 5.15.0-1008.8 is in -updates, so I will mark this as fix released. ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Status: New => Fix Released ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Assignee: (unassigned) => Jacob Martin (jacobmartin) ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Assignee: (unassigned) => Jacob Martin (jacobmartin) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2051942 Title: autopkgtest fails: EE Missing modules Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx source package in Jammy: Fix Released Bug description: From https://objectstorage.prodstack5.canonical.com/swift/v1/AUTH_0f9aae918d5b4744bf7b827671c86842/autopkgtest- jammy/jammy/arm64/l/linux-nvidia-tegra- igx/20240121_072109_094a7@/log.gz : 6243s dpkg-deb: building package 'linux-nvidia-tegra-igx-tools-5.15.0-1007' in '../linux-nvidia-tegra-igx-tools-5.15.0-1007_5.15.0-1007.7_arm64.deb'. 6253s Debug: module-check-nvidia-tegra-igx 6253s debian/scripts/module-check "nvidia-tegra-igx" \ 6253s "/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/abi/arm64" "/tmp/autopkgtest.MfAsoT/build.Xbz/src/debian.nvidia-tegra-igx/__abi.current/arm64" 6254s II: Checking modules for nvidia-tegra-igx... 6254s read 11 modules. 6254sreading new modules...read 7343 modules. 6254sreading old modules... 6254s MISS: ar1335_common 6254s MISS: arm64-ras 6254s MISS: bluedroid_pm 6254s MISS: bmi088 6254s MISS: cam_cdi_tsc [...] 6254s MISS: tegracam_log 6254s MISS: ti_fpdlink_dp_serializer 6254s MISS: tsecriscv 6254s MISS: ufs-tegra 6254s MISS: ufs-tegra-provision 6254s MISS: userspace_ivc_mempool 6254s MISS: virtual_i2c_mux 6254s MISS: watchdog-tegra-t18x 6254s MISS: wch 6254s NEW: pps-ktimer 6254s read 7498 modules : new(1) missing(154) 6254s EE: Missing modules 6254s make: *** [debian/rules.d/4-checks.mk:10: module-check-nvidia-tegra-igx] Error 1 6254s dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit status 2 6254s autopkgtest [07:05:29]: test rebuild: ---] 6259s autopkgtest [07:05:34]: test rebuild: - - - - - - - - - - results - - - - - - - - - - 6259s rebuild FAIL non-zero exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2051942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047712] Re: FS disconnects on WD PC SN810 SDCPNRZ HP FW
Hello,
After some additional investigation it seems more to some kind of problem with
Standby mode.
I checked this discussion and tried the AMD S2IDLE analysis script to debug
ACPI standby.
https://discussion.fedoraproject.org/t/please-improve-the-s0ix-experience-under-linux/79113/2
But no new info found.
As next step I will try to install other SSD from Kingston to check if
this is Disk or System error.
For now I configured system to use Hibernation instead to Standby (only
available is s2idle).
I followed this Discussion to enable Hibernation in System menu:
https://askubuntu.com/questions/1405990/hibernate-entry-in-the-menu-on-22-04
m
--
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/2047712
Title:
FS disconnects on WD PC SN810 SDCPNRZ HP FW
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly
disconnects and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to
Firmware bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via
apt package manager), this is reason why I cannot provide "ubuntu-bug
linux" output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original 2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WD PC SN810 SDCPNRZ-2T00-1006
Serial Number:
Firmware Version: HPS2
PCI Vendor/Subsystem ID:0x15b7
IEEE OUI Identifier:0x001b44
Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2 048 408 248 320 [2,04 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
Local Time is: Fri Dec 29 21:04:43 2023 CET
Firmware Updates (0x14):2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
[Kernel-packages] [Bug 2036672] Re: apply nvidia igx patches for Aug 29 - Sep 19
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2036672 Title: apply nvidia igx patches for Aug 29 - Sep 19 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx source package in Jammy: Fix Released Bug description: Patches to apply on top of the new 1004.4 tag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2036672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037760] Re: Create modprobe configuration for the IGX kernel
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2037760 Title: Create modprobe configuration for the IGX kernel Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx source package in Jammy: Fix Released Bug description: Blacklist the following modules, which are replaced by out-of-tree modules: blacklist tegradisp_nvkms blacklist tegradisp_rm blacklist snd_soc_tegra186_asrc blacklist snd_soc_tegra186_dspk blacklist snd_soc_tegra210_admaif blacklist snd_soc_tegra210_adx blacklist snd_soc_tegra210_ahub blacklist snd_soc_tegra210_amx blacklist snd_soc_tegra210_dmic blacklist snd_soc_tegra210_i2s blacklist snd_soc_tegra210_mixer blacklist snd_soc_tegra210_mvc blacklist snd_soc_tegra210_ope blacklist snd_soc_tegra210_sfc blacklist snd_soc_tegra_audio_graph_card blacklist tegra-safety blacklist dwmac_tegra blacklist host1x blacklist tegra-drm RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use them: options nvidia NVreg_OpenRmEnableUnsupportedGpus=1 Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's /lib/modprobe.d config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2037760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038953] Re: Split iGPU out-of-tree modules into a separate binary package
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038953 Title: Split iGPU out-of-tree modules into a separate binary package Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx source package in Jammy: Fix Released Bug description: Create packages linux-modules-tegra-igpu-igx-nvidia-tegra-igx and linux-modules-tegra-igpu-igx-PKGVER-ABINUM-nvidia-tegra-igx so that iGPU modules can be easily swapped out for dGPU modules. This is required because the IGX iGPU and NVIDIA dGPU display modules cannot currently coexist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049536] Re: apply nvidia-tegra patches 2024 Jan 1-15
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2049536 Title: apply nvidia-tegra patches 2024 Jan 1-15 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2049536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038165] Re: apply nvidia igx patches for Sep 20-29
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038165 Title: apply nvidia igx patches for Sep 20-29 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Status in linux-nvidia-tegra-igx source package in Jammy: Fix Released Bug description: Most of these patches relate to simpledrm support. Notably I am NOT sending the config change that enables simpledrm. That is expected to happen in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
** Tags added: jammy regression-release
** Tags removed: regression-release
** Tags added: regression-update
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe on empty loopback
device
Status in linux package in Ubuntu:
New
Status in linux-signed package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-signed source package in Jammy:
New
Bug description:
This is with the kernel from jammy-proposed (linux-
image-5.15.0-94-generic 5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Also affects: linux-signed (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/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe on empty loopback
device
Status in linux package in Ubuntu:
New
Status in linux-signed package in Ubuntu:
New
Status in linux source package in Jammy:
New
Status in linux-signed source package in Jammy:
New
Bug description:
This is with the kernel from jammy-proposed (linux-
image-5.15.0-94-generic 5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049689] Re: linux-image-5.15.0-94-generic breaks partprobe on empty loopback device
** 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/2049689
Title:
linux-image-5.15.0-94-generic breaks partprobe on empty loopback
device
Status in linux package in Ubuntu:
New
Status in linux-signed package in Ubuntu:
New
Bug description:
This is with the kernel from jammy-proposed (linux-
image-5.15.0-94-generic 5.15.0-94.104).
Do this:
# dd if=/dev/zero of=/tmp/file bs=1M count=50
# partprobe "$(losetup --show --find /tmp/file)"
Notice this very odd error message:
Error: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15,
16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32,
33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49,
50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64 on
/dev/loop2 have been written, but we have been unable to inform the
kernel of the change, probably because it/they are in use. As a
result, the old partition(s) will remain in use. You should reboot
now before making further changes.
That's a result of an ioctl changing its error code in an incompatible
way between kernel versions 5.15.0.91.88 and 5.15.0.94.91, confusing
partprobe.
5.15.0.91.88:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 ENXIO (No such device or
address)
5.15.0.94.91:
ioctl(3, BLKPG, {op=BLKPG_DEL_PARTITION, flags=0, datalen=152, data={start=0,
length=0, pno=1, devname="", volname=""}}) = -1 EINVAL (Invalid argument)
This is a userspace API break which impacts GNU parted and util-linux
(as confirmed by the util-linux maintainer).
This issue was discovered as part of Cockpit CI here:
https://github.com/cockpit-project/bots/pull/5793
This issue is being discussed on LKML here (with a patch likely to
land soon): https://lkml.org/lkml/2024/1/15/147
lsb_release -rd:
Description: Ubuntu 22.04.3 LTS
Release: 22.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2049689/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049536] Re: apply nvidia-tegra patches 2024 Jan 1-15
** Also affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2049536 Title: apply nvidia-tegra patches 2024 Jan 1-15 Status in linux-nvidia-tegra package in Ubuntu: New Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Apply patches to linux-nvidia-tegra (for use in both linux-nvidia- tegra and linux-nvida-tegra-igx). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2049536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047712] Re: FS disconnects on WD PC SN810 SDCPNRZ HP FW
Hello,
I tried some additional tasks.
Added remote- logging to other device to be able catch error.
Below is what I found.
In meantime I tried Mainline kernel 6.7.0 but still same error.
Then I tried add other Quirk (NVME_QUIRK_DELAY_BEFORE_CHK_RDY) for this disk in
"linux/drivers/nvme/host/pci.c".
But after kernel recompile and install I receive still same error.
And also I tried same kernel parameters as was recommended in error message.
After some time of work I received same error.
Can I ask for some help or recommendation please?
This is what I found in logs:
Jan 14 14:17:09 marvin kernel: [52934.215144] nvme nvme0: controller is down;
will reset: CSTS=0x, PCI_STATUS=0x10
Jan 14 14:17:09 marvin kernel: [52934.215157] nvme nvme0: Does your device have
a faulty power saving mode enabled?
Jan 14 14:17:09 marvin kernel: [52934.215162] nvme nvme0: Try
"nvme_core.default_ps_max_latency_us=0 pcie_aspm=off" and report a bug
Jan 14 14:17:09 marvin kernel: [52934.315175] nvme :02:00.0: enabling
device ( -> 0002)
Jan 14 14:17:09 marvin kernel: [52934.315562] nvme nvme0: Disabling device
after reset failure: -19
Jan 14 14:17:09 marvin kernel: [52934.356714] EXT4-fs (nvme0n1p2): shut down
requested (2)
Jan 14 14:17:09 marvin kernel: [52934.356718] Aborting journal on device
nvme0n1p2-8.
Jan 14 14:17:09 marvin kernel: [52934.356722] JBD2: I/O error when updating
journal superblock for nvme0n1p2-8.
Jan 14 14:17:57 marvin udisksd[1948]: Error performing housekeeping for drive
/org/freedesktop/UDisks2/drives/WD_PC_SN810_SDCPNRZ_2T00_1006_23306V800421:
Error updating Health Information: Failed to open device '/dev/nvme0': Resource
temporarily unavailable (g-bd-nvme-error-quark, 2)
Thanks
--
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/2047712
Title:
FS disconnects on WD PC SN810 SDCPNRZ HP FW
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly
disconnects and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to
Firmware bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via
apt package manager), this is reason why I cannot provide "ubuntu-bug
linux" output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original 2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF
[Kernel-packages] [Bug 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1
** Tags added: verification-testing-passed ** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota Apply pull request from NVIDIA received on 2023-11-27 EJ Hsu (1): NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux Register Linus Walleij (1): Revert "pinctrl: tegra: Add support to display pin function" Penny Chiu (3): NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig NVIDIA: SAUCE: arm64: configs: Enable NFS server support NVIDIA: SAUCE: arm64: configs: Enable dm_multipath driver Thierry Reding (1): pinctrl: tegra: Display pin function in pinconf-groups Vince Hsu (1): NVIDIA: SAUCE: arm64: configs: enable few matches for netfliter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2042935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2045080] Re: apply nvidia igx patches for Oct 19 - Nov 28 2023
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Tags added: verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2045080 Title: apply nvidia igx patches for Oct 19 - Nov 28 2023 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Patches for IGX. These are intended for releases that come after the r36.2 DP release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2045080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2046011] Re: apply nvidia igx patches for Nov 29 - Dec 8 2023
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Tags added: verification-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2046011 Title: apply nvidia igx patches for Nov 29 - Dec 8 2023 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Additional patches for IGX kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2046011/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2047712] Re: FS disconnects on WD PC SN810 SDCPNRZ HP FW
Hello,
5 minutes after I submitted this bug FS was disconnected again.
Therefore it seems that the issue was not solved.
When I tried to check status of disk, there was no response from nvme
controller.
Tried smartclt and nvme tool.
--
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/2047712
Title:
FS disconnects on WD PC SN810 SDCPNRZ HP FW
Status in linux package in Ubuntu:
New
Bug description:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly
disconnects and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to
Firmware bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via
apt package manager), this is reason why I cannot provide "ubuntu-bug
linux" output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original 2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description: Ubuntu 23.10
Release: 23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WD PC SN810 SDCPNRZ-2T00-1006
Serial Number:
Firmware Version: HPS2
PCI Vendor/Subsystem ID:0x15b7
IEEE OUI Identifier:0x001b44
Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2 048 408 248 320 [2,04 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
Local Time is: Fri Dec 29 21:04:43 2023 CET
Firmware Updates (0x14):2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02):NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.25W8.25W -0 0 0 00 0
1 + 3.50W3.50W -0 0 0 00 0
2 + 2.60W2.60W -0 0 0 00
[Kernel-packages] [Bug 2047712] [NEW] FS disconnects on WD PC SN810 SDCPNRZ HP FW
Public bug reported:
Hello,
I bought notebook HP ZBook Firefly 14 G10 A with AMD Ryzen 7 7840HS CPU.
This notebook have nvme SSD WD PC SN810 SDCPNRZ-2T00 with HPS2 firmware.
When I use standard Ubuntu kernel 6.5.0-14-generic, disk regularly disconnects
and FS become ReadOnly.
I found similar issue with eg. Kingston A2000 nvme disk. This seems to Firmware
bug.
I tried same solution and this worked.
As first workaround I tried add kernel parameter
"nvme_core.default_ps_max_latency_us=1".
Behavior was much better, but sometimes disk still disconnects (after connect
disconnect from Thunderbolt docking station or after several sleep/wake cycles)
Second workaround was update kernel source code and setup quirk
"NVME_QUIRK_NO_DEEPEST_PS" for disk identifier. Then I build kernel package and
install it on notebook with Ubuntu 23.10.
After ~4days of usage it seems that this is working solution.
Now I running my own kernel build 6.5.3 (from sources downloaded via apt
package manager), this is reason why I cannot provide "ubuntu-bug linux"
output.
Will be possible to add this solution to the default kernel image please?
I'm not a developer and not sure if this is all you need.
I can provide additional info or testing if will be needed.
--
Updated was file "linux-6.5.0/drivers/nvme/host/pci.c" with following lines:
--- drivers-nvme-host-pci.c.original2023-12-29 20:48:38.048105439 +0100
+++ drivers-nvme-host-pci.c.new 2023-12-29 20:48:38.064104967 +0100
@@ -3399,6 +3399,8 @@
.driver_data = NVME_QUIRK_BOGUS_NID, },
{ PCI_DEVICE(0x15b7, 0x2001), /* Sandisk Skyhawk */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
+ { PCI_DEVICE(0x15b7, 0x5011), /* Sandisk Corp WD PC SN810
SDCPNRZ-2T00 (HPS2 FW) */
+.driver_data = NVME_QUIRK_NO_DEEPEST_PS, },
{ PCI_DEVICE(0x1d97, 0x2263), /* SPCC */
.driver_data = NVME_QUIRK_DISABLE_WRITE_ZEROES, },
{ PCI_DEVICE(0x144d, 0xa80b), /* Samsung PM9B1 256G and 512G */
--
$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu 23.10
Release:23.10
--
$ apt-cache policy linux-image-6.5.0-14-generic
linux-image-6.5.0-14-generic:
Installed: 6.5.0-14.14
Candidate: 6.5.0-14.14
Version table:
*** 6.5.0-14.14 500
500 http://sk.archive.ubuntu.com/ubuntu mantic-updates/main amd64
Packages
500 http://security.ubuntu.com/ubuntu mantic-security/main amd64
Packages
100 /var/lib/dpkg/status
$ apt-cache policy linux-image-6.5.3
linux-image-6.5.3:
Installed: 6.5.3-2
Candidate: 6.5.3-2
Version table:
*** 6.5.3-2 100
100 /var/lib/dpkg/status
--
$ sudo smartctl -ic /dev/nvme0n1
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.5.3] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Number: WD PC SN810 SDCPNRZ-2T00-1006
Serial Number:
Firmware Version: HPS2
PCI Vendor/Subsystem ID:0x15b7
IEEE OUI Identifier:0x001b44
Total NVM Capacity: 2 048 408 248 320 [2,04 TB]
Unallocated NVM Capacity: 0
Controller ID: 8224
NVMe Version: 1.4
Number of Namespaces: 1
Namespace 1 Size/Capacity: 2 048 408 248 320 [2,04 TB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64:001b44 8b4a02b37b
Local Time is: Fri Dec 29 21:04:43 2023 CET
Firmware Updates (0x14):2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat
Timestmp
Log Page Attributes (0x1e): Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg Pers_Ev_Lg
Maximum Data Transfer Size: 128 Pages
Warning Comp. Temp. Threshold: 84 Celsius
Critical Comp. Temp. Threshold: 88 Celsius
Namespace 1 Features (0x02):NA_Fields
Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 8.25W8.25W -0 0 0 00 0
1 + 3.50W3.50W -0 0 0 00 0
2 + 2.60W2.60W -0 0 0 00 0
3 - 0.0250W --3 3 3 3 5000 1
4 - 0.0035W --4 4 4 4 3900 45700
Supported LBA Sizes (NSID 0x1)
Id Fmt Data Metadt Rel_Perf
0 + 512 0 2
1 -4096 0 1
--
Thanks
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "OS Report and diff file from my patch."
https://bugs.launchpad.net/bugs/2047712/+attachment/5734736/+files/report-and-patch.zip
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
[Kernel-packages] [Bug 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1
** Summary changed: - NVIDIA pull request 1018-002v1, 1018-003v1 + NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 ** Description changed: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): - NVIDIA: SAUCE: arm64: configs: disable LOGO + NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): - NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY + NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): - NVIDIA: SAUCE: aquantia: issue PHY reset during phy init + NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): - NVIDIA: SAUCE: arm64: config: Disable DMI config + NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): - NVIDIA: SAUCE: configs: defconfig: enable TPM configs + NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): - NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota + NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota + + Apply pull request from NVIDIA received on 2023-11-27 + + EJ Hsu (1): + NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux Register + + Linus Walleij (1): + Revert "pinctrl: tegra: Add support to display pin function" + + Penny Chiu (3): + NVIDIA: SAUCE: arm64: configs: Sanitize arm64 defconfig + NVIDIA: SAUCE: arm64: configs: Enable NFS server support + NVIDIA: SAUCE: arm64: configs: Enable dm_multipath driver + + Thierry Reding (1): + pinctrl: tegra: Display pin function in pinconf-groups + + Vince Hsu (1): + NVIDIA: SAUCE: arm64: configs: enable few matches for netfliter + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1, 1018-003v1, 1018-004v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota Apply pull request from NVIDIA received on 2023-11-27 EJ Hsu (1): NVIDIA: SAUCE: pinctrl: tegra: Set SFIO mode to Mux
[Kernel-packages] [Bug 2039603] Re: NVIDIA pull requests 1018-001v1
** Changed in: linux-nvidia-tegra (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2039603 Title: NVIDIA pull requests 1018-001v1 Status in linux-nvidia-tegra package in Ubuntu: Fix Released Bug description: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2039603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042935] Re: NVIDIA pull request 1018-002v1, 1018-003v1
** Summary changed: - NVIDIA pull request 1018-002v1 + NVIDIA pull request 1018-002v1, 1018-003v1 ** Description changed: Apply pull requests from NVIDIA received on 2023-11-02. - Ankur Pawar (1): - NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 + NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): - usb: typec: ucsi: don't print PPM init deferred errors + usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): - NVIDIA: SAUCE: arm64: configs: enable NTFS fs + NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): - NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control + NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): - NVIDIA: SAUCE: Remove support for summation channel control + NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): - NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable + NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): - NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver + NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): - mmc: sdhci-tegra: Add runtime PM and OPP support + mmc: sdhci-tegra: Add runtime PM and OPP support + + Apply pull requests from NVIDIA received on 2023-11-13 + + Gautham Srinivasan (1): + NVIDIA: SAUCE: arm64: configs: disable LOGO + + Laxman Dewangan (1): + NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY + + Narayan Reddy (1): + NVIDIA: SAUCE: aquantia: issue PHY reset during phy init + + Sandipan Patra (1): + NVIDIA: SAUCE: arm64: config: Disable DMI config + + Shubhi Garg (1): + NVIDIA: SAUCE: configs: defconfig: enable TPM configs + + Vince Hsu (1): + NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota + -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1, 1018-003v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support Apply pull requests from NVIDIA received on 2023-11-13 Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: disable LOGO Laxman Dewangan (1): NVIDIA: SAUCE: platform: tegra: Add new config TEGRA_PROD_LEGACY Narayan Reddy (1): NVIDIA: SAUCE: aquantia: issue PHY reset during phy init Sandipan Patra (1): NVIDIA: SAUCE: arm64: config: Disable DMI config Shubhi Garg (1): NVIDIA: SAUCE: configs: defconfig: enable TPM configs Vince Hsu (1): NVIDIA: SAUCE: arm: configs: enable QFMT_V2 for quota To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2042935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
I also have same problem on Lenovo Yoga Duet 7 13IML05 model 82AS , Intel Core i7-10510U -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.5 in Ubuntu. https://bugs.launchpad.net/bugs/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop Status in ideapad-laptop: New Status in Linux: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux-oem-6.5 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Confirmed Status in linux-oem-6.5 source package in Jammy: Confirmed Status in linux source package in Lunar: Confirmed Status in linux source package in Mantic: Confirmed Status in linux source package in Noble: Confirmed Status in Fedora: New Bug description: [Impact] Keyboard and touchpad doesn't work on some recent systems, and also s2idle is broken. [Fix] Two upstream commits. 128b0c9781c9f26 x86/i8259: Skip probing when ACPI/MADT advertises PCAT compatibility 3bde7ec13c97144 platform/x86: Add s2idle quirk for more Lenovo laptops [Test case] boot a fixed kernel and test that input and s2idle works. [Where problems could occur] A buggy bios could maybe advertise a system being PCAT compatible when it's not, though in such a case it might have been already caught before. -- Hello. Ubuntu 22.04.3 with (later upgraded to kernel 6.2.0-32-generic) was installed in rewly purchased LENOVO V15 GEN4 AMN (AMD Ryzen 5 7520u) laptop and it was noticed that keyboard, touchpad and microphone are not working. The keyboard and touchpad work fine in BIOS setup and till GRUB (command line). It was found that when external devices such as keyboard, mouse and microphone are connected through USB and 3.5 jack, respectively, these work just fine. To confirm these are not hardware problems, Microsoft Windows 11 (Home) was installed in another disk partition and observed all these working alright. Hence a bug is being reported to draw attention of the concerned team and I request them to refer this issue and do the needful at the earliest. Regards, Pradip Kumar Das ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-32-generic 6.2.0-32.32~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-32.32~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 08:04:42 2023 InstallationDate: Installed on 2023-08-14 (22 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash SourcePackage: linux-signed-hwe-6.2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039603] Re: NVIDIA pull requests 1018-001v1
** Changed in: linux-nvidia-tegra (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2039603 Title: NVIDIA pull requests 1018-001v1 Status in linux-nvidia-tegra package in Ubuntu: Fix Committed Bug description: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2039603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2042935] [NEW] NVIDIA pull request 1018-002v1
Public bug reported: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2042935 Title: NVIDIA pull request 1018-002v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply pull requests from NVIDIA received on 2023-11-02. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable NTFS fs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control Jon Hunter (1): NVIDIA: SAUCE: Remove support for summation channel control Ninad Malwade (1): NVIDIA: SAUCE: hwmon: ina3221: Add support for channel summation disable Revanth Kumar Uppala (1): NVIDIA: SAUCE: arm64: config: Enable BRCMFMAC driver Ulf Hansson (1): mmc: sdhci-tegra: Add runtime PM and OPP support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2042935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We can confirm that this bug is no longer an issue with 5.4.0-166 being deployed on all our servers. We consider this bug solved. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Fix Released Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We see that that vmlinuz-5.4.0-166-generic was deplyed as an automatic update a few hours ago, hopefully this resolves the problem :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
-- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
How do I go about getting this upgrade if I had installed the version from Mario's ppa? I have proposed activated in sources.list and have removed the ppa. But sudo apt update && sudo apt upgrade does not show the new packages. Shall I revert from Mario's version? -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Any news on this issue? Is it on time to launch the fix at about 30th of october? -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Can confirm that the fixes work. I added Mario's ppa, upgraded and removed the line from /etc/environment. Would be nice if it was fixed in the official Ubuntu repository. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Committed Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039730] Re: apply nvidia igx patches for Sep 30 - Oct 18
** Description changed: Need to update the latest kernel patches for IGX. There are 4 new patches. + + + Ankur Pawar (1): + NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 + + Fabrice Gasnier (1): + usb: typec: ucsi: don't print PPM init deferred errors + + Gautham Srinivasan (1): + NVIDIA: SAUCE: arm64: configs: enable cifs + + Jim Lin (1): + NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2039730 Title: apply nvidia igx patches for Sep 30 - Oct 18 Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Need to update the latest kernel patches for IGX. There are 4 new patches. Ankur Pawar (1): NVIDIA: SAUCE: memory: tegra: Add client for RCE in Tegra234 Fabrice Gasnier (1): usb: typec: ucsi: don't print PPM init deferred errors Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Jim Lin (1): NVIDIA: SAUCE: phy: xusb-tegra186: No redundant pad control To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2039730/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039603] [NEW] NVIDIA pull requests 1018-001v1
Public bug reported: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- ** Affects: linux-nvidia-tegra (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2039603 Title: NVIDIA pull requests 1018-001v1 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-10-13 to jammy:linux-nvidia-tegra. - 1018-001-v1 - Akhil R (1): NVIDIA: SAUCE: crypto: tegra: Add Kconfig to support Tegra SE Ashish Mhetre (1): NVIDIA: SAUCE: memory: tegra: Fix SID override Daniel Vetter (1): drm/vgem: use shmem helpers Gautham Srinivasan (1): NVIDIA: SAUCE: arm64: configs: enable cifs Hector Martin (1): of: Move simple-framebuffer device handling from simplefb to of Johnny Liu (2): NVIDIA: SAUCE: memory: tegra: Add bpmp_id and type for nvdla NVIDIA: SAUCE: memory: tegra: Add clients for VI in Tegra234 Jon Hunter (1): NVIDIA: SAUCE: dma-buf-map: Fix-up iosys-map integration Kartik (2): NVIDIA: SAUCE: mailbox: tegra-hsp: Add support for virtualization NVIDIA: SAUCE: fs: eventpoll: Add smp_mb() before waitqueue_active Lucas De Marchi (3): dma-buf-map: Rename to iosys-map iosys-map: Add offset to iosys_map_memcpy_to() iosys-map: Add a few more helpers Mikko Perttunen (1): NVIDIA: SAUCE: thermal: tegra-bpmp: Check if BPMP supports trip points Prathamesh Shete (1): NVIDIA: SAUCE: mmc: host: Apply post auto-tuning correction Santosh Reddy Galma (1): NVIDIA: SAUCE: simplefb: add support to parse fb-memory from DT Shunsuke Mie (1): dma-buf: Update obsoluted comments on dma_buf_vmap/vunmap() vinothkumarr (1): NVIDIA: SAUCE: mtd: spi-nor: support for GD --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2039603/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034622] Re: NVIDIA pull requests 1017-001v3
** Tags added: verification-done-jammy-linux-nvidia-tegra -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2034622 Title: NVIDIA pull requests 1017-001v3 Status in linux-nvidia-tegra package in Ubuntu: New Bug description: Apply patches from NVIDIA pull request sent on 2023-09-04 to jammy:linux-nvidia-tegra. 1017-001 V3 (2023-09-14): Akhil R (1): NVIDIA: SAUCE: Revert "i2c: tegra: Allocate DMA memory for DMA engine" Andy Sobczyk (1): NVIDIA: SAUCE: arm64: config: Enable MTD_UBI Ashish Mhetre (2): NVIDIA: SAUCE: iommu: Don't reserve IOVA when address and size are zero NVIDIA: SAUCE: memory: tegra: Add SID override on resume Kartik (1): NVIDIA: SAUCE: mailbox: tegra-hsp: Add sm ops route_irq & set_irq Laxman Dewangan (2): NVIDIA: SAUCE: config: Disable CONFIG_LOCALVERSION_AUTO NVIDIA: SAUCE: arm64: config: recovery_chain: Enable KEXEC configs Mikko Perttunen (2): thermal: tegra-bpmp: Handle errors in BPMP response thermal/drivers/tegra-bpmp: Handle offline zones Mohan Kumar (1): NVIDIA: SAUCE: arch: arm64: enable HDA_INTEL config Parker Newman (1): i2c: tegra: Fix i2c-tegra DMA config option processing Penny Chiu (1): NVIDIA: SAUCE: arm64: configs: Enable BINFMT_MISC support Sumit Gupta (2): NVIDIA: SAUCE: driver: cpufreq: remove volatile as not needed cpufreq: tegra194: add online/offline hooks Vishwaroop A (1): NVIDIA: SAUCE: spi: spi-tegra114: retain the spi mode raju patel (1): NVIDIA: SAUCE: code-owners: Populate OWNERS file zuyih (1): NVIDIA: SAUCE: s25fs: Add post-get-map-id fixup for S25FS512S --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra/+bug/2034622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
After having run tests for two days, it seems likely to us that the bug is currently not in 166 from -proposed. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We have now done close to 6000 runs over the last 24 hours, and 166 from -proposed does not seem to have this problem! Does this mean this is the same bug? When can we expect this to be rolled out? It will be a real relief for us when this bug does not affect our production servers any more. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
> Probably the version installed was 5.4.0-162. Yes, you are probably right. I was only looking at the date of the kernel file. The bug is reproducible with Linux 5.4.0-164.181, however. > I checked some discussions from here https://gitlab.com/qemu- project/qemu/-/issues/1696 and it seems it's similar. I have discusses the problem with Richard Jones here: https://bugzilla.redhat.com/show_bug.cgi?id=2241293 He claims the issue in this bug report is not the same bug as you refer to. Se his last comment. ** Bug watch added: Red Hat Bugzilla #2241293 https://bugzilla.redhat.com/show_bug.cgi?id=2241293 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We have live updates with unattended updates. Our first recording of this problem is Sept. 5th, so this points towards Linux 5.4.0-164.181 being the culprit unless you updated this package just a few days before. Linux 5.4.0-164.181 was installed on our systems Sept 1st, and this has been a problem ever since. We do thousands of runs each day, so if this bug had occurred earlier, we would have noticed. -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
This is a successfull boot of qemu. ** Attachment added: "log89" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709154/+files/log89 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
This is a failing boot of qemu that we killed after some time. ** Attachment added: "log90" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+attachment/5709155/+files/log90 -- 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709152/+files/acpidump.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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
We managed to reproduce the failure on a fresh install of Ubuntu 20.04
using this script. It occurred already on the 90th iteration.
---
for i in {1..1}
do
echo Run $i
guestfish -vx -a /dev/null run >& log$i
done
---
Here is what we did after booting a fresh install
apt update
apt upgrade
apt install qemu-system-x86
apt install libguestfs-tools
(rebooted the server and ran the script above)
--
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/2039258
Title:
qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Status in linux package in Ubuntu:
Confirmed
Bug description:
We have a number of Ubuntu 20.04 servers that have recently been
upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27.
About 1/1000 boots of qemu results in a failed boot hanging at 100%
CPU indefinately. A number of our utilities are using qemu for
processing, so we get a lot of processes spinning at 100% that we need
to clean up regularly.
Ubuntu: 20.04
Linux: 5.4.0-164.181
Qemu: 4.2-3ubuntu6.27
This problem was not seen before the release of Linux. 5.4.0-164.181
on sept. 1.
What you expected to happen: Qemu boots linux reliably.
What happened instead: Qemu hangs at 100% indefinately.
---
ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k5.4.0-164-generic.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
ApportVersion: 2.20.11-0ubuntu27.27
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c',
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
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: skip
DistroRelease: Ubuntu 20.04
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
/: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
|__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
Package: linux (not installed)
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic
root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0
netcfg/do_not_use_netplan=true
ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
RelatedPackageVersions:
linux-restricted-modules-5.4.0-164-generic N/A
linux-backports-modules-5.4.0-164-generic N/A
linux-firmware 1.187.39
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
Tags: focal
Uname: Linux 5.4.0-164-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: True
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: 1.13.0-1ubuntu1.1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-4.2
dmi.modalias:
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-4.2
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709151/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709150/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709147/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709148/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709149/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709143/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709145/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709146/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709144/+files/PciMultimedia.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709142/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709140/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709139/+files/Card0.Codecs.codec.0.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709141/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709138/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 RelatedPackageVersions: linux-restricted-modules-5.4.0-164-generic N/A linux-backports-modules-5.4.0-164-generic N/A linux-firmware 1.187.39 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-164-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.13.0-1ubuntu1.1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2039258] Re: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
apport information ** Tags added: apport-collected focal ** Description changed: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. + --- + ProblemType: Bug + AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. + AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' + ApportVersion: 2.20.11-0ubuntu27.27 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + 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: skip + DistroRelease: Ubuntu 20.04 + IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' + Lsusb: + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Lsusb-t: + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + MachineType: QEMU Standard PC (i440FX + PIIX, 1996) + Package: linux (not installed) + ProcFB: 0 cirrusdrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic root=UUID=ed61e67e-7605-4383-ac16-fe54ee2ede87 ro net.ifnames=0 biosdevname=0 netcfg/do_not_use_netplan=true + ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-164-generic N/A + linux-backports-modules-5.4.0-164-generic N/A + linux-firmware 1.187.39 + RfKill: Error: [Errno 2] No such file or directory: 'rfkill' + Tags: focal + Uname: Linux 5.4.0-164-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: N/A + _MarkForUpload: True + dmi.bios.date: 04/01/2014 + dmi.bios.vendor: SeaBIOS + dmi.bios.version: 1.13.0-1ubuntu1.1 + dmi.chassis.type: 1 + dmi.chassis.vendor: QEMU + dmi.chassis.version: pc-i440fx-4.2 + dmi.modalias: dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.2:cvnQEMU:ct1:cvrpc-i440fx-4.2: + dmi.product.name: Standard PC (i440FX + PIIX, 1996) + dmi.product.version: pc-i440fx-4.2 + dmi.sys.vendor: QEMU ** Attachment added: "AlsaDevices.txt" https://bugs.launchpad.net/bugs/2039258/+attachment/5709137/+files/AlsaDevices.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: Confirmed Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-164-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: 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: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus
[Kernel-packages] [Bug 2039258] [NEW] qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181
Public bug reported: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. ** 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/2039258 Title: qemu 4.2-3ubuntu6.27 Does Not Boot Reliably Into Linux 5.4.0-164.181 Status in linux package in Ubuntu: New Bug description: We have a number of Ubuntu 20.04 servers that have recently been upgraded to linux 5.4.0-164.181 and qemu 4.2-3ubuntu6.27. About 1/1000 boots of qemu results in a failed boot hanging at 100% CPU indefinately. A number of our utilities are using qemu for processing, so we get a lot of processes spinning at 100% that we need to clean up regularly. Ubuntu: 20.04 Linux: 5.4.0-164.181 Qemu: 4.2-3ubuntu6.27 This problem was not seen before the release of Linux. 5.4.0-164.181 on sept. 1. What you expected to happen: Qemu boots linux reliably. What happened instead: Qemu hangs at 100% indefinately. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039258/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037760] Re: Create modprobe configuration for the IGX kernel
** Also affects: linux-nvidia-tegra-igx (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2037760 Title: Create modprobe configuration for the IGX kernel Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Blacklist the following modules, which are replaced by out-of-tree modules: blacklist tegradisp_nvkms blacklist tegradisp_rm blacklist snd_soc_tegra186_asrc blacklist snd_soc_tegra186_dspk blacklist snd_soc_tegra210_admaif blacklist snd_soc_tegra210_adx blacklist snd_soc_tegra210_ahub blacklist snd_soc_tegra210_amx blacklist snd_soc_tegra210_dmic blacklist snd_soc_tegra210_i2s blacklist snd_soc_tegra210_mixer blacklist snd_soc_tegra210_mvc blacklist snd_soc_tegra210_ope blacklist snd_soc_tegra210_sfc blacklist snd_soc_tegra_audio_graph_card blacklist tegra-safety blacklist dwmac_tegra blacklist host1x blacklist tegra-drm RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use them: options nvidia NVreg_OpenRmEnableUnsupportedGpus=1 Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's /lib/modprobe.d config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2037760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036672] Re: apply nvidia igx patches for Aug 29 - Sep 19
** Also affects: linux-nvidia-tegra-igx (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2036672 Title: apply nvidia igx patches for Aug 29 - Sep 19 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Patches to apply on top of the new 1004.4 tag. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2036672/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038165] Re: apply nvidia igx patches for Sep 20-29
** Also affects: linux-nvidia-tegra-igx (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038165 Title: apply nvidia igx patches for Sep 20-29 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Most of these patches relate to simpledrm support. Notably I am NOT sending the config change that enables simpledrm. That is expected to happen in the future. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038953] Re: Split iGPU out-of-tree modules into a separate binary package
** Also affects: linux-nvidia-tegra-igx (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed ** Changed in: linux-nvidia-tegra-igx (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038953 Title: Split iGPU out-of-tree modules into a separate binary package Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Status in linux-nvidia-tegra-igx source package in Jammy: Fix Committed Bug description: Create packages linux-modules-tegra-igpu-igx-nvidia-tegra-igx and linux-modules-tegra-igpu-igx-PKGVER-ABINUM-nvidia-tegra-igx so that iGPU modules can be easily swapped out for dGPU modules. This is required because the IGX iGPU and NVIDIA dGPU display modules cannot currently coexist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2038953] [NEW] Split iGPU out-of-tree modules into a separate binary package
Public bug reported: Create packages linux-modules-tegra-igpu-igx-nvidia-tegra-igx and linux- modules-tegra-igpu-igx-PKGVER-ABINUM-nvidia-tegra-igx so that iGPU modules can be easily swapped out for dGPU modules. This is required because the IGX iGPU and NVIDIA dGPU display modules cannot currently coexist. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2038953 Title: Split iGPU out-of-tree modules into a separate binary package Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Create packages linux-modules-tegra-igpu-igx-nvidia-tegra-igx and linux-modules-tegra-igpu-igx-PKGVER-ABINUM-nvidia-tegra-igx so that iGPU modules can be easily swapped out for dGPU modules. This is required because the IGX iGPU and NVIDIA dGPU display modules cannot currently coexist. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2038953/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Just updated and mutter 45.0-3ubuntu3 does not fix this error. Still crash when lock screen and works with MUTTER_DEBUG_KMS_THREAD_TYPE=user added to /etc/environment -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: New Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Confirmed Status in mutter source package in Mantic: Fix Released Bug description: [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Original Description] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
The process is Intellij IDEA, running on Java 17 in Xwayland. -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [ 422.206597]
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Unfortunately the problem is still reproducible even with the newest mesa, even though it looks like it's much less frequent. Yesterday evening I got another crash, with mesa 23.2.1-1ubuntu2: ``` 2023-10-04T22:33:15.415854+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119146] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415871+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119168] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326e000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415873+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119180] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415874+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119187] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415875+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119194] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415876+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119200] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119206] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415878+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119212] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415879+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119218] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119750] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:4 pasid:32770, for process Xwayland pid 4940 thread Xwayland:cs0 pid 5015) 2023-10-04T22:33:15.415881+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119768] amdgpu :06:00.0: amdgpu: in page starting at address 0xe5ea2326f000 from IH client 0x1b (UTCL2) 2023-10-04T22:33:15.415883+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119780] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00400430 2023-10-04T22:33:15.415884+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119787] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119793] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x0 2023-10-04T22:33:15.415885+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119800] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-10-04T22:33:15.415886+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119806] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-10-04T22:33:15.415887+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119812] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-10-04T22:33:15.415888+03:00 mavi-ThinkPad-T14s kernel: [ 1076.119818] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-10-04T22:33:25.115577+03:00 mavi-ThinkPad-T14s kernel: [ 1085.820288] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=75561, emitted seq=75563 2023-10-04T22:33:25.115600+03:00 mavi-ThinkPad-T14s kernel: [ 1085.821169] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 4940 thread Xwayland:cs0 pid 5015 2023-10-04T22:33:25.115602+03:00 mavi-ThinkPad-T14s kernel: [ 1085.822031] amdgpu :06:00.0: amdgpu: GPU reset begin! 2023-10-04T22:33:25.347547+03:00 mavi-ThinkPad-T14s kernel: [ 1086.052065] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) 2023-10-04T22:33:25.375820+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078048] amdgpu :06:00.0: amdgpu: MODE2 reset 2023-10-04T22:33:25.375835+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078296] amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume 2023-10-04T22:33:25.375837+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078498] [drm] PCIE GART of 1024M enabled. 2023-10-04T22:33:25.375838+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078503] [drm] PTB located at 0x00F43FC0 2023-10-04T22:33:25.375839+03:00 mavi-ThinkPad-T14s kernel: [ 1086.078625] [drm] PSP is resuming... 2023-10-04T22:33:26.075542+03:00 mavi-ThinkPad-T14s kernel: [ 1086.780162] [drm] reserve 0x40 from 0xf43f80 for PSP TMR 2023-10-04T22:33:26.363527+03:00 mavi-ThinkPad-T14s kernel: [ 1087.066834] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available 2023-10-04T22:33:26.375796+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078189] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available 2023-10-04T22:33:26.375806+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078196] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available 2023-10-04T22:33:26.375808+03:00 mavi-ThinkPad-T14s kernel: [ 1087.078204] amdgpu :06:00.0: amdgpu: SMU is resuming... 2023-10-04T22:33:26.375809+03:00 mavi-ThinkPad-T14s kernel: [ 1087.079063] amdgpu :06:00.0: amdgpu: SMU is resumed
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Thanks Mario! I checked, and I have the newest mesa: ``` $ apt search mesa-vdpau Sorting... Done Full Text Search... Done mesa-vdpau-drivers/mantic,now 23.2.1-1ubuntu2 amd64 [installed,automatic] Mesa VDPAU video acceleration drivers ``` Funny thing is that the bug is no longer reproducible - everything is working properly, yay! Could it be that mesa was upgraded a couple of days ago, resolving the issue? Anyways, the issue looks to be fixed now. Thanks again! -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: New Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583]
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I've been testing with the older kernel 6.2 and the issue seems not to be reproducible there. Therefore, the workaround looks to be to use kernel 6.2 for the time being. -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. The setup: the machine is connected to an external monitor via USB-C. Running kernel 6.5 on Ubuntu 23.10. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
** Attachment added: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037641/+attachment/5706097/+files/dmesg ** Description changed: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. + + The setup: the machine is connected to an external monitor via USB-C. + Running kernel 6.5 on Ubuntu 23.10. + There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [ 422.206597] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077727+03:00 mavi-ThinkPad-T14s kernel: [
[Kernel-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Yup, as I suspected, there is a kernel panic too: ``` [ 702.019208] [drm] ring 0 timeout to preempt ib [ 711.547840] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_low timeout, signaled seq=70630, emitted seq=70632 [ 711.548723] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xwayland pid 4958 thread Xwayland:cs0 pid 4979 [ 711.549595] amdgpu :06:00.0: amdgpu: GPU reset begin! [ 711.776824] [drm] psp gfx command UNLOAD_TA(0x2) failed and response status is (0x117) [ 711.802932] amdgpu :06:00.0: amdgpu: MODE2 reset [ 711.803000] amdgpu :06:00.0: amdgpu: GPU reset succeeded, trying to resume [ 711.803210] [drm] PCIE GART of 1024M enabled. [ 711.803215] [drm] PTB located at 0x00F43FC0 [ 711.803348] [drm] PSP is resuming... [ 712.510703] [drm] reserve 0x40 from 0xf43f80 for PSP TMR [ 712.789403] amdgpu :06:00.0: amdgpu: RAS: optional ras ta ucode is not available [ 712.800536] amdgpu :06:00.0: amdgpu: RAP: optional rap ta ucode is not available [ 712.800545] amdgpu :06:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available [ 712.800553] amdgpu :06:00.0: amdgpu: SMU is resuming... [ 712.800840] amdgpu :06:00.0: amdgpu: SMU is resumed successfully! [ 712.801302] [drm] DMUB hardware initialized: version=0x01010027 [ 713.207082] [drm] kiq ring mec 2 pipe 1 q 0 [ 713.222540] [drm:amdgpu_dm_atomic_commit_tail [amdgpu]] *ERROR* got no status for stream e7f7b0df on acrtc15c04636 [ 713.223561] [ cut here ] [ 713.223564] WARNING: CPU: 3 PID: 6794 at drivers/gpu/drm/amd/amdgpu/../display/dc/core/dc.c:3113 update_planes_and_stream_state+0x176/0x460 [amdgpu] [ 713.224355] Modules linked in: nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter ccm rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink bridge stp llc overlay cmac algif_hash algif_skcipher af_alg bnep binfmt_misc snd_soc_dmic snd_acp3x_pdm_dma snd_acp3x_rn snd_sof_amd_rembrandt snd_sof_amd_renoir snd_sof_amd_acp snd_sof_pci snd_sof_xtensa_dsp snd_sof intel_rapl_msr intel_rapl_common snd_sof_utils iwlmvm snd_ctl_led snd_soc_core snd_usb_audio snd_hda_codec_realtek snd_compress btusb nls_iso8859_1 edac_mce_amd snd_hda_codec_generic snd_hda_codec_hdmi ac97_bus snd_usbmidi_lib btrtl uvcvideo mac80211 snd_ump snd_pcm_dmaengine videobuf2_vmalloc uvc snd_pci_ps snd_hda_intel btbcm snd_rpl_pci_acp6x videobuf2_memops snd_intel_dspcfg kvm_amd btintel snd_acp_pci videobuf2_v4l2 snd_seq_midi snd_pci_acp6x btmtk snd_intel_sdw_acpi tps6598x libarc4 snd_pci_acp5x [ 713.224562] snd_seq_midi_event kvm videodev snd_hda_codec bluetooth snd_rn_pci_acp3x snd_rawmidi snd_hda_core iwlwifi irqbypass think_lmi videobuf2_common snd_hwdep snd_acp_config thinkpad_acpi ecdh_generic snd_soc_acpi mc rapl ipmi_devintf ecc firmware_attributes_class wmi_bmof nvram snd_seq k10temp snd_pcm snd_pci_acp3x snd_seq_device i2c_piix4 cfg80211 snd_timer ccp ipmi_msghandler snd soundcore ledtrig_audio platform_profile serial_multi_instantiate i2c_scmi joydev input_leds mac_hid serio_raw msr parport_pc ppdev lp parport efi_pstore dmi_sysfs ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c dm_crypt hid_generic ax88179_178a usbhid usbnet hid mii amdgpu amdxcp iommu_v2 drm_buddy gpu_sched i2c_algo_bit drm_suballoc_helper drm_ttm_helper ttm drm_display_helper cec rc_core crct10dif_pclmul crc32_pclmul polyval_clmulni polyval_generic drm_kms_helper ghash_clmulni_intel sha512_ssse3 aesni_intel rtsx_pci_sdmmc crypto_simd nvme drm cryptd psmouse ucsi_acpi nvme_core r8169 typec_ucsi xhci_pci [ 713.224805] rtsx_pci xhci_pci_renesas video typec nvme_common realtek wmi [ 713.224827] CPU: 3 PID: 6794 Comm: kworker/u32:20 Not tainted 6.5.0-5-generic #5-Ubuntu [ 713.224834] Hardware name: LENOVO 20UH001QMX/20UH001QMX, BIOS R1CET76W(1.45 ) 07/31/2023 [ 713.224839] Workqueue: events_unbound commit_work [drm_kms_helper] [ 713.224886] RIP: 0010:update_planes_and_stream_state+0x176/0x460 [amdgpu] [ 713.225699] Code: 5c 41 5d 41 5e 41 5f 5d 31 d2 31 c9 31 f6 31 ff 45 31 c0 45 31 c9 45 31 d2 45 31 db e9 c3 7a 0c d9 44 8b 55 ac 45 85 d2 74 9a <0f> 0b 31 c0 eb b7 83 7d a8 01 4c 89 45 b0 0f 86 01 01 00 00 8b 55 [ 713.225705] RSP: 0018:b04c0ad877e8 EFLAGS: 00010202 [ 713.225712] RAX: RBX: 9330ca354800 RCX: 9330d01bd800 [ 713.225717] RDX: 0001 RSI: RDI: [ 713.225721] RBP: b04c0ad87858 R08: 9330ca354de8 R09: b04c0ad878ac [ 713.225725] R10: 0001 R11: 0004 R12: 0001 [ 713.225729] R13: 9330ca354de8 R14: 9330d37e R15: 9330d01bd800 [ 713.225733] FS: () GS:9337900c()
[Kernel-packages] [Bug 2037760] [NEW] Create modprobe configuration for the IGX kernel
Public bug reported: Blacklist the following modules, which are replaced by out-of-tree modules: blacklist tegradisp_nvkms blacklist tegradisp_rm blacklist snd_soc_tegra186_asrc blacklist snd_soc_tegra186_dspk blacklist snd_soc_tegra210_admaif blacklist snd_soc_tegra210_adx blacklist snd_soc_tegra210_ahub blacklist snd_soc_tegra210_amx blacklist snd_soc_tegra210_dmic blacklist snd_soc_tegra210_i2s blacklist snd_soc_tegra210_mixer blacklist snd_soc_tegra210_mvc blacklist snd_soc_tegra210_ope blacklist snd_soc_tegra210_sfc blacklist snd_soc_tegra_audio_graph_card blacklist tegra-safety blacklist dwmac_tegra blacklist host1x blacklist tegra-drm RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use them: options nvidia NVreg_OpenRmEnableUnsupportedGpus=1 Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's /lib/modprobe.d config. ** Affects: linux-nvidia-tegra-igx (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2037760 Title: Create modprobe configuration for the IGX kernel Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: Blacklist the following modules, which are replaced by out-of-tree modules: blacklist tegradisp_nvkms blacklist tegradisp_rm blacklist snd_soc_tegra186_asrc blacklist snd_soc_tegra186_dspk blacklist snd_soc_tegra210_admaif blacklist snd_soc_tegra210_adx blacklist snd_soc_tegra210_ahub blacklist snd_soc_tegra210_amx blacklist snd_soc_tegra210_dmic blacklist snd_soc_tegra210_i2s blacklist snd_soc_tegra210_mixer blacklist snd_soc_tegra210_mvc blacklist snd_soc_tegra210_ope blacklist snd_soc_tegra210_sfc blacklist snd_soc_tegra_audio_graph_card blacklist tegra-safety blacklist dwmac_tegra blacklist host1x blacklist tegra-drm RTX A6000 is considered "unsupported" by the OpenRM drivers, but we want to use them: options nvidia NVreg_OpenRmEnableUnsupportedGpus=1 Add these modprobe stanzas to the linux-nvidia-tegra-igx kernel's /lib/modprobe.d config. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2037760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031344] Re: apply nvidia igx patches for Aug 8-14
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2031344 Title: apply nvidia igx patches for Aug 8-14 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: 2 patches to apply to IGX kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2031344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2032578] Re: apply nvidia igx patches for Aug 15-21
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2032578 Title: apply nvidia igx patches for Aug 15-21 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Released Bug description: 1 patch for the dates Aug 15-21, 2023 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2032578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] [NEW] amdgpu: [gfxhub0] no-retry page fault
Public bug reported: Whenever I use Intellij IDEA, after a couple of minutes the screen locks up and pretty much renders the machine unusable. I can still ssh to it, but the UI is pretty much gone and doesn't respond to Ctrl+Alt+F* keys. There's the following in kern.log: ``` 2023-09-28T13:58:23.077679+03:00 mavi-ThinkPad-T14s kernel: [ 422.206433] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077694+03:00 mavi-ThinkPad-T14s kernel: [ 422.206450] amdgpu :06:00.0: amdgpu: in page starting at address 0xb15852923000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077695+03:00 mavi-ThinkPad-T14s kernel: [ 422.206460] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077696+03:00 mavi-ThinkPad-T14s kernel: [ 422.206466] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077698+03:00 mavi-ThinkPad-T14s kernel: [ 422.206471] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206476] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077699+03:00 mavi-ThinkPad-T14s kernel: [ 422.206481] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077700+03:00 mavi-ThinkPad-T14s kernel: [ 422.206485] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206490] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077701+03:00 mavi-ThinkPad-T14s kernel: [ 422.206497] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077702+03:00 mavi-ThinkPad-T14s kernel: [ 422.206506] amdgpu :06:00.0: amdgpu: in page starting at address 0xb07248096000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077703+03:00 mavi-ThinkPad-T14s kernel: [ 422.206514] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206519] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077704+03:00 mavi-ThinkPad-T14s kernel: [ 422.206524] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206528] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077705+03:00 mavi-ThinkPad-T14s kernel: [ 422.206533] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077706+03:00 mavi-ThinkPad-T14s kernel: [ 422.206538] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077707+03:00 mavi-ThinkPad-T14s kernel: [ 422.206542] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077708+03:00 mavi-ThinkPad-T14s kernel: [ 422.206549] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077709+03:00 mavi-ThinkPad-T14s kernel: [ 422.206556] amdgpu :06:00.0: amdgpu: in page starting at address 0xaf8c3d808000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206564] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077710+03:00 mavi-ThinkPad-T14s kernel: [ 422.206569] amdgpu :06:00.0: amdgpu: Faulty UTCL2 client ID: IA (0x2) 2023-09-28T13:58:23.077711+03:00 mavi-ThinkPad-T14s kernel: [ 422.206574] amdgpu :06:00.0: amdgpu: MORE_FAULTS: 0x1 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206578] amdgpu :06:00.0: amdgpu: WALKER_ERROR: 0x0 2023-09-28T13:58:23.077712+03:00 mavi-ThinkPad-T14s kernel: [ 422.206583] amdgpu :06:00.0: amdgpu: PERMISSION_FAULTS: 0x3 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206588] amdgpu :06:00.0: amdgpu: MAPPING_ERROR: 0x0 2023-09-28T13:58:23.077713+03:00 mavi-ThinkPad-T14s kernel: [ 422.206592] amdgpu :06:00.0: amdgpu: RW: 0x0 2023-09-28T13:58:23.077726+03:00 mavi-ThinkPad-T14s kernel: [ 422.206597] amdgpu :06:00.0: amdgpu: [gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:6 pasid:32773, for process Xwayland pid 7640 thread Xwayland:cs0 pid 7663) 2023-09-28T13:58:23.077727+03:00 mavi-ThinkPad-T14s kernel: [ 422.206605] amdgpu :06:00.0: amdgpu: in page starting at address 0xaea632f7a000 from IH client 0x1b (UTCL2) 2023-09-28T13:58:23.077727+03:00 mavi-ThinkPad-T14s kernel: [ 422.206613] amdgpu :06:00.0: amdgpu: VM_L2_PROTECTION_FAULT_STATUS:0x00600431 2023-09-28T13:58:23.077728+03:00 mavi-ThinkPad-T14s kernel: [
[Kernel-packages] [Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
I can confirm that it works! <:D -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland Status in X.Org X server: Unknown Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Bug description: I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/2034619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2033295] Re: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen
Kernel >6.3 and amd_pstate=active (not needed for kernel >6.5) solves the problem on my Thinkpad P14s gen 3. -- 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/2033295 Title: AMDGPU: Screen frequently and suddenly freezes. Hard reboot necessary. AMD Ryzen Status in linux package in Ubuntu: Confirmed Bug description: Frequently, when I just use the computer, the mouse cursor freezes, the screen starts to flicker and freezes (screen flickers between entirely black and desktop visible). No interaction possible. In most cases Ctrl-Alt-Prnt-REISUB works to hard reboot the system. Frequency: Freezes happen several times a day. Unsaved work is lost. I noticed that: * The freezes usually happen when an external display is connected (it does not matter whether USB-C or HDMI). The freezes rarely happen when no external display is connected. * The freezes happen with Wayland and X11, with Ubuntu UI and Gnome Shell. * The freezes happen randomly, but I have the feeling that they happen more often when "something graphical" happens, e.g. when I go to the Gnome Shell overview, desktop switching, or when I switch to/from full screen mode, click on an image to scale it, or when I use map services in the web browser like Google Maps or radio.garden. * The freezes even more often happened when WebGL is active in Firefox or Chomium. * I encounter these annoying freezes already for several weeks. Having looked at the log files, I assume that AMDGPU is at the core of the problem. System: Ubuntu 23.04 (up to date), Wayland (freezes also happen with X11), Gnome 44.3. Linux 6.2.0-31-generic Lenovo ThinkPad T14s Gen 1 (with most recent BIOS/UEFI 1.44), AMD Ryzen™ 7 PRO 4750U with Radeon™ Graphics × 16. --- ProblemType: Bug ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME DistroRelease: Ubuntu 23.04 InstallationDate: Installed on 2021-06-06 (813 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20UJS00K00 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-31-generic root=UUID=9eae73b3-aab9-4f80-9203-01ac00f03c33 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.2.0-31.31-generic 6.2.15 RelatedPackageVersions: linux-restricted-modules-6.2.0-31-generic N/A linux-backports-modules-6.2.0-31-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.6 Tags: lunar wayland-session Uname: Linux 6.2.0-31-generic x86_64 UpgradeStatus: Upgraded to lunar on 2023-05-11 (110 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/13/2023 dmi.bios.release: 1.44 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET75W(1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UJS00K00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.44 dmi.modalias: dmi:bvnLENOVO:bvrR1CET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UJS00K00:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJS00K00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UJ_BU_Think_FM_ThinkPadT14sGen1: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UJS00K00 dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2033295/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2030815] Re: apply nvidia igx patches for Aug 1-7
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2030815 Title: apply nvidia igx patches for Aug 1-7 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: Set of 7 patches for igx kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2030815/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2031344] Re: apply nvidia igx patches for Aug 8-14
** Changed in: linux-nvidia-tegra-igx (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra-igx in Ubuntu. https://bugs.launchpad.net/bugs/2031344 Title: apply nvidia igx patches for Aug 8-14 Status in linux-nvidia-tegra-igx package in Ubuntu: Fix Committed Bug description: 2 patches to apply to IGX kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2031344/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
