[Kernel-packages] [Bug 2026322] Re: Fix non-working MT7921e when pre-boot WiFi is enabled
** Tags added: oem-priority originate-from-2017953 stella ** Tags added: originate-from-2019067 -- 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/2026322 Title: Fix non-working MT7921e when pre-boot WiFi is enabled Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-6.1 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 source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under Linux. [Fix] Reset the device earlier at the probing process. [Test] With the patch applied, WiFi always works regardless of pre-boot WiFi is toggled or not. [Where problems could occur] Probe routine might fail one some other corner cases. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2026322/+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 2025444] Re: Mute/mic LEDs no function on some HP Platforms
** Changed in: oem-priority Status: Confirmed => Fix Committed ** Tags added: originate-from-2026260 -- 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/2025444 Title: Mute/mic LEDs no function on some HP Platforms Status in OEM Priority Project: Fix Committed Status in linux-oem-6.1 package in Ubuntu: New Status in linux-oem-6.1 source package in Jammy: Fix Committed Bug description: [Impact] The mic mute/audio mute LEDS are not work on some HP Platforms [Fix] It needs the specific quirk for the hardware layout. Thus, add the quirks to make it works. [Test] After applying the quirk on linux-oem-6.1, the audio/mic mute LEDs are working good. [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2025444/+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 2026322] [NEW] Fix non-working MT7921e when pre-boot WiFi is enabled
Public bug reported: [Impact] When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under Linux. [Fix] Reset the device earlier at the probing process. [Test] With the patch applied, WiFi always works regardless of pre-boot WiFi is toggled or not. [Where problems could occur] Probe routine might fail one some other corner cases. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Lunar) Importance: Undecided Assignee: Kai-Heng Feng (kaihengfeng) Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided => Medium ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Lunar) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) -- 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/2026322 Title: Fix non-working MT7921e when pre-boot WiFi is enabled Status in linux package in Ubuntu: New Status in linux-oem-6.1 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 source package in Lunar: Confirmed Status in linux-oem-6.1 source package in Lunar: Invalid Bug description: [Impact] When "pre-boot WiFi" is enabled in UEFI, MT7921e WiFi doesn't work under Linux. [Fix] Reset the device earlier at the probing process. [Test] With the patch applied, WiFi always works regardless of pre-boot WiFi is toggled or not. [Where problems could occur] Probe routine might fail one some other corner cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026322/+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 2023307] Re: System hang at reading amdgpu sysfs attribute psp_vbflash
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/2023307 Title: System hang at reading amdgpu sysfs attribute psp_vbflash Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux source package in Jammy: Invalid Status in linux-oem-6.0 source package in Jammy: Won't Fix Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: In Progress Status in linux-oem-6.0 source package in Mantic: Invalid Status in linux-oem-6.1 source package in Mantic: Confirmed Bug description: [Summary] 1. System hang on starting checkbox test. 2. Hang on collecting device information during start Auto and Stress test. 3. This issue exist on GPU with W7500 & W7600. [Steps to reproduce] 1. Boot into OS 2. Start Auto test or Stress test(checkbox-cli run com.canonical.certification::sysfs_attachment) AMD proposed fix in https://lore.kernel.org/amd-gfx/20230607065259.48516-1-mario.limoncie...@amd.com/T/#mc5c38f31129f23e498d669734cafe96474a8f8ba . --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1442 F pulseaudio /dev/snd/controlC0: u 1442 F pulseaudio CasperMD5CheckResult: pass DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-jammy-amd64-20220504-33+jellyfish-tynamo+X81 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2023-05-16 (23 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - somerville-jammy-amd64-20220504-33 IwConfig: lono wireless extensions. enp5s0f0 no wireless extensions. enp4s0no wireless extensions. MachineType: Dell Inc. Precision 7875 Tower Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.1.0-1014-oem root=UUID=e9463c30-0a89-4838-a9fa-3296791ccd2a ro log_buf_len=64M quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 6.1.0-1014.14-oem 6.1.29 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-6.1.0-1014-oem N/A linux-backports-modules-6.1.0-1014-oem N/A linux-firmware 20220329.git681281e4-0ubuntu3.13 RfKill: Tags: jammy Uname: Linux 6.1.0-1014-oem x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 05/10/2023 dmi.bios.release: 0.4 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.28 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.18 dmi.modalias: dmi:bvnDellInc.:bvr0.4.28:bd05/10/2023:br0.4:efr0.18:svnDellInc.:pnPrecision7875Tower:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku0C61: dmi.product.family: Precision dmi.product.name: Precision 7875 Tower dmi.product.sku: 0C61 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023307/+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 2025353] Re: Add support of AMD Pink Sardine and RPL DMIC
** Changed in: hwe-next Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2025353 Title: Add support of AMD Pink Sardine and RPL DMIC Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Jammy: Fix Committed Status in alsa-ucm-conf source package in Lunar: Fix Committed Status in alsa-ucm-conf source package in Mantic: Fix Released Bug description: [Impact] Mic-mute LED is not working after press (Mic-mute/F4) key on Thinkpad AMD platform with AMD Pink Sardine and RPL DMIC. [Fix] Add support of AMD Pink Sardine and RPL, DMIC and Micmute LED work fine. [Test] The mic mute LED works fine. [Where problems could occur] Low, upstream fix. It may break mic-mute LED. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2025353/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
There's also an askubuntu question about this issue: https://askubuntu.com/questions/1471028/fatalcredentials-cc127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2017980] Re: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13)
Relaying the information from https://bugs.chromium.org/p/chromium/issues/detail?id=1459821 as it is not publicly visible: ``` Hmmm this looks like https://bugs.chromium.org/p/chromium/issues/detail?id=1365674#c8 again. I don't know why using clone(CLONE_NEWUSER ...) would return EACCES (which causes the crash). It's not documented to return that error code and I couldn't find anything in 5.19 that would change that. Glibc doesn't seem to change the error code either. We have a spike of crashes here recently (unsurprisingly, most of them on this 5.19.0 -1010-nvidia-lowlatency #10-Ubuntu kernel). I would call this an upstream Ubuntu bug for now. ``` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2017980 Title: FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Status in linux-meta-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Confirmed Bug description: With this kernel linux-image-nvidia-5.19 (version 5.19.0.1009.10) I experience that google-chrome crashes. It shows ```shell [11849:11849:0428/091628.955956:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)". ``` To be honest I don't think it has anything to do with google-chrome at all. When google-chrome starts it (normally) request the system key-manager (KWallet in my case) for access to the users keys before it actually shows anything from chrome. Not even that part (the KWallet password box) shows up. I can only reproduce this problem with this specific kernel. It should be possible to take google-chrome out of the equation by using another application that starts by request the desktop key manager for access. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-nvidia-5.19 (not installed) ProcVersionSignature: Ubuntu 5.15.0-1023.23-nvidia 5.15.92 Uname: Linux 5.15.0-1023-nvidia x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Fri Apr 28 11:23:23 2023 InstallationDate: Installed on 2016-01-08 (2666 days ago) InstallationMedia: Kubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: linux-meta-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-21 (281 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-nvidia-5.19/+bug/2017980/+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 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory
Hi, black screen may be caused by multiple issues. Is message "RmInitAdapter failed" message gone after restarting with nvidia and kernel updates from last days? I noticed 2 updates. I had to remote login over ssh to analyze logging before fix. (last update installs new kernel, updates initrd and nvidia modules/libraries) currently on 6.2.0-24-generic from ubuntu distro. snipped of installed nvidia to get exact version: linux-objects-nvidia-390-6.2.0-24-generic6.2.0-24.24+5 Regarding your question regarding "mainline-kernel", which is a bash script which makes it easier to install non-standard kernels, which i used to install 5.19.17 to have my system workable with nvidia chipset. (and ld.so.conf.d nvidia hack). Posted link to ubuntu-mainline-kernel.sh in previous post. My messages is about: i have uninstalled those, and booted into latest ubuntu 23.04 provided kernel. you don't need to worry about it. But installing mainline-kernel 5.19.17 and ld.so.conf.d hack might get you going without the pressure of wanting/trying to downgrade whole distribution installation, just select desired kernel during boot time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2016459 Title: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Hi, just performed a do-release_upgrade -d to try 23.10 on my lenovo T430 laptop with Nvidia chipset (NVIDIA NVS 5200M). Upgrade went smooth, but noticed my external displays where not seen. a checkup shows nvidia-settings doesn't show full as usual, and noticed messages in recarding NVRM which i had never before. ``` [35057.710742] NVRM: RmInitAdapter failed! (0x30:0x:663) [35057.710792] NVRM: rm_init_adapter failed for device bearing minor number 0 [35060.706390] NVRM: failed to copy vbios to system memory. [35060.706501] NVRM: RmInitAdapter failed! (0x30:0x:663) [35060.706562] NVRM: rm_init_adapter failed for device bearing minor number 0 [35063.708929] NVRM: failed to copy vbios to system memory. [35063.709041] NVRM: RmInitAdapter failed! (0x30:0x:663) [35063.709087] NVRM: rm_init_adapter failed for device bearing minor number 0 ``` searching for nvidia ``` 2023-04-16T22:15:49.402742+02:00 T430-i7 kernel: [ 14.428429] nvidia: loading out-of-tree module taints kernel. 2023-04-16T22:15:49.402743+02:00 T430-i7 kernel: [ 14.428443] nvidia: module license 'NVIDIA' taints kernel. 2023-04-16T22:15:49.402757+02:00 T430-i7 kernel: [ 14.528477] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 2023-04-16T22:15:49.402845+02:00 T430-i7 kernel: [ 14.529212] nvidia :01:00.0: enabling device ( -> 0003) 2023-04-16T22:15:49.402847+02:00 T430-i7 kernel: [ 14.529674] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none 2023-04-16T22:15:49.402857+02:00 T430-i7 kernel: [ 14.589081] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.157 Wed Oct 12 09:15:25 UTC 2022 2023-04-16T22:15:49.402870+02:00 T430-i7 kernel: [ 14.619491] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver 2023-04-16T22:15:49.402901+02:00 T430-i7 kernel: [ 14.657436] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to allocate NvKmsKapiDevice 2023-04-16T22:15:49.402903+02:00 T430-i7 kernel: [ 14.659661] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to register device 2023-04-16T22:15:49.402988+02:00 T430-i7 kernel: [ 15.433547] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 511 2023-04-16T22:15:49.402993+02:00 T430-i7 kernel: [ 15.536785] audit: type=1400 audit(1681676145.574:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=2406 comm="apparmor_parser" 2023-04-16T22:15:49.403000+02:00 T430-i7 kernel: [ 15.536790] audit: type=1400 audit(1681676145.574:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=2406 comm="apparmor_parser" 2023-04-16T22:15:49.403188+02:00 T430-i7 kernel: [ 18.933794] nvidia-uvm: Unloaded the UVM driver in 8 mode 2023-04-16T22:15:49.403194+02:00 T430-i7 kernel: [ 18.987254] nvidia-modeset: Unloading 2023-04-16T22:15:49.403195+02:00 T430-i7 kernel: [ 19.023265] nvidia-nvlink: Unregistered the Nvlink Core, major device number 234 2023-04-16T22:15:49.403218+02:00 T430-i7 kernel: [ 19.328850] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 2023-04-16T22:15:49.654976+02:00 T430-i7 kernel: [ 19.608711] nvidia :01:00.0: enabling device ( -> 0003) 2023-04-16T22:15:49.654996+02:00 T430-i7 kernel: [ 19.608847] nvidia
[Kernel-packages] [Bug 2025987] Re: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel
Marking the Qemu task as Incomplete, given that the problem goes away by using a different kernel, and there's nothing specific pointing to a Qemu bug. ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- 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/2025987 Title: 5.15.0-76: Qemu live migration causes VMs to crash but works with HWE kernel Status in linux package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: I am trying to live migrate Qemu VMs between Amd Zen3 to Zen2 servers. What we expect: VMs continue to run after live-migrate What happened: VMs instantly get stuck after migration with 100% CPU usage. All Nodes are running Ubuntu 22.04. We have tested Kernel releases back to 5.15.0-70. Nodes running Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: OK Nodes running Ubuntu 5.15.0-76.83-generic 5.15.99 : Zen2 -> Zen3 migration: OK Zen3 -> Zen2 migration: NOT OK We've tested it with fresh started and with live-migrated VMs, getting same results. Its probably related to KVM: SVM: fix tsc scaling cache logic https://linux.googlesource.com/linux/kernel/git/torvalds/linux/+/11d39e8cc43e1c6737af19ca9372e590061b5ad2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025987/+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 2025538] Re: Unrequested kernel update
This also installed itself and completely broke my machine, I couldn't even boot. Had to waste a whole workday trying to fix it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-nvidia-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in ubuntu-drivers-common package in Ubuntu: New Bug description: Running Kubuntu 22.04 LTS (lsb_release -a: Ubuntu 22.04.2 LTS) I was informed that new packages are available and I just hit update. This caused my system running 5.15.0-76-generic to be switched to 5.19.0-1010-nvidia-lowlatency. I noted this as I was now running into bugs like https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/2017980 The update was, as stated in history.log: Start-Date: 2023-07-01 00:25:40 Commandline: packagekit role='update-packages' Requested-By: cm (1000) Install: linux-objects-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-signatures-nvidia-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-image-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-5.19.0-1010-nvidia-lowlatency:amd64 (5.19.0-1010.10, automatic), linux-modules-nvidia-510-nvidia-lowlatency-edge:amd64 (5.19.0-1010.10, automatic) Upgrade: libmm-glib0:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2), modemmanager:amd64 (1.20.0-1~ubuntu22.04.1, 1.20.0-1~ubuntu22.04.2) => This simple update was changing my kernel from 5.15 to 5.19 without a request from my side ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-1010-nvidia-lowlatency 5.19.0-1010.10 ProcVersionSignature: Ubuntu 5.19.0-1010.10-nvidia-lowlatency 5.19.17 Uname: Linux 5.19.0-1010-nvidia-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sat Jul 1 21:16:09 2023 InstallationDate: Installed on 2018-10-10 (1724 days ago) InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) SourcePackage: linux-signed-nvidia-5.19 UpgradeStatus: Upgraded to jammy on 2022-07-24 (342 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-nvidia-5.19/+bug/2025538/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes
Ah, in that case I would say it shouldn't be a cherry pick. Just pick
the file.
IE We don't need the whole commit for either, just
amdgpu/yellow_carp_dmcub.bin (For RMB) and amdgpu/dcn_3_1_4_dmcub.bin
(for PHX).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Confirmed
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
Affects users of laptops that contain:
* AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
* eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)
[ Test Plan ]
* Test an affected laptop with the newer firmware and ensure that PSR-SU
function can be enabled and system is stable.
* Ensure other functions such as hotplugging monitors and suspending
continue to work.
[ Where problems could occur ]
* Affected firmware only is loaded on Rembrandt and Phoenix laptops.
Problems would be localized to these machines.
[ Other Info ]
The minimum firmware needed to help these hangs:
* Rembrandt: 0x43a or later
* Phoenix: 0x8001000 or later
The following commit upgrades the firmware for Rembrandt
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")
The following commit upgrades the firmware for Phoenix
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")
The TCON in a given laptop can be identified from the DPCD with this script:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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
Re: [Kernel-packages] [Bug 2007038] Re: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04
Glad it is not just me. I've acquired some other IB cards (Mellanox MHJH29-XTC X5 and an Oracle 7046442) and hope to try them against the later kernels' IB drivers too, but haven't had the time to take down the server yet. On 7/6/23 09:53, Shurak wrote: > Hello! > > > Same problem here: Ubuntu 22.04 (kernel 5.15.0-76-generic) with mother > S3200SHC (with latest fw) and pci-e card (with latest fw 1.2.0) > > 01:00.0 InfiniBand: Mellanox Technologies MT25204 [InfiniHost III Lx > HCA] (rev 20) > > I can submit any report needed (just tell me the link to the procedure > or the console commands) > > Thank you very much > Best Regards > -- 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/2007038 Title: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04 Status in linux package in Ubuntu: Expired Bug description: I run some x86_64 machines with Infiniband interfaces (Mellanox MT25204, ib_mthca driver + ib_ipoib for IP-over-IB). This had worked fine for years under Ubuntu 20.04.1 LTS and under RHEL6 before it. But as soon as I updated to 22.04.1 LTS -- with both its default 5.15.0-60-generic kernel and also 6.1.0-1006-oem (the latest packaged one I could find), the IB interface doesn't work. dmesg shows some UBSAN shift-out-of-bounds warnings in mthca modules, e.g. "shift exponent -25557 is negative". That's a bizarre number - maybe a hint of something uninitialized? The crippling symptom shows up within a second after that: a NULL dereference within the ib_mthca driver -- the "BUG: kernel NULL pointer dereference", in mthca_poll_one. The interface never sets its RUNNING flag (as shown by ifconfig). The rest of the system remains usable after the "BUG" message -- the ethernet, disk, etc. drivers and other functions work as expected. Attempting to unload the ib_mthca driver causes a kernel panic. Is there anything I should try? Should I build a kernel from source with debugging? I could try installing the 5.4.0 kernel from 20.04, but would rather use something that will continue to get security patches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 12 14:12 seq crw-rw+ 1 root audio 116, 33 Feb 12 14:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sun Feb 12 14:17:28 2023 InstallationDate: Installed on 2020-11-22 (812 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X7DBR-8 PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=8624cf02-e743-4da6-9209-14ef2c2abd10 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-10 (2 days ago) dmi.bios.date: 12/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: X7DBR-8 dmi.board.vendor: Supermicro dmi.board.version: PCB Version dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/03/2007:svnSupermicro:pnX7DBR-8:pvr0123456789:rvnSupermicro:rnX7DBR-8:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:sku: dmi.product.name: X7DBR-8 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007038/+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 2024774] Re: AMD Rembrandt / Phoenix PSR-SU related freezes
the upstream commits update firmware for other asics too, meaning that
we'd need to pull in earlier updates for all of them and not just
Rembrandt/Phoenix..
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2024774
Title:
AMD Rembrandt / Phoenix PSR-SU related freezes
Status in Linux Firmware:
New
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-firmware source package in Jammy:
Confirmed
Status in linux-firmware source package in Lunar:
Confirmed
Status in linux-firmware source package in Mantic:
Fix Released
Bug description:
[ Impact ]
When using kernel 6.2 or later AMD has enabled PSR selective update (PSR-SU).
After a non-deterministic amount of time the system may hang with a message
like this in the logs:
"[amdgpu :67:00.0: [drm] *ERROR* [CONNECTOR:78:eDP-1] commit wait timed
out]"
Affects users of laptops that contain:
* AMD Rembrandt (Yellow Carp) or AMD Phoenix (Pink Sardine) chips
* eDP panels with Parade TCONs (8-03 and 8-01 both reported to fail)
[ Test Plan ]
* Test an affected laptop with the newer firmware and ensure that PSR-SU
function can be enabled and system is stable.
* Ensure other functions such as hotplugging monitors and suspending
continue to work.
[ Where problems could occur ]
* Affected firmware only is loaded on Rembrandt and Phoenix laptops.
Problems would be localized to these machines.
[ Other Info ]
The minimum firmware needed to help these hangs:
* Rembrandt: 0x43a or later
* Phoenix: 0x8001000 or later
The following commit upgrades the firmware for Rembrandt
(amdgpu/yellow_carp_dmcub.bin) to 0x43c:
9dbd8ec2 ("amdgpu: DMCUB updates for various AMDGPU asics")
The following commit upgrades the firmware for Phoenix
(amdgpu/dcn_3_1_4_dmcub.bin) to 0x8001a00:
045b2136 ("amdgpu: update DMCUB to v0.0.172.0 for various AMDGPU ASICs")
The TCON in a given laptop can be identified from the DPCD with this script:
https://gitlab.freedesktop.org/drm/amd/-/blob/master/scripts/psr.py
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux-firmware/+bug/2024774/+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 2026295] [NEW] Google Chrome loses hardware acceleration after update to nvidia 535 drivers
Public bug reported: Google Chrome (114.0.5735.198) has no hardware acceleration anymore with nvidia-driver-535_535.54.03-0ubuntu0.23.04.2 Chrome log on chrome://gpu shows: [8344:8344:0702/133010.886230:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process. GpuProcessHost: The GPU process crashed! Console output of chrome shows: [8519:1:0702/133015.490076:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange. [8301:8301:0702/133015.506857:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133 [8372:1:0702/133018.997300:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [8411:1:0702/133033.519614:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [8301:8301:0702/133033.537284:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133 [8519:1:0702/133034.105681:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange. [8519:1:0702/133034.105831:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error Tried setting __GL_THREADED_OPTIMIZATIONS=0 as a workaround which reportedly helps with a similar issue with steam CEF, but no change for this issue. Rolling back to 530.41.03 and immediately hwaccel is back. ** Affects: nvidia-graphics-drivers-535 (Ubuntu) Importance: Undecided Status: New -- 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/2026295 Title: Google Chrome loses hardware acceleration after update to nvidia 535 drivers Status in nvidia-graphics-drivers-535 package in Ubuntu: New Bug description: Google Chrome (114.0.5735.198) has no hardware acceleration anymore with nvidia-driver-535_535.54.03-0ubuntu0.23.04.2 Chrome log on chrome://gpu shows: [8344:8344:0702/133010.886230:WARNING:sandbox_linux.cc(393)] : InitializeSandbox() called with multiple threads in process gpu-process. GpuProcessHost: The GPU process crashed! Console output of chrome shows: [8519:1:0702/133015.490076:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange. [8301:8301:0702/133015.506857:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133 [8372:1:0702/133018.997300:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [8411:1:0702/133033.519614:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer. [8301:8301:0702/133033.537284:ERROR:gpu_process_host.cc(953)] GPU process exited unexpectedly: exit_code=133 [8519:1:0702/133034.105681:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange. [8519:1:0702/133034.105831:ERROR:grcontext_for_gles2_interface.cc(61)] Skia shader compilation error Tried setting __GL_THREADED_OPTIMIZATIONS=0 as a workaround which reportedly helps with a similar issue with steam CEF, but no change for this issue. Rolling back to 530.41.03 and immediately hwaccel is back. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535/+bug/2026295/+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 2025616] Re: kernel Firmware Bug: TSC ADJUST differs failures during suspend
I was curious why this wasn't a problem with focal/5.4. I took a look at the last cert run that used focal/5.4[*], and I see these errors in the logs as well. I then went back to the cert run that was used to award focal certification[**] and those errors do *not* appear there. So either this is an intermittent failure, or likely one of 3 things happened in the interim: - The test changed (or was introduced) - The kernel changed - The firmware changed The test does not appear to be new - I have not checked if it has changed. The kernel version between these runs changed from 5.4.0-37.41-generic to 5.4.0-121.137-generic. A change to this kernel code was introduced in between, in 5.4.0-100.113-generic: commit 7dcfa07b500834c75a4f5043a43f409a3f02bd5e Author: Feng Tang Date: Wed Nov 17 10:37:50 2021 +0800 x86/tsc: Add a timer to make sure TSC_adjust is always checked BugLink: https://bugs.launchpad.net/bugs/1956381 commit c7719e79347803b8e3b6b50da8c6db410a3012b5 upstream. That causes the code that *might* print this warning to run every 10 minutes, instead of when the CPU enters idle. But the log shows these messages appearing every 28-29 seconds, so this being the cause seems unlikely. As for the firmware, the dmidecode output is identical between these runs, which suggests the firmware has not changed. [*] https://certification.canonical.com/hardware/201711-25989/submission/269263/ [**] https://certification.canonical.com/hardware/201711-25989/submission/172650/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/2025616 Title: kernel Firmware Bug: TSC ADJUST differs failures during suspend Status in linux-nvidia package in Ubuntu: New Bug description: [Summary] Discoverd kernel error message during suspend stress test test case id: power-management/suspend_30_cycles_with_reboots collected log ~~~ High failures: s3: 180 failures HIGH Kernel message: [38779.612837] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5266754042. Restoring (x 3) HIGH Kernel message: [38839.622411] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5295340520. Restoring (x 3) HIGH Kernel message: [38868.467564] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270514862. Restoring (x 3) HIGH Kernel message: [38897.419897] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5275834616. Restoring (x 3) HIGH Kernel message: [38926.135900] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5249511520. Restoring (x 3) HIGH Kernel message: [38955.114760] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5252454094. Restoring (x 3) HIGH Kernel message: [38983.860142] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5270474360. Restoring (x 3) HIGH Kernel message: [39012.819868] [Firmware Bug]: TSC ADJUST differs: CPU0 0 --> -5264045578. Restoring (x 3) ~~~ [Failure rate] 1/1 [Additional information] CID: 201711-25989 SKU: DGX-1 Station system-manufacturer: NVIDIA system-product-name: DGX Station bios-version: 0406 CPU: Intel(R) Xeon(R) CPU E5-2698 v4 @ 2.20GHz (40x) GPU: 07:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 08:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0e:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) 0f:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1db2] (rev a1) nvidia-driver-version: 525.105.17 kernel-version: 5.15.0-1028-nvidia [Stage] Issue reported and logs collected at a later stage To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/2025616/+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 2007038] Re: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04
Hello! Same problem here: Ubuntu 22.04 (kernel 5.15.0-76-generic) with mother S3200SHC (with latest fw) and pci-e card (with latest fw 1.2.0) 01:00.0 InfiniBand: Mellanox Technologies MT25204 [InfiniHost III Lx HCA] (rev 20) I can submit any report needed (just tell me the link to the procedure or the console commands) Thank you very much Best Regards -- 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/2007038 Title: 22.04 ib_mthca BUG: kernel NULL pointer, but had worked in 20.04 Status in linux package in Ubuntu: Expired Bug description: I run some x86_64 machines with Infiniband interfaces (Mellanox MT25204, ib_mthca driver + ib_ipoib for IP-over-IB). This had worked fine for years under Ubuntu 20.04.1 LTS and under RHEL6 before it. But as soon as I updated to 22.04.1 LTS -- with both its default 5.15.0-60-generic kernel and also 6.1.0-1006-oem (the latest packaged one I could find), the IB interface doesn't work. dmesg shows some UBSAN shift-out-of-bounds warnings in mthca modules, e.g. "shift exponent -25557 is negative". That's a bizarre number - maybe a hint of something uninitialized? The crippling symptom shows up within a second after that: a NULL dereference within the ib_mthca driver -- the "BUG: kernel NULL pointer dereference", in mthca_poll_one. The interface never sets its RUNNING flag (as shown by ifconfig). The rest of the system remains usable after the "BUG" message -- the ethernet, disk, etc. drivers and other functions work as expected. Attempting to unload the ib_mthca driver causes a kernel panic. Is there anything I should try? Should I build a kernel from source with debugging? I could try installing the 5.4.0 kernel from 20.04, but would rather use something that will continue to get security patches. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-60-generic 5.15.0-60.66 ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78 Uname: Linux 5.15.0-60-generic x86_64 AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Feb 12 14:12 seq crw-rw+ 1 root audio 116, 33 Feb 12 14:12 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Sun Feb 12 14:17:28 2023 InstallationDate: Installed on 2020-11-22 (812 days ago) InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Supermicro X7DBR-8 PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-60-generic root=UUID=8624cf02-e743-4da6-9209-14ef2c2abd10 ro RelatedPackageVersions: linux-restricted-modules-5.15.0-60-generic N/A linux-backports-modules-5.15.0-60-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.9 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2023-02-10 (2 days ago) dmi.bios.date: 12/03/2007 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: X7DBR-8 dmi.board.vendor: Supermicro dmi.board.version: PCB Version dmi.chassis.type: 1 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd12/03/2007:svnSupermicro:pnX7DBR-8:pvr0123456789:rvnSupermicro:rnX7DBR-8:rvrPCBVersion:cvnSupermicro:ct1:cvr0123456789:sku: dmi.product.name: X7DBR-8 dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2007038/+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 2019024] Re: Migrate oem-5.17 to oem-6.1
** Summary changed: - Migrate oem-5.17 to hwe-6.2 + Migrate oem-5.17 to oem-6.1 ** Description changed: [Impact] - Migrate oem-5.17 to hwe-5.19 now that there should be no functional regressions left anymore. + Migrate oem-5.17 to oem-6.1 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.17 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. ** Package changed: linux-restricted-modules-hwe-5.19 (Ubuntu) => linux- restricted-modules-oem-6.1 (Ubuntu) ** Package changed: linux-meta-hwe-5.19 (Ubuntu) => linux-meta-oem-6.1 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2019024 Title: Migrate oem-5.17 to oem-6.1 Status in linux-meta-oem-6.1 package in Ubuntu: Invalid Status in linux-restricted-modules-oem-6.1 package in Ubuntu: Invalid Status in linux-meta-oem-6.1 source package in Jammy: New Status in linux-restricted-modules-oem-6.1 source package in Jammy: New Bug description: [Impact] Migrate oem-5.17 to oem-6.1 now that there should be no functional regressions left anymore. [Test case] Update a machine with oem-5.17 metapackages to the proposed ones, and verify that all packages (including nvidia etc) migrate properly. [Where things could go wrong] In theory we might miss a package to transition, but at this point this is unlikely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-oem-6.1/+bug/2019024/+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 2024917] Re: [Azure][MANA][InfinitiBand] Features Support and InfiniBand for MANA
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/2024917 Title: [Azure][MANA][InfinitiBand] Features Support and InfiniBand for MANA Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested support for MANA feature updates as well as virtual Infiniband support. [Test Case] Microsoft tested [Regression Potential] the MANA driver may not function correctly. Infiniband is new. [Other Info] SF: #00358953 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2024917/+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
Re: [Kernel-packages] [Bug 2025543] Re: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
sudo apt-get install linux-headers-6.2.0-1007-lowlatency Reading package lists... Done Building dependency tree... Done Reading state information... Done The following additional packages will be installed: linux-lowlatency-headers-6.2.0-1007 The following NEW packages will be installed: linux-headers-6.2.0-1007-lowlatency linux-lowlatency-headers-6.2.0-1007 0 upgraded, 2 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. Need to get 16.8 MB of archives. After this operation, 110 MB of additional disk space will be used. Do you want to continue? [Y/n] y Get:1 http://us.archive.ubuntu.com/ubuntu lunar-updates/main amd64 linux-lowlatency-headers-6.2.0-1007 all 6.2.0-1007.7 [13.2 MB] Get:2 http://us.archive.ubuntu.com/ubuntu lunar-updates/main amd64 linux-headers-6.2.0-1007-lowlatency amd64 6.2.0-1007.7 [3,625 kB] Fetched 16.8 MB in 2s (10.6 MB/s) Selecting previously unselected package linux-lowlatency-headers-6.2.0-1007. (Reading database ... 200643 files and directories currently installed.) Preparing to unpack .../linux-lowlatency-headers-6.2.0-1007_6.2.0-1007.7_all.deb ... Unpacking linux-lowlatency-headers-6.2.0-1007 (6.2.0-1007.7) ... Selecting previously unselected package linux-headers-6.2.0-1007-lowlatency. Preparing to unpack .../linux-headers-6.2.0-1007-lowlatency_6.2.0-1007.7_amd64.deb ... Unpacking linux-headers-6.2.0-1007-lowlatency (6.2.0-1007.7) ... Setting up linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ... Setting up linux-lowlatency-headers-6.2.0-1007 (6.2.0-1007.7) ... Setting up linux-headers-6.2.0-1007-lowlatency (6.2.0-1007.7) ... /etc/kernel/header_postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-1007-lowlatency Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... unset ARCH; [ ! -h /usr/bin/cc ] && export CC=/usr/bin/gcc; env NV_VERBOSE=1 'make' -j12 NV_EXCLUDE_BUILD_MODULES='' KERNEL_UNAME=6.2.0-1007-lowlatency IGNORE_XEN_PRESENCE=1 IGNORE_CC_MISMATCH=1 SYSSRC=/lib/modules/6.2.0-1007-lowlatency/build LD=/usr/bin/ld.bfd CONFIG_X86_KERNEL_IBT= modules.. Signing module /var/lib/dkms/nvidia/525.125.06/build/nvidia.ko Signing module /var/lib/dkms/nvidia/525.125.06/build/nvidia-modeset.ko Signing module /var/lib/dkms/nvidia/525.125.06/build/nvidia-drm.ko Signing module /var/lib/dkms/nvidia/525.125.06/build/nvidia-uvm.ko Signing module /var/lib/dkms/nvidia/525.125.06/build/nvidia-peermem.ko Cleaning build area... nvidia.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ nvidia-modeset.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ nvidia-drm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ nvidia-uvm.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ nvidia-peermem.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ depmod... Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Building module: Cleaning build area... KERNELDIR=/lib/modules/6.2.0-1007-lowlatency/build make driver. Signing module /var/lib/dkms/openrazer-driver/3.6.1/build/driver/razerkbd.ko Signing module /var/lib/dkms/openrazer-driver/3.6.1/build/driver/razermouse.ko Signing module /var/lib/dkms/openrazer-driver/3.6.1/build/driver/razerkraken.ko Signing module /var/lib/dkms/openrazer-driver/3.6.1/build/driver/razeraccessory.ko Cleaning build area... razerkbd.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ razermouse.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ razerkraken.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.2.0-1007-lowlatency/updates/dkms/ razeraccessory.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to
Re: [Kernel-packages] [Bug 2025543] Re: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
sudo apt-get upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages have been kept back: gnome-remote-desktop libinput-bin libinput10 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ... Processing triggers for linux-image-6.2.0-1007-lowlatency (6.2.0-1007.7) ... /etc/kernel/postinst.d/dkms: * dkms: running auto installation service for kernel 6.2.0-1007-lowlatency Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at /lib/modules/6.2.0-1007-lowlatency/build or /lib/modules/6.2.0-1007-lowlatency/source. Please install the linux-headers-6.2.0-1007-lowlatency package or use the --kernelsourcedir option to tell DKMS where it's located. Sign command: /usr/bin/kmodsign Signing key: /var/lib/shim-signed/mok/MOK.priv Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der Error! Your kernel headers for kernel 6.2.0-1007-lowlatency cannot be found at /lib/modules/6.2.0-1007-lowlatency/build or /lib/modules/6.2.0-1007-lowlatency/source. Please install the linux-headers-6.2.0-1007-lowlatency package or use the --kernelsourcedir option to tell DKMS where it's located. dkms autoinstall on 6.2.0-1007-lowlatency/x86_64 failed for nvidia(1) openrazer-driver(1) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 dpkg: error processing package linux-image-6.2.0-1007-lowlatency (--configure): installed linux-image-6.2.0-1007-lowlatency package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-6.2.0-1007-lowlatency E: Sub-process /usr/bin/dpkg returned an error code (1) On Sat, Jul 1, 2023 at 11:35 PM Apport retracing service < 2025...@bugs.launchpad.net> wrote: > ** Tags removed: need-duplicate-check > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2025543 > > Title: > package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with > return code 11 > > Status in linux-signed-lowlatency package in Ubuntu: > New > > Bug description: > Failed upon update via GUI. > > ProblemType: Package > DistroRelease: Ubuntu 23.04 > Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 > ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 > Uname: Linux 6.2.0-23-generic x86_64 > NonfreeKernelModules: nvidia_modeset nvidia > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > Date: Sat Jul 1 13:21:52 2023 > ErrorMessage: installed linux-image-6.2.0-1007-lowlatency package > post-installation script subprocess returned error exit status 1 > InstallationDate: Installed on 2023-02-02 (149 days ago) > InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) > Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, > 3.11.2-1 > PythonDetails: N/A > RebootRequiredPkgs: Error: path contained symlinks. > RelatedPackageVersions: >dpkg 1.21.21ubuntu1 >apt 2.6.0 > SourcePackage: linux-signed-lowlatency > Title: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to > install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return > code 11 > UpgradeStatus: Upgraded to lunar on 2023-05-22 (40 days ago) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/linux-signed-lowlatency/+bug/2025543/+subscriptions > > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2025543 Title: package linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in linux-signed-lowlatency package in Ubuntu: New Bug description: Failed upon update via GUI. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-1007-lowlatency 6.2.0-1007.7 ProcVersionSignature: Ubuntu 6.2.0-23.23-generic 6.2.12 Uname: Linux 6.2.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass Date: Sat Jul 1 13:21:52 2023 ErrorMessage: installed linux-image-6.2.0-1007-lowlatency package post-installation script subprocess returned error exit
[Kernel-packages] [Bug 1553750] Re: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2
*** This bug is a duplicate of bug 1547505 *** https://bugs.launchpad.net/bugs/1547505 ** This bug is no longer a duplicate of bug 1553744 package linux-image-4.4.0-10-generic 4.4.0-10.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 ** This bug has been marked a duplicate of bug 1547505 package linux-image-4.4.0-6-generic 4.4.0-6.21 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 -> can't read /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth -- 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/1553750 Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 Status in linux-meta package in Ubuntu: New Bug description: upgrading from 15.10 with latest update software ( after do a apt-get update && sudo apt-get upgrade). I got 5 or more errors in sequence. I'll try to install manually other kernel. probably same bug as: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553744 and https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1553749 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-generic 4.4.0.10.11 ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zhe1403 F pulseaudio /dev/snd/controlC0: zhe1403 F pulseaudio /dev/snd/controlC2: zhe1403 F pulseaudio Date: Sun Mar 6 12:37:12 2016 ErrorMessage: dependency problems - leaving unconfigured HibernationDevice: RESUME=UUID=614b6ea9-83ad-4c8a-a581-03bcf289e06e InstallationDate: Installed on 2016-03-06 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) IwConfig: enp3s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7900 ProcFB: 0 radeondrmfb 1 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-30-generic.efi.signed root=UUID=d8cd991e-7ac6-4097-b3cc-775150407e05 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A RfKill: SourcePackage: linux-meta Title: package linux-image-generic 4.4.0.10.11 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 2 UpgradeStatus: Upgraded to xenial on 2016-03-06 (0 days ago) dmi.bios.date: 01/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88X-G45 GAMING (MS-7900) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.7:bd01/12/2016:svnMSI:pnMS-7900:pvr1.0:rvnMSI:rnA88X-G45GAMING(MS-7900):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7900 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1553750/+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 2025599] Re: BlueZ release 5.68
Thanks Daniel, uploaded ** Changed in: bluez (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2025599 Title: BlueZ release 5.68 Status in bluez package in Ubuntu: Fix Committed Bug description: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 1980805] Re: Backport packages for 20.04.5 HWE stack
** Changed in: mesa (Ubuntu Focal) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to llvm-toolchain-13 in Ubuntu. https://bugs.launchpad.net/bugs/1980805 Title: Backport packages for 20.04.5 HWE stack Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-13 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in mesa-amber package in Ubuntu: Invalid Status in libdrm source package in Focal: Fix Committed Status in llvm-toolchain-13 source package in Focal: Fix Committed Status in mesa source package in Focal: Won't Fix Status in mesa-amber source package in Focal: Fix Committed Bug description: [Impact] These are needed for 20.04.5 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. [What could go wrong] libdrm: pci-id updates, some minor api updates mesa: a new major release, but we'll pull the final stable release of 22.0.x series, so there shouldn't be any regressions left at that point mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI drivers that were removed from main mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 2026229] Re: Crashing issue with 5.15 kernel
Hello @jdkandersson, I see on the logs that the machines are running kernel 5.15.0-73-generic, can you please first try the jammy kernel currently in -updates (5.15.0-76.83)? If that doesn't solve, I would suggest trying the kernel in -proposed as well (currently 5.15.0-77.84). These kernels carry several fixes from upstream stable updates, so there's a chance the issue has been already fixed. -- 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+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 2026269] [NEW] Jammy update: v6.1.38 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.38 upstream stable release from git://git.kernel.org/ Linux 6.1.38 drm/amd/display: Ensure vmin and vmax adjust for DCE drm/amdgpu: Validate VM ioctl flags. docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation perf symbols: Symbol lookup with kcore can fail if multiple segments match stext nubus: Partially revert proc_create_single_data() conversion execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter drm/amd/display: Do not update DRR while BW optimizations pending drm/amd/display: Remove optimization for VRR updates xtensa: fix lock_mm_and_find_vma in case VMA not found ** Affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New -- 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/2026269 Title: Jammy update: v6.1.38 upstream stable release Status in linux-oem-6.1 package in Ubuntu: Confirmed Status in linux-oem-6.1 source package in Jammy: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v6.1.38 upstream stable release from git://git.kernel.org/ Linux 6.1.38 drm/amd/display: Ensure vmin and vmax adjust for DCE drm/amdgpu: Validate VM ioctl flags. docs: Set minimal gtags / GNU GLOBAL version to 6.6.5 scripts/tags.sh: Resolve gtags empty index generation perf symbols: Symbol lookup with kcore can fail if multiple segments match stext nubus: Partially revert proc_create_single_data() conversion execve: always mark stack as growing down during early stack setup PCI/ACPI: Call _REG when transitioning D-states PCI/ACPI: Validate acpi_pci_set_power_state() parameter drm/amd/display: Do not update DRR while BW optimizations pending drm/amd/display: Remove optimization for VRR updates xtensa: fix lock_mm_and_find_vma in case VMA not found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.1/+bug/2026269/+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 2026196] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess r
nvidia-fs 2.15.3 doesn't look like an Ubuntu package/version. Mantic is at 2.14.12~12.0.0-2: https://packages.ubuntu.com/mantic/nvidia-fs-dkms Please uninstall this unsupported nvidia-fs DKMS package and install the one for Mantic. ** Changed in: linux (Ubuntu) Status: New => Invalid -- 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/2026196 Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: Invalid Bug description: Has a restart error after update ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rama 1510 F wireplumber /dev/snd/controlC2: rama 1510 F wireplumber /dev/snd/controlC0: rama 1510 F wireplumber /dev/snd/seq:rama 1507 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jun 22 21:40:11 2023 ErrorMessage: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-05-07 (58 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=644d521c-89d4-4057-ac87-ecbdd199ff7e ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F60e dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF60e:bd12/09/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026196/+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 2026253] Re: i915: Add DMC/GuC/HuC firmware for Meteor Lake
** Changed in: linux-firmware (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2026253 Title: i915: Add DMC/GuC/HuC firmware for Meteor Lake Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Fix Committed Bug description: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2026253/+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 2026196] Re: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess r
Building module: Cleaning build area... 'make' -j32 KVER=6.2.0-23-generic IGNORE_CC_MISMATCH='1'...(bad exit status: 2) Error! Bad return status for module build on kernel: 6.2.0-23-generic (x86_64) Consult /var/lib/dkms/nvidia-fs/2.15.3/build/make.log for more information. dkms autoinstall on 6.2.0-23-generic/x86_64 succeeded for nvidia dkms autoinstall on 6.2.0-23-generic/x86_64 failed for nvidia-fs(10) Error! One or more modules failed to install during autoinstall. Refer to previous errors for more information. ...fail! -- 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/2026196 Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: Has a restart error after update ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-23-generic 6.2.0-23.23 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rama 1510 F wireplumber /dev/snd/controlC2: rama 1510 F wireplumber /dev/snd/controlC0: rama 1510 F wireplumber /dev/snd/seq:rama 1507 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jun 22 21:40:11 2023 ErrorMessage: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-05-07 (58 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: Gigabyte Technology Co., Ltd. B450M DS3H WIFI ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic root=UUID=644d521c-89d4-4057-ac87-ecbdd199ff7e ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1 PythonDetails: N/A RelatedPackageVersions: grub-pc N/A SourcePackage: linux Title: package linux-headers-6.2.0-23-generic 6.2.0-23.23 failed to install/upgrade: installed linux-headers-6.2.0-23-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2020 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F60e dmi.board.asset.tag: Default string dmi.board.name: B450M DS3H WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF60e:bd12/09/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3HWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3HWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: B450M DS3H WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026196/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
* linux-firmware SRU: - https://lists.ubuntu.com/archives/kernel-team/2023-July/140891.html (jammy) - https://lists.ubuntu.com/archives/kernel-team/2023-July/140892.html (lunar) ** Description changed: + [SRU Justification] + + BugLink: https://bugs.launchpad.net/bugs/2024427 + + [Impact] + + Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms + will sometimes fail to wake from S3. + + [Fix] + + kernel patches: + ac2f5739fdca drm/amdgpu/mes11: enable reg active poll + a2fe4534bb38 drm/amd/amdgpu: update mes11 api def + da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin + 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 + 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 + + firmware patches: + * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release + * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release + + [Test Case] + + $ checkbox-cli run com.canonical.certification::stress- + suspend-30-cycles-with-reboots-automated + + [Where problems could occur] + + Little we know about the firmware fixes. However, while with these commits have + been pulled via stable kernel fixes, the driver begins to request new firmware + blobs of a different filename. + + [Other Info] + + The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and + partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to + be fixed. + + For the firmware parts, they have been included in linux-firmware/mantic, + leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. + + == original bug report == + amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [SRU Justification] BugLink: https://bugs.launchpad.net/bugs/2024427 [Impact] Under stress testing it was reported that the amdgpu Navi31/Navi33 platforms will sometimes fail to wake from S3. [Fix] kernel patches: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 firmware patches: * Navi31: ffe1a41e2ddb amdgpu: update GC 11.0.0 firmware for amd.5.5 release * Navi33: a5d7b4df1a76 amdgpu: update GC 11.0.2 firmware for amd.5.5 release [Test Case] $ checkbox-cli run com.canonical.certification::stress- suspend-30-cycles-with-reboots-automated [Where problems could occur] Little we know about the firmware fixes. However, while with these commits have been pulled via stable kernel fixes, the driver begins to request new firmware blobs of a different filename. [Other Info] The kernel driver commits are in v6.4-rc1, backported to v6.3.4, v6.1.31, and partially (missing da9a8dc33da2, 616843d5a11b) v6.2.16. Only linux/lunar has to be fixed. For the firmware parts, they have been included in linux-firmware/mantic, leaving linux-firmware/lunar and linux-firmware/jammy to be fixed. == original bug report == amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin
[Kernel-packages] [Bug 2026253] Re: i915: Add DMC/GuC/HuC firmware for Meteor Lake
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2026253 Title: i915: Add DMC/GuC/HuC firmware for Meteor Lake Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Bug description: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2026253/+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 2024427] Re: potential S3 issue for amdgpu Navi 31/Navi33
** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => High ** Changed in: linux (Ubuntu Lunar) Status: Triaged => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2024427 Title: potential S3 issue for amdgpu Navi 31/Navi33 Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Lunar: In Progress Status in linux-firmware source package in Lunar: In Progress Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Triaged Status in linux-firmware source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: amdgppu update is needed to fix some potential Navi31/Navi33 S3 issue. amdgpu: ac2f5739fdca drm/amdgpu/mes11: enable reg active poll a2fe4534bb38 drm/amd/amdgpu: update mes11 api def da9a8dc33da2 drm/amdgpu: reserve the old gc_11_0_*_mes.bin 616843d5a11b drm/amd/amdgpu: introduce gc_*_mes_2.bin v2 09bf14907d86 drm/amdgpu: declare firmware for new MES 11.0.4 Navi31: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=ffe1a41e2ddbc39109b12d95dcac282d90eba8fc Navi33: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a5d7b4df1a76f82e2ecb725cc1b56ce111830bac To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2024427/+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 2025599] Re: BlueZ release 5.68
** Attachment added: "bluez_5.68-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+attachment/5684205/+files/bluez_5.68-0ubuntu1.debian.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2025599 Title: BlueZ release 5.68 Status in bluez package in Ubuntu: In Progress Bug description: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 2025599] Re: BlueZ release 5.68
** Attachment added: "bluez_5.68.orig.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+attachment/5684197/+files/bluez_5.68.orig.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/2025599 Title: BlueZ release 5.68 Status in bluez package in Ubuntu: In Progress Bug description: BlueZ release 5.68 is now available: https://mirrors.edge.kernel.org/pub/linux/bluetooth/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 2026253] Re: i915: Add DMC/GuC/HuC firmware for Meteor Lake
these are already in mantic ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2026253 Title: i915: Add DMC/GuC/HuC firmware for Meteor Lake Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Bug description: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2026253/+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 2026253] [NEW] i915: Add DMC/GuC/HuC firmware for Meteor Lake
Public bug reported: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Description changed: [Impact] - Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel - + Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. - [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/2026253 Title: i915: Add DMC/GuC/HuC firmware for Meteor Lake Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: New Bug description: [Impact] Intel Meteor Lake GPU's need new firmware for upcoming oem-6.5 kernel. As the kernel is only for jammy, there's no need to target lunar/kinetic. [Test case] Install the update, check that i915.ko driver loads them fine on MTL hardware. [Where problems could happen] These are new files for new hardware, so they can't regress shipping hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/2026253/+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 2026229] Re: Crashing issue with 5.15 kernel
** Description changed: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be - with the kernel. This is a doc with more details: - https://docs.google.com/document/d/1E00rlT12Cu-h99do80Qge- - MKyQARFDY6hxSjhFFfPvA/edit?usp=sharing + with the kernel. + + The github-runner charm is a machine charm that runs on virtual + machines. The charm creates a LXD virtual machine inside the juju + unit/machine and runs the GitHub self-hosted runner application. The + self-hosted runner can be used on GitHub to run GitHub Actions. + + The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: + Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 + The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ + Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ + The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. + + For the last week, the team has been experimenting with upgrading the + kernel to the HWE version which is 5.19. Since then we have not + encountered crashes in the virtual machine hosting the juju machine. + + This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: + https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy -- 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/2026229 Title: Crashing issue with 5.15 kernel Status in linux package in Ubuntu: New Bug description: We have been working on making self-hosted GitHub actions runners available in Canonical and have encountered an issue which seems to be with the kernel. The github-runner charm is a machine charm that runs on virtual machines. The charm creates a LXD virtual machine inside the juju unit/machine and runs the GitHub self-hosted runner application. The self-hosted runner can be used on GitHub to run GitHub Actions. The deployment of github-runner charm consists of about 15 units/machines (one unit per machine). In the past, we would see about one machine going into “down” state about every 1-3 days. From the openstack hosting the machine, it seems the machine has crashed. The syslog includes the following entry: Jun 8 21:15:58 juju-e4d256-prod-github-runner-66 kernel: [27199.579882] BUG: kernel NULL pointer dereference, address: 0008 The syslog: https://pastebin.canonical.com/p/gYy3Z9XGkN/ Log on openstack: https://pastebin.canonical.com/p/fbGcmQv9JW/ The deployment of the charm was on the jammy series (22.04). This series uses the Linux kernel 5.15. For the last week, the team has been experimenting with upgrading the kernel to the HWE version which is 5.19. Since then we have not encountered crashes in the virtual machine hosting the juju machine. This mattermost thread includes our team’s discussion of this issue and the reason we decide to upgrade the kernel: https://chat.canonical.com/canonical/pl/h8wrrmcnh3d17dtjmg56zf5pwy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026229/+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 2025550] Re: nvidia 535 kernel module is not loaded
** Changed in: nvidia-graphics-drivers-535 (Ubuntu) Status: Incomplete => Won't Fix -- 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/2025550 Title: nvidia 535 kernel module is not loaded Status in nvidia-graphics-drivers-535 package in Ubuntu: Won't Fix Bug description: After an update my external display switched off and is not being detected. I connected my external display to windows laptop to test and it worked. Some additional information: lsb_release -rd No LSB modules are available. Description: Ubuntu 23.04 Release: 23.04 xrandr --listmonitors Monitors: 1 0: +*XWAYLAND0 1920/340x1080/190+0+0 XWAYLAND0 dpkg -l | grep -i nvidia ii libnvidia-cfg1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA binary OpenGL/GLX configuration library ii libnvidia-common-535 535.54.03-0ubuntu0.23.04.2 all Shared files used by the NVIDIA libraries rc libnvidia-compute-525:amd64 525.116.04-0ubuntu0.23.04.1 amd64NVIDIA libcompute package ii libnvidia-compute-535:amd64535.54.03-0ubuntu0.23.04.2 amd64NVIDIA libcompute package ii libnvidia-decode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA Video Decoding runtime libraries ii libnvidia-encode-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVENC Video Encoding runtime library ii libnvidia-extra-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64Extra libraries for the NVIDIA driver ii libnvidia-fbc1-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL-based Framebuffer Capture runtime library ii libnvidia-gl-535:amd64 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA OpenGL/GLX/EGL/GLES GLVND libraries and Vulkan ICD rc linux-modules-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 rc linux-modules-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 rc linux-modules-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 ii linux-objects-nvidia-525-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel nvidia modules for version 6.2.0-1005 (objects) ii linux-objects-nvidia-525-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel nvidia modules for version 6.2.0-1007 (objects) rc linux-objects-nvidia-525-6.2.0-20-generic 6.2.0-20.20+2 amd64Linux kernel nvidia modules for version 6.2.0-20 (objects) rc linux-objects-nvidia-525-6.2.0-23-generic 6.2.0-23.23 amd64Linux kernel nvidia modules for version 6.2.0-23 (objects) rc linux-objects-nvidia-525-6.2.0-24-generic 6.2.0-24.24 amd64Linux kernel nvidia modules for version 6.2.0-24 (objects) ii linux-signatures-nvidia-6.2.0-1005-oracle 6.2.0-1005.5+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1005-oracle ii linux-signatures-nvidia-6.2.0-1007-lowlatency 6.2.0-1007.7+3 amd64Linux kernel signatures for nvidia modules for version 6.2.0-1007-lowlatency rc nvidia-compute-utils-525 525.116.04-0ubuntu0.23.04.1 amd64NVIDIA compute utilities ii nvidia-compute-utils-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA compute utilities ii nvidia-dkms-535535.54.03-0ubuntu0.23.04.2 amd64NVIDIA DKMS package ii nvidia-driver-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA driver metapackage ii nvidia-firmware-535-535.54.03 535.54.03-0ubuntu0.23.04.2 amd64Firmware files used by the kernel module rc nvidia-kernel-common-525 525.116.04-0ubuntu0.23.04.1 amd64Shared files used with the kernel module ii nvidia-kernel-common-535 535.54.03-0ubuntu0.23.04.2 amd64Shared files used with the kernel module ii nvidia-kernel-source-535 535.54.03-0ubuntu0.23.04.2 amd64NVIDIA kernel source package ii nvidia-prime 0.8.17.1
[Kernel-packages] [Bug 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory
Unfortunately, just the 6.2.0-24-generic + 390.157-0ubuntu5.23.04.1 didn't work for my laptop with 820M. I get a blinking cursor black screen after the Ubuntu splash. Maybe I missed something from your config/setup. For example, > deactivated the mainline-kernel installed manual Can you explain what this means? Or do you have any other suggestions? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/2016459 Title: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: Hi, just performed a do-release_upgrade -d to try 23.10 on my lenovo T430 laptop with Nvidia chipset (NVIDIA NVS 5200M). Upgrade went smooth, but noticed my external displays where not seen. a checkup shows nvidia-settings doesn't show full as usual, and noticed messages in recarding NVRM which i had never before. ``` [35057.710742] NVRM: RmInitAdapter failed! (0x30:0x:663) [35057.710792] NVRM: rm_init_adapter failed for device bearing minor number 0 [35060.706390] NVRM: failed to copy vbios to system memory. [35060.706501] NVRM: RmInitAdapter failed! (0x30:0x:663) [35060.706562] NVRM: rm_init_adapter failed for device bearing minor number 0 [35063.708929] NVRM: failed to copy vbios to system memory. [35063.709041] NVRM: RmInitAdapter failed! (0x30:0x:663) [35063.709087] NVRM: rm_init_adapter failed for device bearing minor number 0 ``` searching for nvidia ``` 2023-04-16T22:15:49.402742+02:00 T430-i7 kernel: [ 14.428429] nvidia: loading out-of-tree module taints kernel. 2023-04-16T22:15:49.402743+02:00 T430-i7 kernel: [ 14.428443] nvidia: module license 'NVIDIA' taints kernel. 2023-04-16T22:15:49.402757+02:00 T430-i7 kernel: [ 14.528477] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 2023-04-16T22:15:49.402845+02:00 T430-i7 kernel: [ 14.529212] nvidia :01:00.0: enabling device ( -> 0003) 2023-04-16T22:15:49.402847+02:00 T430-i7 kernel: [ 14.529674] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=none 2023-04-16T22:15:49.402857+02:00 T430-i7 kernel: [ 14.589081] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 390.157 Wed Oct 12 09:15:25 UTC 2022 2023-04-16T22:15:49.402870+02:00 T430-i7 kernel: [ 14.619491] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver 2023-04-16T22:15:49.402901+02:00 T430-i7 kernel: [ 14.657436] [drm:nv_drm_load [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to allocate NvKmsKapiDevice 2023-04-16T22:15:49.402903+02:00 T430-i7 kernel: [ 14.659661] [drm:nv_drm_probe_devices [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x0100] Failed to register device 2023-04-16T22:15:49.402988+02:00 T430-i7 kernel: [ 15.433547] nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 511 2023-04-16T22:15:49.402993+02:00 T430-i7 kernel: [ 15.536785] audit: type=1400 audit(1681676145.574:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=2406 comm="apparmor_parser" 2023-04-16T22:15:49.403000+02:00 T430-i7 kernel: [ 15.536790] audit: type=1400 audit(1681676145.574:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=2406 comm="apparmor_parser" 2023-04-16T22:15:49.403188+02:00 T430-i7 kernel: [ 18.933794] nvidia-uvm: Unloaded the UVM driver in 8 mode 2023-04-16T22:15:49.403194+02:00 T430-i7 kernel: [ 18.987254] nvidia-modeset: Unloading 2023-04-16T22:15:49.403195+02:00 T430-i7 kernel: [ 19.023265] nvidia-nvlink: Unregistered the Nvlink Core, major device number 234 2023-04-16T22:15:49.403218+02:00 T430-i7 kernel: [ 19.328850] nvidia-nvlink: Nvlink Core is being initialized, major device number 234 2023-04-16T22:15:49.654976+02:00 T430-i7 kernel: [ 19.608711] nvidia :01:00.0: enabling device ( -> 0003) 2023-04-16T22:15:49.654996+02:00 T430-i7 kernel: [ 19.608847] nvidia :01:00.0: vgaarb: changed VGA decodes: olddecodes=none,decodes=none:owns=none 2023-04-16T22:15:49.720716+02:00 T430-i7 systemd[1]: Starting nvidia-persistenced.service - NVIDIA Persistence Daemon... 2023-04-16T22:15:49.723994+02:00 T430-i7 nvidia-persistenced: Verbose syslog connection opened 2023-04-16T22:15:49.724337+02:00 T430-i7 nvidia-persistenced: Now running with user ID 139 and group ID 155 2023-04-16T22:15:49.724508+02:00 T430-i7 systemd[1]: Started nvidia-persistenced.service - NVIDIA Persistence Daemon. 2023-04-16T22:15:49.724577+02:00 T430-i7 nvidia-persistenced: Started (3602) 2023-04-16T22:15:49.724717+02:00 T430-i7 nvidia-persistenced: Received signal 15 2023-04-16T22:15:49.724786+02:00 T430-i7 nvidia-persistenced: PID file unlocked.
