[Kernel-packages] [Bug 2037340] [NEW] Four Screens
You have been subscribed to a public bug: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu wayland-session -- Four Screens https://bugs.launchpad.net/bugs/2037340 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037613] [NEW] package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beyagu 1901 F pulseaudio /dev/snd/controlC1: beyagu 1901 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Sep 28 10:29:33 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-28 (91 days ago) InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 (20230419) IwConfig: lono wireless extensions. enp3s0no wireless extensions. docker0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=603facbe-a5f3-4d8a-b62d-bd59c2ddf5c4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: dkms Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2017 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H61 dmi.board.vendor: INTEL Corporation dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd07/19/2017:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnINTELCorporation:rnH61:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2037613 Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: package linux-image-6.2.0-32-generic 6.2.0-32.32 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-31-generic 6.2.0-31.31 ProcVersionSignature: Ubuntu 6.2.0-32.32-generic 6.2.16 Uname: Linux 6.2.0-32-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 AptOrdering: NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beyagu 1901 F pulseaudio /dev/snd/controlC1: beyagu 1901 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass Date: Thu Sep 28 10:29:33 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-06-28 (91 days ago) InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 (20230419) IwConfig: lono wireless extensions. enp3s0no wireless extensions. docker0 no wireless extensions. MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-32-generic root=UUID=603facbe-a5f3-4d8a-b62d-bd59c2ddf5c4 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1 PythonDetails: /usr/bin/python3.11, Python 3.11.4, python-is-python3, 3.11.1-3 RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: grub-pc 2.06-2ubuntu16 RfKill: SourcePackage: dkms Title: package linux-image-6.2.0-31-generic 6.2.0-31.31 failed to
[Kernel-packages] [Bug 2037340] Re: Four Screens
I can't think of a good solution here, but if you would like the same "safe graphics" mode that also happens to disable the GPU, then you can edit /etc/default/grub and change: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" and then run: sudo update-grub and reboot. Though performance will be poor. ** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (Ubuntu) ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags added: radeon ** Summary changed: - Four Screens + [radeon] iMac a1311 is split into four screens -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2037340 Title: [radeon] iMac a1311 is split into four screens Status in linux-hwe-6.2 package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: I apologize for any grammar issues, but I can barely see what I am typing. Essentially, when I installed Ubuntu, I had to do so in safe graphics mode, as the screen would otherwise split itself into four different displays that had small amounts of resolution and are rather pale. I managed to install it, but once that happend, and it restarted, it went back to being four screens. I am not sure what to do, as I cannot really read any lines of code. Thank you for your help. I am using an iMac a1311, with an HDD and installed from a flashed usb. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Sep 25 20:33:11 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV730/M96-XT [Mobility Radeon HD 4670] [1002:9488] (prog-if 00 [VGA controller]) Subsystem: Apple Inc. RV730/M96-XT [Mobility Radeon HD 4670] [106b:00b6] InstallationDate: Installed on 2023-09-24 (1 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) MachineType: Apple Inc. iMac10,1 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=be40ad74-149a-443c-99b3-2dbae10973a3 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/14/2019 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 215.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Mac-F2268CC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 13 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268CC8 dmi.modalias: dmi:bvnAppleInc.:bvr215.0.0.0.0:bd06/14/2019:br0.1:svnAppleInc.:pniMac10,1:pvr1.0:rvnAppleInc.:rnMac-F2268CC8:rvr:cvnAppleInc.:ct13:cvrMac-F2268CC8:skuSystemSKU#: dmi.product.family: Mac dmi.product.name: iMac10,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.2/+bug/2037340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037650] [NEW] dkms-autopkgtest: avoid catching packages with -no-dkms in their name
Public bug reported: [Impact] The current version of dkms-autopkgtest in 20.04 and later selects binary packages with names ending with "-dkms" for its automatic DKMS test. This also includes packages such as nvidia-headless-535-no-dkms, which are not real dkms packages, and should not be tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535, and the test will fail because of nvidia-headless-535-no-dkms not being an actual dkms package. https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html [Where problems could occur] The main issue that we can experience is if the scripts dealt with other packages with "-no-dkms" in their name, which, for some reason, actually are DKMS packages, in which case, their testing would be skipped. ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Focal) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: dkms (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: dkms (Ubuntu Jammy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2037650 Title: dkms-autopkgtest: avoid catching packages with -no-dkms in their name Status in dkms package in Ubuntu: New Status in dkms source package in Focal: New Status in dkms source package in Jammy: New Status in dkms source package in Lunar: New Bug description: [Impact] The current version of dkms-autopkgtest in 20.04 and later selects binary packages with names ending with "-dkms" for its automatic DKMS test. This also includes packages such as nvidia-headless-535-no-dkms, which are not real dkms packages, and should not be tested automatically by autopkgtest. [Test Case] Run autopkgtest in Focal, or later, for nvidia-graphics-drivers-535, and the test will fail because of nvidia-headless-535-no-dkms not being an actual dkms package. https://kernel.ubuntu.com/adt-matrix/lunar-linux-meta.html [Where problems could occur] The main issue that we can experience is if the scripts dealt with other packages with "-no-dkms" in their name, which, for some reason, actually are DKMS packages, in which case, their testing would be skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2037650/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037642] [NEW] [FFe] Raspberry Pi 5 support
Public bug reported: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement ** Affects: libcamera (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: mesa (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: pipewire (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: rpi-eeprom (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: Confirmed ** Also affects: linux-meta-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Also affects: libcamera (Ubuntu) Importance: Undecided Status: New ** Also affects: pipewire (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: rpi-eeprom (Ubuntu) Importance: Undecided Status: New ** Also affects: rpiboot (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-settings (Ubuntu) Importance: Undecided Status: New ** Description changed: [ Impact ] - * HWE for Raspberry Pi 5 https://raspberrypi.com/5 + * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] - * Private builds tested on all existing/supported Raspberry Pi SKUs in + * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants - * No regressions on any existing SKUs + * No regressions on any existing SKUs - * Test that Raspberry Pi 5 boards work + * Test that Raspberry Pi 5 boards work [ Where problems could occur ] - * Mesa is upgraded, and there are patches to mesa, the raspberry-pi + * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. - * libcamera has new build-depends for the raspberry-pi specific - provider which also affects pipewire to provide full webcam support. + * libcamera has new build-depends on new package libpisp for the + raspberry-pi specific provider which also affects pipewire to provide + full webcam support. - * These dependencies, will need to make their way into gnome platform + * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] - - * The proposed code changes have been tested in private, prior to public announcement + + * The proposed code changes have been tested in private, prior to + public announcement ** Summary changed: - Raspberry Pi 5 support + [FFe] Raspberry Pi 5 support -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
[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 2037642] Re: [FFe] Raspberry Pi 5 support
The rpiboot package can be skipped for now; according to upstream the updated package won't be ready at release. The separate bug LP: #2032178 will track updates if/when I can get the uploaded. ** No longer affects: rpiboot (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/2037642 Title: [FFe] Raspberry Pi 5 support Status in libcamera package in Ubuntu: Confirmed Status in linux-firmware-raspi package in Ubuntu: Confirmed Status in linux-meta-raspi package in Ubuntu: Confirmed Status in linux-raspi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in pipewire package in Ubuntu: Confirmed Status in rpi-eeprom package in Ubuntu: Confirmed Status in ubuntu-settings package in Ubuntu: Confirmed Bug description: [ Impact ] * HWE for Raspberry Pi 5 https://raspberrypi.com/5 [ Test Plan ] * Private builds tested on all existing/supported Raspberry Pi SKUs in armhf & arm64 variants * No regressions on any existing SKUs * Test that Raspberry Pi 5 boards work [ Where problems could occur ] * Mesa is upgraded, and there are patches to mesa, the raspberry-pi specific provider this has been tested but not as extensively. Separately there is mesa FFe granted to upgrade to latest release, thus these changes piggy-back on top of it. * libcamera has new build-depends on new package libpisp for the raspberry-pi specific provider which also affects pipewire to provide full webcam support. * These dependencies, will need to make their way into gnome platform snaps to be usable by default in Firefox. [ Other Info ] * The proposed code changes have been tested in private, prior to public announcement To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037641] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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. 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 thre
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535-server - 535.104.12-0ubuntu0.23.04.1 --- nvidia-graphics-drivers-535-server (535.104.12-0ubuntu0.23.04.1) lunar; urgency=medium * New upstream release (LP: #2037266): - Fixed an issue where the NVSwitch driver would not retrain NVLinks on init correctly on HGX 8 H100, in case they faulted earlier (such a due to GPU resets). This would result in links being down and CUDA workloads failing with "system not yet initialized" error. The issue was introduced in the 535.86.10 driver and fixed in 535.104.12 and later drivers. -- Alberto Milone Mon, 25 Sep 2023 16:18:16 + ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Lunar) Status: In Progress => Fix Released ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Lunar) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535 - 535.113.01-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2037266): - Fixed a bug that could cause GPU memory utilization to be reported incorrectly for Multi-Instance GPU (MIG) partitions on Grace Hopper systems. - Fixed a bug that intermittently caused the display to freeze when resuming from suspend on some Ada GPUs. -- Alberto Milone Mon, 25 Sep 2023 09:45:05 + ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535-server - 535.104.12-0ubuntu0.22.04.1 --- nvidia-graphics-drivers-535-server (535.104.12-0ubuntu0.22.04.1) jammy; urgency=medium * New upstream release (LP: #2037266): - Fixed an issue where the NVSwitch driver would not retrain NVLinks on init correctly on HGX 8 H100, in case they faulted earlier (such a due to GPU resets). This would result in links being down and CUDA workloads failing with "system not yet initialized" error. The issue was introduced in the 535.86.10 driver and fixed in 535.104.12 and later drivers. -- Alberto Milone Mon, 25 Sep 2023 16:30:44 + ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535-server - 535.104.12-0ubuntu0.20.04.1 --- nvidia-graphics-drivers-535-server (535.104.12-0ubuntu0.20.04.1) focal; urgency=medium * New upstream release (LP: #2037266): - Fixed an issue where the NVSwitch driver would not retrain NVLinks on init correctly on HGX 8 H100, in case they faulted earlier (such a due to GPU resets). This would result in links being down and CUDA workloads failing with "system not yet initialized" error. The issue was introduced in the 535.86.10 driver and fixed in 535.104.12 and later drivers. -- Alberto Milone Mon, 25 Sep 2023 16:29:52 + ** Changed in: nvidia-graphics-drivers-535 (Ubuntu Focal) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2037266] Re: Update the 535 driver series - 25/09/2023
This bug was fixed in the package nvidia-graphics-drivers-535 - 535.113.01-0ubuntu0.23.04.1 --- nvidia-graphics-drivers-535 (535.113.01-0ubuntu0.23.04.1) lunar; urgency=medium * New upstream release (LP: #2037266): - Fixed a bug that could cause GPU memory utilization to be reported incorrectly for Multi-Instance GPU (MIG) partitions on Grace Hopper systems. - Fixed a bug that intermittently caused the display to freeze when resuming from suspend on some Ada GPUs. -- Alberto Milone Mon, 25 Sep 2023 09:32:34 + ** Changed in: nvidia-graphics-drivers-535-server (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535 in Ubuntu. https://bugs.launchpad.net/bugs/2037266 Title: Update the 535 driver series - 25/09/2023 Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-535 source package in Focal: Fix Released Status in nvidia-graphics-drivers-535-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-535 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535-server source package in Jammy: Fix Released Status in nvidia-graphics-drivers-535 source package in Lunar: Fix Released Status in nvidia-graphics-drivers-535-server source package in Lunar: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] 535 (535.113.01): https://www.nvidia.com/Download/driverResults.aspx/211711/en-us/ 535-server (535.104.12): https://docs.nvidia.com/datacenter/tesla/tesla-release-notes-535-104-12/index.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2037266/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036625] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
just remove linux-oem-5.17-tools-host and be done with it -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036625 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.1 package in Ubuntu: New Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:16:27 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2036625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036625] Re: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie
same for -6.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2036625 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 Status in linux-oem-6.1 package in Ubuntu: New Bug description: Install problem ProblemType: Package DistroRelease: Ubuntu 22.04 Package: linux-oem-6.1-tools-host (not installed) ProcVersionSignature: Ubuntu 6.5.0-1003.3-oem 6.5.0 Uname: Linux 6.5.0-1003-oem x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Tue Sep 19 17:16:27 2023 ErrorMessage: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 InstallationDate: Installed on 2023-08-27 (23 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.10 SourcePackage: linux-oem-6.1 Title: package linux-oem-6.1-tools-host (not installed) failed to install/upgrade: próba nadpisania "/lib/systemd/system/kvm_stat.service", który istnieje także w pakiecie linux-oem-5.17-tools-host 5.17.0-1035.36 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2036625/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036287] Re: 6.2.0-32 kernel doesn't work with Asus Vivobook
Hi, I installed Ubuntu 23.04 and this problem suddenly started arising on kernel 6.2.0-34. Then I installed Ubuntu 22.04.3 LTS with kernel 6.2.0-32 which also has this issue. Tried booting through advanced>6.2.0-26 which worked fine. The reason is the same fingerprint reader. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-6.2 in Ubuntu. https://bugs.launchpad.net/bugs/2036287 Title: 6.2.0-32 kernel doesn't work with Asus Vivobook Status in linux-signed-hwe-6.2 package in Ubuntu: Confirmed Bug description: I have both kernel 6.2.0-32 and 6.2.0-26 installed on my Asus Vivobook. Since 6.2.0-32 install boot has been impossible. I think this may be a common problem as I'm seeing issues with Ubuntu: https://ubuntuforums.org/showthread.php?t=2490616 and Linux Mint: https://forums.linuxmint.com/viewtopic.php?t=403618 https://askubuntu.com/questions/1485350/booting-ubuntu-22-with- kernel-6-2-0-32-is-impossible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-6.2.0-26-generic 6.2.0-26.26~22.04.1 ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13 Uname: Linux 6.2.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Sep 15 20:38:11 2023 InstallationDate: Installed on 2023-01-20 (238 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) RebootRequiredPkgs: Error: path contained symlinks. 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/ubuntu/+source/linux-signed-hwe-6.2/+bug/2036287/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2036273] Re: 5.15+ GCE Instances are unable to create fb0 with virt mon attached
Hi guys Is there an update here? Many thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2036273 Title: 5.15+ GCE Instances are unable to create fb0 with virt mon attached Status in linux-gcp package in Ubuntu: New Bug description: This is a public facing LP issue to address the content in Canonical's SF#00366439. Summary: Post 18.04 ( or 20.04 prior to moving to 5.15 ), efifb fails to stand up fb0. It is assigned, but fb0 is never created, nor are there any errors that I noted. Here is an example from a focal using linux-gcp --- 5.15.0-1041-gcp #49~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.925827] pci :00:05.0: BAR 0: assigned to efifb --- If you then install the generic HWE kernel and reboot, you can see that fb0 is successfully summoned: --- 5.15.0-83-generic #92~20.04.1-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [2.128815] pci :00:05.0: BAR 0: assigned to efifb [3.021819] efifb: probing for efifb [3.022511] efifb: framebuffer at 0xc000, using 6076k, total 6075k [3.023925] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [3.025382] efifb: scrolling: redraw [3.026347] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- and finally, using linux-gcp-lts on 20.04, it does work (as it's 5.4): --- 5.4.0-1112-gcp #121-Ubuntu SMP kyler_hornor@kyler-focal:~$ sudo dmesg | grep efifb [0.834541] pci :00:05.0: BAR 0: assigned to efifb [1.057258] efifb: probing for efifb [1.058182] efifb: framebuffer at 0xc000, using 6076k, total 6075k [1.059210] efifb: mode is 1920x1080x24, linelength=5760, pages=1 [1.060203] efifb: scrolling: redraw [1.060722] efifb: Truecolor: size=0:8:8:8, shift=0:16:8:0 --- So some linux-gcp backport or config seems to be breaking this. Supplementary to this, the framebuffer can not be leveraged by X and throws a fatal error around the time shadow is loaded. This part is replicable on -generic, as well as on debian using gdm3/X, so this is likely an upstream problem. I tried disabling shadow with an X conf, but as it uses 24bppp, it forces it. For the scope of this LP, we need to figure out the -gcp specific breakage. I've reached out to google to see if we can get some contacts on the virt mon team to push the other aspect forward. Replication: Launch any ubuntu 20.04+ GCE instance with the "Display Device" option enabled. Expected Behavior: We should see the above output in dmesg and also observe /dev/fb0 being created. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/2036273/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
