[Kernel-packages] [Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Fix Released ** Description changed: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. - [ Workaround ] + [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment + + or upgrade to a newer kernel: + sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.19 package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment or upgrade to a newer kernel: sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
The kernel is only seeing the built-in display as "connected": /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected If we assume one of those DP ports is actually the HDMI port then the problem would be a connector or cable issue. If however those DP ports are the USB-C ports then the HDMI port seems to be missing at the kernel level :( If the laptop has two GPUs then the second one would own the HDMI port, but I don't see a second GPU here. Unless it exists and is disabled in the BIOS? ** Package changed: mutter (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Changed in: linux-hwe-5.19 (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port Status in linux-hwe-5.19 package in Ubuntu: New Bug description: On fresh installation of Ubuntu 22.04.2 LTS with and without latest updates there's no HDMI signal to external monitor. No display , no picture, no detection at all. The hardware is functional under Windows the HDMI port is working. What I've managed to research is some problems with Intel 12th gen CPU GPUs drivers where other user have similar problem. Some sources mention Wayland protocol as part of the problem but cannot clarify how reliable that is. Tried changing display protocols on login but it didn't help. CPU i7-1255U , notebook: ASUS Expertbook B9400 CBA ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 00:53:19 2023 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu GraphicsCard: Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1f02] InstallationDate: Installed on 2023-07-12 (0 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 8087:0033 Intel Corp. Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK B9400CBA_B9400CBA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic root=UUID=28808a14-059c-4b86-a687-ebd6d7ad1b12 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2022 dmi.bios.release: 5.26 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: B9400CBA.214 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: B9400CBA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrB9400CBA.214:bd09/26/2022:br5.26:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKB9400CBA_B9400CBA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB9400CBA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ASUS EXPERTBOOK dmi.product.name: ASUS EXPERTBOOK B9400CBA_B9400CBA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2027631/+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 1989044] Re: RPL: Add INT3400 base path
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1989044 Title: RPL: Add INT3400 base path Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * Add INT3400 base path for Raptor Lake CPU. [Test Plan] * Use a machine with a Raptor Lake cpu. * check the thermald log. * Get the base path of INT3400. [Where problems could occur] * This change is to add path in INT3400 for Raptor Lake, which won't impact other hardware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989044/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
Verified against thermald-2.4.9-1ubuntu0.3, ~~~ LP#2018275, LP#2018236, LP#2012260, LP#2007579, LP#1989044, LP#1981087 ~~~ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 1995606] Re: Upgrade thermald to 2.5.1 for Jammy (22.04)
** Tags added: originate-from-2012475 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1995606 Title: Upgrade thermald to 2.5.1 for Jammy (22.04) Status in OEM Priority Project: New Status in thermald package in Ubuntu: New Status in thermald source package in Jammy: Fix Committed Bug description: [Justification] The purpose of this bug is that prevent the regression in the future. The automatic test scripts are better for the future SRU and is still on the planning. [Test case] For these CPU series, RPL/ADL/TGL/CML/CFL/KBL, the following tests will be run on machines in the CI lab: 1. Run stress-ng, and observe the temperature/frequency/power with s-tui - Temperatures should stay just below trip values - Power/performance profiles should stay roughly the same between old thermald and new thermald (unless specifically expected eg: to fix premature/insufficient throttling) 2. check if thermald could read rules from /dev/acpi_thermal_rel and generate the xml file on /etc/thermald/ correctly. - this depends on if acpi_thermal_rel exist. - if the machine suppots acpi_thermal_rel, the "thermal-conf.xml.auto" could be landed in etc/thermald/. - if not, the user-defined xml could be created, then jump to (3). - run thermald with --loglevel=debug, and compare the log with xml.auto file. check if the configuration could be parsed correctly. 3. check if theramd-conf.xml and thermal-cpu-cdev-order.xml can be loaded correctly. - run thermald with --loglevel=debug, and compare the log with xml files. - if parsed correctly, the configurations from XML files would appear in the log. 4. Run unit tests, the scripts are under test folder, using emul_temp to simulate the High temperatue and check thermald would throttle CPU through the related cooling device. - rapl.sh - intel_pstate.sh - powerclamp.sh - processor.sh 5. check if the power/frequency would be throttled once the temperature reach the trip-points of thermal zone. 6. check if system would be throttled even the temperature is under the trip-points. [ Where problems could occur ] since the PL1 min/max is introduced, there may have some cases that don't check the minimum of PL1 then make PL1 to smaller and smaller and throttle the CPU. this may cause machines run like the old behavior that doesn't have PL1 min/max. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1995606/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
** No longer affects: mutter (Ubuntu Jammy) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Won't Fix ** No longer affects: linux-intel-iotg (Ubuntu Jammy) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
@ Kai-Heng NOT THAT I'M AWARE OF (Why I booted the various ISOs (20.04.5 with 5.15, 22.04.2 with 5.19, and 23.04 with 6.2) under the same settings which had wifi..) IF the WLAN/RF_KILL can be toggled with a keyboard combination & I accidentally hit that, that for sure is possible as the keyboard isn't full size & I'm mishitting keys regularly on this device. The fact that 7/8 boots of mantic give me no WIFI is inconsistent I know, but I can't rule out me making mistakes on the keyboard. I'll endeavor to explore this later today. (a quick boot & look on installed system, and I don't see any, nor on https://helpguide.sony.net/apmig/vaio/htmlmanuals/20122Q/SVS1/eng/contents/03/13/01/01.html ... quick exploration of keys & I didn't see any extra written to dmesg |grep RF_KILL) -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+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 2027531] Re: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box
When it wasn't working: [4.500054] iwlwifi :01:00.0: RF_KILL bit toggled to disable radio. Does the system have any hardware rfkill button/switch? -- 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/2027531 Title: ubuntu/lubuntu mantic with 6.3 kernel only occasioanlly has wifi on this box Status in linux package in Ubuntu: New Bug description: On this device, wifi is only usable occasionally on repeated boots when using the 6.3 kernel now included on Ubuntu mantic. Same applies if I use Lubuntu or another 23.10 (ISO using 6.3) but not with 22.04.2, 20.04 or 23.04 ISOs. I'm seeing this as a regression on the kernel. PLEASE NOTE: This is the 5th time I've booted this thumb-drive since it was written yesterday and the FIRST of the 5 boots where it worked; thus I've used this "working" boot to file issue (hardware details) EVEN though its working now... I intend adding more, but at least can use this bug report to track when this issue occurs from now on (wifi is the ONLY networking on this box; so its a problem to report when I have the issue... If specific details would be helpful, please let me know. Also note I have a Ubuntu mantic desktop install currently on this box; and the issue occurs on installed images and not just LIVE boots; ie. installing Ubuntu Desktop, Lubuntu usually results in a boot that won't have wifi on first boot (thus far I've not had wifi first boot when installs are with 6.3 kernel!) Why it works after boot an older ISO though on thumb-drive seems strange to me.. maybe it's just luck & I'm seeing a pattern that isn't actually there. This issue I've been aware there since 6.3 kernel in my experience, but on this box/hardware only. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: linux-image-6.3.0-7-generic 6.3.0-7.7 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1659 F wireplumber /dev/snd/controlC0: ubuntu 1659 F wireplumber /dev/snd/seq:ubuntu 1656 F pipewire CRDA: N/A CasperMD5CheckResult: pass CasperVersion: 1.481 CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 03:16:45 2023 LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230705) MachineType: Sony Corporation SVP11216CGB ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz layerfs-path=minimal.standard.live.squashfs --- quiet splash RelatedPackageVersions: linux-restricted-modules-6.3.0-7-generic N/A linux-backports-modules-6.3.0-7-generic N/A linux-firmware 20230629.gitee91452d-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/17/2013 dmi.bios.release: 2.70 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0270V7 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.ec.firmware.release: 2.70 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0270V7:bd05/17/2013:br2.70:efr2.70:svnSonyCorporation:pnSVP11216CGB:pvrC60BZAQW:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:sku54585979: dmi.product.family: VAIO dmi.product.name: SVP11216CGB dmi.product.sku: 54585979 dmi.product.version: C60BZAQW dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027531/+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 2016388] Re: Kernel Panic on shutdown / reboot on NUC8I3BEH
Please install later kernel by issuing `sudo apt install linux-generic- hwe-20.04` and reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2016388 Title: Kernel Panic on shutdown / reboot on NUC8I3BEH Status in linux package in Ubuntu: Confirmed Bug description: Kernel 5.4.0-146 panics on power-down (e.g. shutdown -P now) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-146-generic 5.4.0-146.163 ProcVersionSignature: Ubuntu 5.4.0-144.161-generic 5.4.229 Uname: Linux 5.4.0-144-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bbogart1051 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sat Apr 15 09:07:33 2023 InstallationDate: Installed on 2019-02-09 (1526 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Intel(R) Client Systems NUC8i3BEH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-144-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-144-generic N/A linux-backports-modules-5.4.0-144-generic N/A linux-firmware 1.187.38 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-06-30 (289 days ago) dmi.bios.date: 02/14/2023 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0092.2023.0214.1114 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0092.2023.0214.1114:bd02/14/2023:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2016388/+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 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest
** Changed in: linux-gcp (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-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2020319 Title: Encountering an issue with memcpy_fromio causing failed boot of SEV- enabled guest Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: Fix Committed Bug description: [Impact] When launching a SEV-enabled guest, the guest kernel panics with the following call trace, indicating a critical error in the system. == [1.090638] software IO TLB: Memory encryption is active and system is using DMA bounce buffers [1.092105] Linux agpgart interface v0.103 [1.092716] BUG: unable to handle page fault for address: 9b820003d068 [1.093445] #PF: supervisor read access in kernel mode [1.093966] #PF: error_code(0x) - not-present page [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 8001001da067 PTE 8000fed40173 [1.094629] Oops: [#1] SMP NOPTI [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 0002 [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 9b820001ba90 [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 0f80 [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 8cc7068eca48 [1.094629] R13: 8cc700a64288 R14: R15: fed40080 [1.094629] FS: () GS:8cc77bd0() knlGS: [1.094629] CS: 0010 DS: ES: CR0: 80050033 [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 00350ee0 [1.094629] Call Trace: [1.094629] [1.094629] crb_map_io+0x315/0x870 [1.094629] ? radix_tree_iter_tag_clear+0x12/0x20 [1.094629] ? _raw_spin_unlock_irqrestore+0xe/0x30 [1.094629] crb_acpi_add+0xc2/0x140 [1.094629] acpi_device_probe+0x4c/0x170 [1.094629] really_probe+0x222/0x420 [1.094629] __driver_probe_device+0x119/0x190 [1.094629] driver_probe_device+0x23/0xc0 [1.094629] __driver_attach+0xbd/0x1e0 [1.094629] ? __device_attach_driver+0x120/0x120 [1.094629] bus_for_each_dev+0x7e/0xd0 [1.094629] driver_attach+0x1e/0x30 [1.094629] bus_add_driver+0x139/0x200 [1.094629] driver_register+0x95/0x100 [1.094629] ? init_tis+0xfd/0xfd [1.094629] acpi_bus_register_driver+0x39/0x50 [1.094629] crb_acpi_driver_init+0x15/0x1b [1.094629] do_one_initcall+0x48/0x1e0 [1.094629] do_initcalls+0x12f/0x159 [1.094629] kernel_init_freeable+0x162/0x1b5 [1.094629] ? rest_init+0x100/0x100 [1.094629] kernel_init+0x1b/0x150 [1.094629] ? rest_init+0x100/0x100 [1.094629] ret_from_fork+0x22/0x30 [1.094629] [1.094629] Modules linked in: [1.094629] CR2: 9b820003d068 [1.094629] ---[ end trace 3d6d81c42a3c2030 ]--- [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 0002 [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 9b820001ba90 [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 0f80 [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 8cc7068eca48 [1.094629] R13: 8cc700a64288 R14: R15: fed40080 [1.094629] FS: () GS:8cc77bd0() knlGS: [1.094629] CS: 0010 DS: ES: CR0: 80050033 [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 00350ee0 [1.094629] Kernel panic - not syncing: Attempted to kill init!
[Kernel-packages] [Bug 2027746] [NEW] package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl
Public bug reported: It occurs on start up[ ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 13 16:04:37 2023 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking libnvidia-compute-535-server:amd64 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 InstallationDate: Installed on 2023-06-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535-server Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-535-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-535-server in Ubuntu. https://bugs.launchpad.net/bugs/2027746 Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux- gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 Status in nvidia-graphics-drivers-535-server package in Ubuntu: New Bug description: It occurs on start up[ ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17 Uname: Linux 5.19.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Thu Jul 13 16:04:37 2023 DpkgTerminalLog: Preparing to unpack .../libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb ... Unpacking libnvidia-compute-535-server:amd64 (535.54.03-0ubuntu0.22.04.1) ... [1mdpkg:[0m error processing archive /var/cache/apt/archives/libnvidia-compute-535-server_535.54.03-0ubuntu0.22.04.1_amd64.deb (--unpack): trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 InstallationDate: Installed on 2023-06-23 (20 days ago) InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 (20230223) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RelatedPackageVersions: dpkg 1.21.1ubuntu2.2 apt 2.4.9 SourcePackage: nvidia-graphics-drivers-535-server Title: package libnvidia-compute-535-server 535.54.03-0ubuntu0.22.04.1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-pkcs11-openssl3.so.535.54.03', which is also in package libnvidia-extra-535:amd64 535.54.03-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-535-server/+bug/2027746/+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 2027744] Re: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2027744 Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Crash report appeared on my screen. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psingh 1537 F wireplumber /dev/snd/seq:psingh 1535 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 13 18:04:34 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-05-05 (69 days ago) InstallationMedia: Ubuntu 23.04.0 2023.05.04 amd64 "Custom Lunar Lobster" (20230504) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=18152a14-145a-4099-be2b-f93f2f37953d 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 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:sku1VW22AV: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dkms/+bug/2027744/+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 2027744] [NEW] package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
Public bug reported: Crash report appeared on my screen. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psingh 1537 F wireplumber /dev/snd/seq:psingh 1535 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 13 18:04:34 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-05-05 (69 days ago) InstallationMedia: Ubuntu 23.04.0 2023.05.04 amd64 "Custom Lunar Lobster" (20230504) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=18152a14-145a-4099-be2b-f93f2f37953d 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 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.43:bd12/15/2020:br15.43:efr95.11:svnHP:pnHPSpectrex360Convertible15-bl1XX:pvr:rvnHP:rn827F:rvr95.11:cvnHP:ct31:cvrChassisVersion:sku1VW22AV: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 15-bl1XX dmi.product.sku: 1VW22AV dmi.sys.vendor: HP ** Affects: dkms (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/2027744 Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 Status in dkms package in Ubuntu: New Bug description: Crash report appeared on my screen. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psingh 1537 F wireplumber /dev/snd/seq:psingh 1535 F pipewire CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 13 18:04:34 2023 ErrorMessage: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 InstallationDate: Installed on 2023-05-05 (69 days ago) InstallationMedia: Ubuntu 23.04.0 2023.05.04 amd64 "Custom Lunar Lobster" (20230504) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 064e:3401 Suyin Corp. HP TrueVision FHD RGB-IR Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Spectre x360 Convertible 15-bl1XX ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=18152a14-145a-4099-be2b-f93f2f37953d 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 2.06-2ubuntu16 SourcePackage: dkms Title: package linux-image-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/dkms exited with return code 11 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/15/2020 dmi.bios.release: 15.43 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.43 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827F dmi.board.vendor: HP dmi.board.version: 95.11 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 95.11 dmi.modalias:
[Kernel-packages] [Bug 1998643] Re: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices
doesn't apply to iotg or tegra kernels ** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1998643 Title: smartpqi: Update 22.04 driver to include recent bug fixes and support current generation devices Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Released Bug description: [Impact] These patches provide bug fixes and add support for the latest generation of OEM PCI devices to ensure customers are able to use Jammy on the recent generations of server hardware. This will bring us in line with the other major linux distros. [Fix] There are some outstanding patches already in Linus's tree that can be applied to 22.04. git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git The following patches apply to https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/jammy f54f85dfd757 scsi: smartpqi: Update version to 2.1.18-045 e4b73b3fa2b9 scsi: smartpqi: Update copyright to current year 6d567dfee0b7 scsi: smartpqi: Add ctrl ready timeout module parameter 2d80f4054f7f scsi: smartpqi: Update deleting a LUN via sysfs cf15c3e734e8 scsi: smartpqi: Add module param to disable managed ints 6ce3cfb365eb scsi: smartpqi: Fix RAID map race condition 69695aeaa662 scsi: smartpqi: Fix DMA direction for RAID requests 85b41834b0f4 scsi: smartpqi: Stop logging spurious PQI reset failures 2a9c2ba2bc47 scsi: smartpqi: Add PCI IDs for Lenovo controllers 44e68c4af5d2 scsi: smartpqi: Add PCI ID for Adaptec SmartHBA 2100-8i 331f7e998b20 scsi: smartpqi: Fix PCI control linkdown system hang 904f2bfda65e scsi: smartpqi: Add driver support for multi-LUN devices 297bdc540f0e scsi: smartpqi: Close write read holes dab5378485f6 scsi: smartpqi: Add PCI IDs for ramaxel controllers 1d393227fc76 scsi: smartpqi: Add controller fw version to console log 4e7d26029ee7 scsi: smartpqi: Shorten drive visibility after removal 8946ea283808 scsi: smartpqi: Fix typo in comment c1ea387d998a scsi: smartpqi: Stop using the SCSI pointer 31b17c3aeb5e scsi: smartpqi: Fix unused variable pqi_pm_ops for clang 62ed6622aaf0 scsi: smartpqi: Update version to 2.1.14-035 291c2e0071ef scsi: smartpqi: Fix lsscsi -t SAS addresses c66e078ad89e scsi: smartpqi: Fix hibernate and suspend 5e6935864d81 scsi: smartpqi: Fix BUILD_BUG_ON() statements c52efc923856 scsi: smartpqi: Fix NUMA node not updated during init 00598b056aa6 scsi: smartpqi: Expose SAS address for SATA drives 5d8fbce04d36 scsi: smartpqi: Speed up RAID 10 sequential reads 27655e9db479 scsi: smartpqi: Update volume size after expansion b73357a1fd39 scsi: smartpqi: Avoid drive spin-down during suspend 42dc0426fbbb scsi: smartpqi: Resolve delay issue with PQI_HZ value 9e98e60bfca3 scsi: smartpqi: Fix a typo in func pqi_aio_submit_io() b4dc06a9070e scsi: smartpqi: Fix a name typo and cleanup code 94a68c814328 scsi: smartpqi: Quickly propagate path failures to SCSI midlayer 70ba20be4bb1 scsi: smartpqi: Eliminate drive spin down on warm boot 2a47834d9452 scsi: smartpqi: Enable SATA NCQ priority in sysfs c57ee4ccb358 scsi: smartpqi: Add PCI IDs c4ff687d25c0 scsi: smartpqi: Fix rmmod stack trace 64fc9015fbeb scsi: smartpqi: Switch to attribute groups 0ca190805784 scsi: smartpqi: Call scsi_done() directly I added the above SHA1 IDs to a file called: backport_linus_6.1_into_22.04 git-backport --sort -d /tmp/patches ../backport_linus_6.1_into_22.04 git am -s /tmp/patches/*.diff All patches applied without any conflicts. [Test Plan] The upstream driver has undergone extensive testing by Microchip's test team before submitting those patches to the upstream kernel. All patches are tested and accepted in the upstream kernel at this time. One should be able to load the smartpqi driver and verify the version is at 2.1.18-045 [Other Info] https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/smartpqi_2204_3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998643/+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 2027615] Re: Azure: MANA: Fix doorbell access for receives
** 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/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+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 2027615] Re: Azure: MANA: Fix doorbell access for receives
** Changed in: linux-azure (Ubuntu Lunar) 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/2027615 Title: Azure: MANA: Fix doorbell access for receives Status in linux-azure package in Ubuntu: New Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Lunar: Fix Committed Bug description: SRU Justification [Impact] It's inefficient to ring the doorbell page every time a WQE is posted to the received queue. Excessive MMIO writes result in CPU spending more time waiting on LOCK instructions (atomic operations), resulting in poor scaling performance. [Test Plan] MSFT tested. [Regression Potential] The MANA receive queue could stop. [Other Info] SF: #00363437 These 2 patches have been submitted for upstream inclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/2027615/+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 2020319] Re: Encountering an issue with memcpy_fromio causing failed boot of SEV-enabled guest
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu) Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2020319 Title: Encountering an issue with memcpy_fromio causing failed boot of SEV- enabled guest Status in linux package in Ubuntu: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux source package in Focal: Fix Committed Status in linux-gcp source package in Focal: New Status in linux source package in Jammy: Fix Committed Status in linux-gcp source package in Jammy: In Progress Bug description: [Impact] When launching a SEV-enabled guest, the guest kernel panics with the following call trace, indicating a critical error in the system. == [1.090638] software IO TLB: Memory encryption is active and system is using DMA bounce buffers [1.092105] Linux agpgart interface v0.103 [1.092716] BUG: unable to handle page fault for address: 9b820003d068 [1.093445] #PF: supervisor read access in kernel mode [1.093966] #PF: error_code(0x) - not-present page [1.094481] PGD 80010067 P4D 80010067 PUD 8001001d7067 PMD 8001001da067 PTE 8000fed40173 [1.094629] Oops: [#1] SMP NOPTI [1.094629] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 5.15.0-46-generic #49-Ubuntu [1.094629] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015 [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 0002 [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 9b820001ba90 [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 0f80 [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 8cc7068eca48 [1.094629] R13: 8cc700a64288 R14: R15: fed40080 [1.094629] FS: () GS:8cc77bd0() knlGS: [1.094629] CS: 0010 DS: ES: CR0: 80050033 [1.094629] CR2: 9b820003d068 CR3: 800174a1 CR4: 00350ee0 [1.094629] Call Trace: [1.094629] [1.094629] crb_map_io+0x315/0x870 [1.094629] ? radix_tree_iter_tag_clear+0x12/0x20 [1.094629] ? _raw_spin_unlock_irqrestore+0xe/0x30 [1.094629] crb_acpi_add+0xc2/0x140 [1.094629] acpi_device_probe+0x4c/0x170 [1.094629] really_probe+0x222/0x420 [1.094629] __driver_probe_device+0x119/0x190 [1.094629] driver_probe_device+0x23/0xc0 [1.094629] __driver_attach+0xbd/0x1e0 [1.094629] ? __device_attach_driver+0x120/0x120 [1.094629] bus_for_each_dev+0x7e/0xd0 [1.094629] driver_attach+0x1e/0x30 [1.094629] bus_add_driver+0x139/0x200 [1.094629] driver_register+0x95/0x100 [1.094629] ? init_tis+0xfd/0xfd [1.094629] acpi_bus_register_driver+0x39/0x50 [1.094629] crb_acpi_driver_init+0x15/0x1b [1.094629] do_one_initcall+0x48/0x1e0 [1.094629] do_initcalls+0x12f/0x159 [1.094629] kernel_init_freeable+0x162/0x1b5 [1.094629] ? rest_init+0x100/0x100 [1.094629] kernel_init+0x1b/0x150 [1.094629] ? rest_init+0x100/0x100 [1.094629] ret_from_fork+0x22/0x30 [1.094629] [1.094629] Modules linked in: [1.094629] CR2: 9b820003d068 [1.094629] ---[ end trace 3d6d81c42a3c2030 ]--- [1.094629] RIP: 0010:memcpy_fromio+0x27/0x50 [1.094629] Code: cc cc cc 0f 1f 44 00 00 55 48 89 e5 48 85 d2 74 28 40 f6 c6 01 75 30 48 83 fa 01 76 06 40 f6 c6 02 75 1c 48 89 d1 48 c1 e9 02 a5 f6 c2 02 74 02 66 a5 f6 c2 01 74 01 a4 5d e9 14 b3 97 00 66 [1.094629] RSP: 0018:9b820001ba50 EFLAGS: 00010212 [1.094629] RAX: 9b820003d040 RBX: 9b820001bac0 RCX: 0002 [1.094629] RDX: 0008 RSI: 9b820003d068 RDI: 9b820001ba90 [1.094629] RBP: 9b820001ba50 R08: 0f80 R09: 0f80 [1.094629] R10: fed40080 R11: 9b820001bac0 R12: 8cc7068eca48 [1.094629] R13: 8cc700a64288 R14: R15:
[Kernel-packages] [Bug 2027567] Re: No more HDMI
And I also cannot log in here: https://discourse.ubuntu.com -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 2027567] Re: No more HDMI
I wanted to correct the wiki by updating the PPA here: https://wiki.ubuntu.com/Kernel/FAQ But when I try to login to the wiki using Ubuntu One it says invalid email/password combination. But it is exactly the same email/password combination that I use for launchpad.net. Is the wiki limited to Ubuntu staff? -- 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/2027567 Title: No more HDMI Status in linux package in Ubuntu: New Bug description: Hello, Thanks for your hard work :) I just upgraded to kernel 6.2.0-25. There is no more HDMI and my external screen can not be used. Moreover, when I stop my laptop, it takes 30s. If I switch back to 6.2.0-24 the HDMI works again and stopping my laptop takes a few seconds. I'll join screenshots of command: ls /sys/class/drm/* Thanks, best regards, Laurent Lyaudet ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: linux-image-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laurent5201 F wireplumber /dev/snd/controlC1: laurent5201 F wireplumber /dev/snd/seq:laurent5192 F pipewire CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 11:34:15 2023 InstallationDate: Installed on 2020-07-01 (1105 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Micro-Star International Co., Ltd. GL73 8SD ProcEnviron: LANG=fr_FR.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=894d943a-5e5a-4980-96c2-64d37638009d ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-6.2.0-25-generic N/A linux-backports-modules-6.2.0-25-generic N/A linux-firmware20230323.gitbcdcfbcf-0ubuntu1.2 SourcePackage: linux UpgradeStatus: Upgraded to lunar on 2023-04-22 (80 days ago) dmi.bios.date: 03/29/2019 dmi.bios.release: 1.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E17C7IMS.10E dmi.board.asset.tag: Default string dmi.board.name: MS-17C7 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE17C7IMS.10E:bd03/29/2019:br1.14:svnMicro-StarInternationalCo.,Ltd.:pnGL738SD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-17C7:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku17C7.1: dmi.product.family: GL dmi.product.name: GL73 8SD dmi.product.sku: 17C7.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027567/+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 1970957] Re: suspend problem
I am experiencing a similar issue on ThinkPad t460s suspend works the majority of the time, but every few days, I will try to wake up from suspend and get input/output errors on everything. I am able to wake the machine and log in, but can't do anything from there but force a restart from the command line or by holding the power button. I'm on the latest Ubuntu 22.04.2. The issue only started happening after upgrading from 20.04 to 22.04 in the past 2 months. I've run fsck on the drive. It fixed many errors, but the problem persists. I re-ran fsck just to check, and the drive is still clean without errors. Ubuntu 22.04.2 5.15.0-76-generic Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz -- 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/1970957 Title: suspend problem Status in linux package in Ubuntu: Confirmed Bug description: I've installed Ubuntu 22.04 on the ThinkPad E480. Suspend functions ok intermittently. Some times it works fine, other times the computer does not enter the suspend mode (the screen gets blank, but the machine is still running and the ThinPad led is on, and there is no way out... no response from keyboard or mouse... the only solution is to switch off manually hitting and holding the power button), other times the machine does not wakes up from suspension mode. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: ubuntu-release-upgrader-core 1:22.04.10 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 10:53:59 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: leoca 1913 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 EcryptfsInUse: Yes InstallationDate: Installed on 2022-04-24 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) MachineType: LENOVO 20KQ000EBR Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=1e7d6212-699d-4319-b137-8a7059545433 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 RelatedPackageVersions: linux-restricted-modules-5.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 Tags: jammy Uname: Linux 5.15.0-27-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/14/2018 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: R0PET42W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KQ000EBR dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.19 dmi.modalias: dmi:bvnLENOVO:bvrR0PET42W(1.19):bd06/14/2018:br1.19:efr1.19:svnLENOVO:pn20KQ000EBR:pvrThinkPadE480:rvnLENOVO:rn20KQ000EBR:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20KQ_BU_Think_FM_ThinkPadE480: dmi.product.family: ThinkPad E480 dmi.product.name: 20KQ000EBR dmi.product.sku: LENOVO_MT_20KQ_BU_Think_FM_ThinkPad E480 dmi.product.version: ThinkPad E480 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970957/+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 2022887] Re: add Fintek F81604 can controller support
** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2022887 Title: add Fintek F81604 can controller support Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: Fix Committed Bug description: [Impact] add Fintek F81604 can controller support [Test Plan] 1. compile test. 2. check f81604 can controller functionalities on the hardware. 3. test kernel is provided to the customer. [Regression potential] Low. one new driver is backported. the others are code revised and bug fixed, although they touch all the existent can drivers. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2022887/+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 1921536] Re: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch
> sudo apt install nvidia-driver-535 linux-modules-nvidia-535-generic > sudo apt remove nvidia-dkms-535 Not changing anything! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1921536 Title: "modprobe: ERROR: could not insert 'nvidia': Key was rejected by service" due to binutils mismatch Status in linux package in Ubuntu: Confirmed Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-525 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: Confirmed Bug description: If a user does not have the same version of binutils installed as the one used to produce the nvidia module signature, the module generated at postinst maybe unloadable: modprobe: ERROR: could not insert 'nvidia': Key was rejected by service I ran into this when I tried to install the hirsute kernel/nvidia driver on a focal system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921536/+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 2019011] Re: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver
This bug is awaiting verification that the linux/5.4.0-155.172 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- 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/2019011 Title: [UBUNTU 20.04] [HPS] Kernel panic with "refcount_t: underflow" in mlx5 driver Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Bug description: SRU Justification: == [ Impact ] * The mlx5 driver is causing a Kernel panic with "refcount_t: underflow". * This issue occurs during a recovery when the PCI device is isolated and thus doesn't respond. [ Fix ] * This issue got solved upstream with aaf2e65cac7f aaf2e65cac7f2e1ae729c2fbc849091df9699f96 "net/mlx5: Fix handling of entry refcount when command is not issued to FW" (upstream since 6.1-rc1) * But to get aaf2e65cac7f a backport of b898ce7bccf1 b898ce7bccf13087719c021d829dab607c175246 "net/mlx5: cmdif, Avoid skipping reclaim pages if FW is not accessible" is required on top (upstream since 5.10) [ Test Plan ] * An Ubuntu Server for s390x 20.04 LPAR or z/VM installation is needed that has Mellanox cards (RoCE Express 2.1) assigned, configured and enabled and that runs a 5.4 kernel with mlx5 driver. * Create some network traffic on (one of the) RoCE device (interface ens???[d?]) for testing (e.g. with stress-ng). * Make sure the module/driver mlx5 is loaded and in use. * Trigger a recovery (via the Support Element) that will render the adapter (ports) unresponsive for a moment and should provoke a similar situation. * Alternatively the interface itself can be removed for a moment and re-added again (but this may break further things on top). * Due to the lack of RoCE Express 2.1 hardware, the verification is on IBM. [ Where problems could occur ] * The modifications are limited to the Mellanox mlx5 driver only - no other network driver is affected. * The pre-required commit (aaf2e65cac7f) can have a bad impact on (re-)claiming pages if FW is not accessible, which could cause page leaks in case done wrong. But this commit is pretty save since it's upstream since v5.10. * The fix itself (aaf2e65cac7f) mainly changes the cmd_work_handler and mlx5_cmd_comp_handler functions in a way that instead of pci_channel_offline mlx5_cmd_is_down (introiduced by b898ce7bccf1). * Actually b898ce7bccf1 started with changing from pci_channel_offline to mlx5_cmd_is_down, but looks like a few cases (in the area of refcount increate/decrease) were missed, that are now covered by aaf2e65cac7f. * It fixes now on top refcounts are now always properly increment and decrement to achieve a symmetric state for all flows. * These changes may have an impact on all cases where the mlx5 device is not responding, which can happen in case of an offline channel, interface down, reset or recovery. [ Other Info ] * Looking at the master-next git trees for jammy, kinetic and lunar showed that both fixes are already included, hence only focal is affected. __ ---Problem Description--- Kernel panic with "refcount_t: underflow" in kernel log Contact Information = rijo...@ibm.com, vineeth.vija...@ibm.com ---uname output--- 5.4.0-128-generic Machine Type = s390x ---System Hang--- Kernel panic and stack-trace as below ---Debugger--- A debugger is not configured Stack trace output: [Sat Apr 8 17:52:21 UTC 2023] Call Trace: [Sat Apr 8 17:52:21 UTC 2023] ([<002a5939a286>] refcount_warn_saturate+0xce/0x140) [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f861e>] cmd_ent_put+0xe6/0xf8 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9b6a>] mlx5_cmd_comp_handler+0x102/0x4f0 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<03ff805f9f8a>] cmd_comp_notifier+0x32/0x48 [mlx5_core] [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf0c6>] notifier_call_chain+0x4e/0xa0 [Sat Apr 8 17:52:21 UTC 2023] [<002a58ecf17e>] atomic_notifier_call_chain+0x2e/0x40 [Sat Apr 8 17:52:21 UTC 2023] [<03ff805fe4fc>]
[Kernel-packages] [Bug 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
This bug is awaiting verification that the linux/5.4.0-155.172 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-focal-linux verification-needed-focal -- 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/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+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 2023807] Re: Initialize linux-nvidia-tegra-igx with patch list from NVIDIA
** Package changed: linux-nvidia-tegra (Ubuntu) => linux-nvidia-tegra- igx (Ubuntu) ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia-tegra in Ubuntu. https://bugs.launchpad.net/bugs/2023807 Title: Initialize linux-nvidia-tegra-igx with patch list from NVIDIA Status in linux-nvidia-tegra-igx package in Ubuntu: New Bug description: [Impact] This change reflects the creation and initialization of a new kernel, linux-nvidia-tegra-igx. This kernel will be initialized with the patches already in linux-nvidia-tegra, and be maintained as a sibling to linux-nvidia-tegra. A patch list containing patches required to enable the IGX platform has been provided by NVIDIA, and these patches have been integrated into the new kernel. [Other Info] The following patches are contained in the NVIDIA-provided list, but need backporting to v5.15. 8681e3663411 drm/simpledrm: Support the XB24/AB24 format 9abecb1d338c drm/format-helper: Support the XB24 format 9a10c7e6519b drm/simpledrm: Add support for system memory framebuffers fa904b4cbc60 drm/simpledrm: Use struct iosys_map consistently Hence, these will be addressed in a separate change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia-tegra-igx/+bug/2023807/+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 2027708] Re: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess r
** Tags removed: need-duplicate-check -- 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/2027708 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: was playing mount and blade got it work before but now its not working has me confused got and error report finally with this info wondering If I broke it somehow when I compiled drivers. If you don't mind taking a look I know its silly to ask help for a proton windows compatibility error with mount and blade bannerlord but I really like playing this on ubuntu and I think this kind of stuff improoves ubuntu overall. I am having trouble with one vulkan library says unable to determine path to install libglvnd or pkg-config specify path --glvnd-egl-config-path. i entered --glvnd-egl-config-path into a terminal it said cannot find so i wondered i install a cuda library as well and i get superior performance on vulkan compatable games like AMAZING RESULTS gave me such happiness. but i wondered why mount and blade isnt working. space engineers and planetary anihilationa nd mechwarrior online works in full detail physics and best performance ive ever seen. but this one leaves me stumped and perplexed. my card is a nivdia gtx 3050 zotac twin edge. i installed the vulkan driver in the root terminal with the # with no gui loaded. and the cuda library causually beforehand with the $ while nouvea was enabled. now it shows a manually insttalled driver which is the vulkan driver. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 13 07:01:11 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-11 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=3cbda6b7-9865-4de0-9758-bf5477284ff1 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-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING A520M-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd02/24/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGA520M-PLUSWIFI:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027708/+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 2027708] [NEW] package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess
Public bug reported: was playing mount and blade got it work before but now its not working has me confused got and error report finally with this info wondering If I broke it somehow when I compiled drivers. If you don't mind taking a look I know its silly to ask help for a proton windows compatibility error with mount and blade bannerlord but I really like playing this on ubuntu and I think this kind of stuff improoves ubuntu overall. I am having trouble with one vulkan library says unable to determine path to install libglvnd or pkg-config specify path --glvnd-egl-config-path. i entered --glvnd-egl-config-path into a terminal it said cannot find so i wondered i install a cuda library as well and i get superior performance on vulkan compatable games like AMAZING RESULTS gave me such happiness. but i wondered why mount and blade isnt working. space engineers and planetary anihilationa nd mechwarrior online works in full detail physics and best performance ive ever seen. but this one leaves me stumped and perplexed. my card is a nivdia gtx 3050 zotac twin edge. i installed the vulkan driver in the root terminal with the # with no gui loaded. and the cuda library causually beforehand with the $ while nouvea was enabled. now it shows a manually insttalled driver which is the vulkan driver. ProblemType: Package DistroRelease: Ubuntu 23.04 Package: linux-headers-6.2.0-25-generic 6.2.0-25.25 ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12 Uname: Linux 6.2.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass Date: Thu Jul 13 07:01:11 2023 ErrorMessage: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2023-07-11 (1 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) MachineType: ASUS System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic root=UUID=3cbda6b7-9865-4de0-9758-bf5477284ff1 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-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2023 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING A520M-PLUS WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd02/24/2023:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGA520M-PLUSWIFI:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lunar -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2027708 Title: package linux-headers-6.2.0-25-generic 6.2.0-25.25 failed to install/upgrade: installed linux-headers-6.2.0-25-generic package post-installation script subprocess returned error exit status 1 Status in linux package in Ubuntu: New Bug description: was playing mount and blade got it work before but now its not working has me confused got and error report finally with this info wondering If I broke it somehow when I compiled drivers. If you don't mind taking a look I know its silly to ask help for a proton windows compatibility error with mount and blade bannerlord but I really like playing this on ubuntu and I think this kind of stuff improoves ubuntu overall. I am having trouble with one vulkan library says unable to determine path to install libglvnd or pkg-config specify path --glvnd-egl-config-path. i entered --glvnd-egl-config-path into a terminal it said cannot find so i wondered i install a cuda library as well and i get superior performance on vulkan compatable games like AMAZING RESULTS gave me such happiness. but i wondered why mount and blade isnt working. space engineers and planetary anihilationa nd mechwarrior online works in full detail physics and best performance ive ever seen. but this one leaves me stumped and perplexed. my card is a nivdia gtx 3050 zotac twin edge. i installed the vulkan driver in the root
[Kernel-packages] [Bug 2026229] Re: Crashing issue with 5.15 kernel
@kleber-souza do you have any reference for which kind of bugs were resolved between 5.15.0-73-generic and 5.15.0-76.83 that might have addressed this? Our testing indicates that the newer kernel version is stable. It would be good to know what specifically caused this issue -- 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 2020469] Re: Package ppc64el/s390x signing certs
Thx for the diff, xnox. I've incl. it in the latest v2.28 and kicked off a PPA test build, available here: https://launchpad.net/~fheimes/+archive/ubuntu/lp2020469 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2020469 Title: Package ppc64el/s390x signing certs Status in Ubuntu CD Images: New Status in Ubuntu on IBM z Systems: New Status in linux-signed package in Ubuntu: Incomplete Status in s390-tools-signed package in Ubuntu: New Bug description: Package ppc64el/s390x signing certs For ease of using signed boot on opal & sipl platforms, package and expose the signing certificate in .pem format in the .deb packages and on the isos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+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 1942935] Re: kernel io hangs during mdcheck/resync
I can't add much in terms of data. But this is a +1. My symptoms were virtually identical to Chad Wagner's This happened july 1st 2023 on my machine, the day the check started. It got stuck at 98%. Only cure I could find was to reboot the system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1942935 Title: kernel io hangs during mdcheck/resync Status in linux package in Ubuntu: Confirmed Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Status in linux-signed-hwe-5.15 package in Ubuntu: New Status in linux-signed-hwe-5.4 package in Ubuntu: Confirmed Bug description: It seems to always occur during an mdcheck/resync, if I am logged in via SSH it is still somewhat responsive and basic utilities like dmesg will work. But it apppears any write I/O will hang the terminal and nothing is written to syslog (presumably because it is blocked). Below is output of dmesg and cat /proc/mdstat, it appears the data check was interrupted and /proc/mdstat still shows progress, and a whole slew of hung tasks including md1_resync itself. [756484.534293] md: data-check of RAID array md0 [756484.628039] md: delaying data-check of md1 until md0 has finished (they share one or more physical units) [756493.808773] md: md0: data-check done. [756493.829760] md: data-check of RAID array md1 [778112.446410] md: md1: data-check interrupted. [810654.608102] md: data-check of RAID array md1 [832291.201064] md: md1: data-check interrupted. [899745.389485] md: data-check of RAID array md1 [921395.835305] md: md1: data-check interrupted. [921588.558834] INFO: task systemd-journal:376 blocked for more than 120 seconds. [921588.558846] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.558850] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.558854] task:systemd-journal state:D stack:0 pid: 376 ppid: 1 flags:0x0220 [921588.558859] Call Trace: [921588.558864] __schedule+0x44c/0x8a0 [921588.558872] schedule+0x4f/0xc0 [921588.558876] md_write_start+0x150/0x240 [921588.558880] ? wait_woken+0x80/0x80 [921588.558886] raid5_make_request+0x88/0x890 [raid456] [921588.558898] ? wait_woken+0x80/0x80 [921588.558901] ? mempool_kmalloc+0x17/0x20 [921588.558904] md_handle_request+0x12d/0x1a0 [921588.558907] ? __part_start_io_acct+0x51/0xf0 [921588.558912] md_submit_bio+0xca/0x100 [921588.558915] submit_bio_noacct+0x112/0x4f0 [921588.558918] ? ext4_fc_reserve_space+0x110/0x230 [921588.558922] submit_bio+0x51/0x1a0 [921588.558925] ? _cond_resched+0x19/0x30 [921588.558928] ? kmem_cache_alloc+0x38e/0x440 [921588.558932] ? ext4_init_io_end+0x1f/0x50 [921588.558936] ext4_io_submit+0x4d/0x60 [921588.558940] ext4_writepages+0x2c6/0xcd0 [921588.558944] do_writepages+0x43/0xd0 [921588.558948] ? do_writepages+0x43/0xd0 [921588.558951] ? fault_dirty_shared_page+0xa5/0x110 [921588.558955] __filemap_fdatawrite_range+0xcc/0x110 [921588.558960] file_write_and_wait_range+0x74/0xc0 [921588.558962] ext4_sync_file+0xf5/0x350 [921588.558967] vfs_fsync_range+0x49/0x80 [921588.558970] do_fsync+0x3d/0x70 [921588.558973] __x64_sys_fsync+0x14/0x20 [921588.558976] do_syscall_64+0x38/0x90 [921588.558980] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [921588.558984] RIP: 0033:0x7f4c97ee832b [921588.558987] RSP: 002b:7ffdceb29e50 EFLAGS: 0293 ORIG_RAX: 004a [921588.558991] RAX: ffda RBX: 55ced34b0fa0 RCX: 7f4c97ee832b [921588.558993] RDX: 7f4c97fc8000 RSI: 55ced3487b70 RDI: 0021 [921588.558995] RBP: 0001 R08: R09: 7ffdceb29fa8 [921588.558996] R10: 7f4c97d2c848 R11: 0293 R12: 7ffdceb29fa8 [921588.558998] R13: 7ffdceb29fa0 R14: 55ced34b0fa0 R15: 55ced34bcf90 [921588.559014] INFO: task mysqld:1505 blocked for more than 120 seconds. [921588.559018] Not tainted 5.11.0-27-generic #29~20.04.1-Ubuntu [921588.559022] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [921588.559025] task:mysqld state:D stack:0 pid: 1505 ppid: 1 flags:0x [921588.559030] Call Trace: [921588.559032] __schedule+0x44c/0x8a0 [921588.559036] schedule+0x4f/0xc0 [921588.559040] md_write_start+0x150/0x240 [921588.559044] ? wait_woken+0x80/0x80 [921588.559047] raid5_make_request+0x88/0x890 [raid456] [921588.559056] ? wait_woken+0x80/0x80 [921588.559059] ? mempool_kmalloc+0x17/0x20 [921588.559062] md_handle_request+0x12d/0x1a0 [921588.559065] ? __part_start_io_acct+0x51/0xf0 [921588.559068] md_submit_bio+0xca/0x100 [921588.559071] submit_bio_noacct+0x112/0x4f0 [921588.559075] submit_bio+0x51/0x1a0 [921588.559077] ? _cond_resched+0x19/0x30
[Kernel-packages] [Bug 2019000] Re: Use new annotations model
** Also affects: linux-gcp (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-gcp (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: linux-gcp (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-gcp (Ubuntu Jammy) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-gcp (Ubuntu Kinetic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux-gcp (Ubuntu Jammy) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/2019000 Title: Use new annotations model Status in linux package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux source package in Focal: Triaged Status in linux-gcp source package in Focal: New Status in linux source package in Jammy: Fix Released Status in linux-gcp source package in Jammy: Fix Committed Status in linux source package in Kinetic: Confirmed Status in linux-gcp source package in Kinetic: Invalid Bug description: [Impact] Starting with lunar we have introduced a new way to manage kernel configs, unifying the duplicated information defined in the annotations file + config chunks into an annotations-only model. [Test case] A kernel build can be considered a valid test case, in particular the specific command that is used to update the .config's for all the supported architectures and flavours: $ fakeroot debian/rules updateconfigs [Fix] Import the required changes in debian/ from lunar (with the required adjustments) to support the annotations-only model also in all the previous releases. [Regression potential] We may experience regressions during the updateconfigs step, especially with derivatives. Moreover, derivatives that want to transition to the new annotations model require to adjust the header in the annotations file as following (make sure to define the corresponding architectures and flavours): # FORMAT: 4 # ARCH: amd64 arm64 armhf ppc64el s390x # FLAVOUR: amd64-generic amd64-lowlatency arm64-generic arm64-generic-64k arm64-lowlatency arm64-lowlatency-64k armhf-generic armhf-generic-lpae ppc64el-generic s390x-generic After adjusting the header a special command is provided to transition to the new annotations-only model: $ fakeroot debian/rules migrateconfigs This command should automatically import the old configs into the new annotations file. A kernel with this change applied can still support the old annotations+configs model, the transition to the new model is not mandatory. Basically without using `fakeroot debian/rules migrateconfigs` the updateconfigs step will continue to use the old model and the old scripts (that is the safest approach to avoid potential unexpected .config changes). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019000/+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 2022887] Re: add Fintek F81604 can controller support
** Description changed: - [Summary] + [Impact] + add Fintek F81604 can controller support - adds support for Fintek USB to 2CAN controller + [Test Plan] + 1. compile test. + 2. check f81604 can controller functionalities on the hardware. + 3. test kernel is provided to the customer. + + [Regression potential] + Low. one new driver is backported. the others are code revised and bug + fixed, although they touch all the existent can drivers. + + [Other info] + https://git.launchpad.net/~jianhuilee/ubuntu/+source/linux-intel-iotg/+git/jammy-iotg/log/?h=f81604-enable ** Description changed: [Impact] add Fintek F81604 can controller support [Test Plan] 1. compile test. 2. check f81604 can controller functionalities on the hardware. 3. test kernel is provided to the customer. [Regression potential] Low. one new driver is backported. the others are code revised and bug fixed, although they touch all the existent can drivers. [Other info] - https://git.launchpad.net/~jianhuilee/ubuntu/+source/linux-intel-iotg/+git/jammy-iotg/log/?h=f81604-enable -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2022887 Title: add Fintek F81604 can controller support Status in linux-intel-iotg package in Ubuntu: Invalid Status in linux-intel-iotg source package in Jammy: New Bug description: [Impact] add Fintek F81604 can controller support [Test Plan] 1. compile test. 2. check f81604 can controller functionalities on the hardware. 3. test kernel is provided to the customer. [Regression potential] Low. one new driver is backported. the others are code revised and bug fixed, although they touch all the existent can drivers. [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-intel-iotg/+bug/2022887/+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 1981087] Re: thermald prematurely throttling GPU
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Fri Jul 8 16:08:55 2022 InstallationDate: Installed on 2020-10-19 (626 days ago) InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: thermald UpgradeStatus: Upgraded to jammy on 2022-06-17 (20 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1981087/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
I'm setting the importance to Critical per #6 at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: mutter (Ubuntu Jammy) Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2020469] Re: Package ppc64el/s390x signing certs
** Tags added: s390x ** Also affects: ubuntu-z-systems Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/2020469 Title: Package ppc64el/s390x signing certs Status in Ubuntu CD Images: New Status in Ubuntu on IBM z Systems: New Status in linux-signed package in Ubuntu: Incomplete Status in s390-tools-signed package in Ubuntu: New Bug description: Package ppc64el/s390x signing certs For ease of using signed boot on opal & sipl platforms, package and expose the signing certificate in .pem format in the .deb packages and on the isos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/2020469/+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
It seems like NVIDIA Driver metapackage 535 leads to kernel panics in my case while NVIDIA Driver metapackage 525 works fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/2025538 Title: Unrequested kernel update Status in linux-restricted-modules package in Ubuntu: Triaged Status in linux-signed-nvidia-5.19 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-535 package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: Triaged 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-restricted-modules/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
** Description changed: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... + + For kinetic: The bug never existed in mutter 43.0 (it was introduced in + 43.2) and was already fixed in the kernel anyway. + + For lunar and later: The bug was already fixed in the kernel. You would + only ever encounter it in theory if you downgrade the kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
Fix proposed: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/100 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+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 2027645] Re: [Lenovo Legion 5] Brightness option is not working and not showing in system menu
** Changed in: linux (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/2027645 Title: [Lenovo Legion 5] Brightness option is not working and not showing in system menu Status in linux package in Ubuntu: Incomplete Bug description: The ubuntu version is automatic updated and then i am facing this issue that there is not britness control is there in my system ment and my briness key also not wokring ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 09:44:30 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027645/+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 1981087] Re: thermald prematurely throttling GPU
Verified with unigine-super of phoronix-test-suite ~~~ $phoronix-test-suite benchmark unigine-super ~~~ didn't observe the significant difference compared to upstream thermald 2.5.3. ~~~ - thermald-2.4.9_1ubuntu-0.3 > > > > Unigine Superposition 1.0: > pts/unigine-super-1.0.8 [Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL] > Test 1 of 1 > Estimated Trial Run Count:3 > > Estimated Time To Completion: 13 Minutes [03:40 CDT] > Started Run 1 @ 03:28:08 > Started Run 2 @ 03:31:37 > Started Run 3 @ 03:35:03 > > ``` > Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL: > 4.6 > 4.6 > 4.6 > > Average: 4.6 Frames Per Second > Maximum: 5.4 > Deviation: 0.00% > > Comparison of 1,233 OpenBenchmarking.org samples since 14 June 2018; median result: 70.5 Frames Per Second. Box plot of samples: > [ *--!###*##*#*#*---*-*--*-*| * ] > ^ This Result (2nd Percentile): 4.6 > Arc A770 DG2: 101 ^ RTX 3080: 147 ^ RX 6900 XT: 199 ^ > Arc A750 DG2: 96 ^ Gigabyte RX 6800 XT: 177 ^ > RTX 2070 SUPER: 91 ^ RTX 3090: 173 ^ > RX 5700 XT: 81 ^ Gigabyte RX 6800: 163 ^ > ``` > ~~~ - upstream thermald 2.5.3, > Unigine Superposition 1.0: pts/unigine-super-1.0.8 [Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL] Test 1 of 1 Estimated Trial Run Count:3 > > Estimated Time To Completion: 11 Minutes [03:49 CDT] Started Run 1 @ 03:39:42 Started Run 2 @ 03:43:08 Started Run 3 @ 03:46:35 > > Resolution: 1920 x 1080 - Mode: Fullscreen - Quality: High - Renderer: OpenGL: 4.7 4.7 4.7 Average: 4.7 Frames Per Second Maximum: 5.4 Deviation: 0.00% Comparison of 1,233 OpenBenchmarking.org samples since 14 June 2018; median result: 70.5 Frames Per Second. Box plot of samples: [ *--!###*##*#*#*---*-*--*-*| * ] ^ This Result (2nd Percentile): 4.7 Arc A770 DG2: 101 ^ RTX 3080: 147 ^ RX 6900 XT: 199 ^ Arc A750 DG2: 96 ^ Gigabyte RX 6800 XT: 177 ^ RTX 2070 SUPER: 91 ^ RTX 3090: 173 ^ RX 5700 XT: 81 ^ Gigabyte RX 6800: 163 ^ > ~~~ ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1981087 Title: thermald prematurely throttling GPU Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Jammy: Fix Committed Bug description: [Impact] * thermald prematurely throttling GPU [Fix] This fix is removed the code refactoring part and keep the necessary. (patch: 0009-Install-passive-default.patch) 82609c7) Separate Adaptive engine and GDDV [Test Plan] Test1, * Run game on the target machine. * the FPS must not be significantly reduced. Test2, * Run on others platform, ADL/TGL/CML/CFL/KBL. * Use monitoring tool(e.g. s-tui) and stress-ng to verify if the machine runs normally. [Where problems could occur] * better support for Passive Policy. currently passive policy 1 is supported and it should have a bug if the machine only enable pssive policy 2. ~~~ I got a new game and started playing it It would run at over 100 FPS solidly some of the time and then cyclically dip down to below 20 FPS for a few minutes I determined that it was thermald trying to keep my GPU below 70°C to determine this I sudo systemctl stop thermald The game ran solidly and consistently with the GPU at 75°C This is well below the specs set by the manufacturer and perhaps unreasonably low for a laptop But more importantly I was given no indication this was happening. I had to sleuth it out myself. Perhaps it is impossible to determine good defaults for all hardware, I don't know. However without an indication that this is happening there will be a lot of people with a mysteriously broken experience. This was extremely difficult for me to find and I had several friend who are experts on linux gaming and video drivers trying to track this down. I discovered it by luck and perseverance. This absolutely needs some sort of indication and hopefully a way to remedy it from the GUI. ideally it would set thermal limits that are more in line with what the device is designed for and not a conservative default if at all possible. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: thermald 2.4.9-1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
[Kernel-packages] [Bug 2027645] Re: [Lenovo Legion 5] Brightness option is not working and not showing in system menu
See also: bug 1899626, bug 1944094, bug 1995173 ** Summary changed: - britness option is not working and not showing in system menu + [Lenovo Legion 5] Brightness option is not working and not showing in system menu ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2027645 Title: [Lenovo Legion 5] Brightness option is not working and not showing in system menu Status in linux package in Ubuntu: New Bug description: The ubuntu version is automatic updated and then i am facing this issue that there is not britness control is there in my system ment and my briness key also not wokring ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 09:44:30 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027645/+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 1853306] Re: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part
This bug is awaiting verification that the linux/5.15.0-79.86 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853306 Title: [22.04 FEAT] Enhanced Interpretation for PCI Functions on s390x - kernel part Status in Ubuntu on IBM z Systems: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [ Impact ] * Currently the PCI passthrough implementation for s390x is based on intercepting PCI I/O instructions, which leads to a reduced I/O performance compared to the execution of PCI instructions directly in LPAR. * Hence users may face I/O bottlenecks when using PCI devices in passthrough mode based on the current implementation. * For avoiding this and to improve performance, the interpretive execution of the PCI store and PCI load instructions get enabled. * A further improvement is achieved by enabling the Adapter-Event-Notification Interpretation (AENI). * Since LTS releases are the main focus for stable and long running KVM workloads, it is highly desired to get this backported to the jammy kernel (and because the next LTS is still some time away). [ Test Plan ] * Have an Ubuntu Server 22.04 installation on LPAR, that is able to access (ideally multiple) PCI devices, like RoCE Express (network) or NVMe disks. * Setup KVM and pass through (ideally multiple) of these PCI devices (that are otherwise unused on the KVM host). * Generate IO load on these passed through PCI devices, for example with stress-ng, using class network and/or device and/or io stressors. * This PR also introduces a new kernel config option 'VFIO_PCI_ZDEV_KVM' that allows to enable support for the s390x-specific extensions and enhancements to KVM passthrough, such as interpretive execution of zPCI instructions and is with this PR and got enabled. * The qemu autopkgtest (also needed due to LP#1853307) will be a got fit to identify any potential regressions, also in the kvm kernel area. * zPCI passthrough related test will be done by IBM. [ Where problems could occur ] * The modifications do not change the way users or APIs have to make use of PCI passthrough, only the internal implementation got modified. * The vast majority of the code changes/or additional code is s390x-specific, under arch/s390 and drivers/s390. * However there is also common code touched: * 'kvm: use kvfree() in kvm_arch_free_vm()' touches arch/arm64/include/asm/kvm_host.h, arch/arm64/kvm/arm.c, arch/x86/include/asm/kvm_host.h, arch/x86/kvm/x86.c, include/linux/kvm_host.h switches in kvm_arch_free_vm() from kfree() to kvfree() allowing to use the common variant, which is upstream since v5.16 and with that well established. * And 'vfio-pci/zdev: add open/close device hooks' touches drivers/vfio/pci/vfio_pci_core.c and drivers/vfio/pci/vfio_pci_zdev.c include/linux/vfio_pci_core.h add now code to introduce device hooks. It's upstream since kernel 6.0. * 'KVM: s390: pci: provide routines for en-/disabling interrupt forwarding' expands a single #if statement in include/linux/sched/user.h. * 'KVM: s390: add KVM_S390_ZPCI_OP to manage guest zPCI devices' adds s390x specific KVM_S390_ZPCI_OP and it's definition to include/uapi/linux/kvm.h. * And 'vfio-pci/zdev: different maxstbl for interpreted devices' and 'vfio-pci/zdev: add function handle to clp base capability' expand s390x-specific (aka z-specific aka zdev) device structs in include/uapi/linux/vfio_zdev.h. * This shows that the vast majority of modifications are s390x specific, even in most of the common code files. * The remaining modifications in the (generally) common code files are related to the newly introduced kernel option 'CONFIG_VFIO_PCI_ZDEV_KVM' and documentation. * The s390x changes are more significant, and could not only harm passthrough itself for zPCI
[Kernel-packages] [Bug 2008745] Re: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU
This bug is awaiting verification that the linux/5.15.0-79.86 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2008745 Title: [SRU] Intel Sapphire Rapids HBM support needs CONFIG_NUMA_EMU Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Bug description: [Impact] Currently Ubuntu kernel has this kernel config disabled. But in some cases, Intel's Sapphire Rapids High Bandwith Memory (SPR-HBM) needs this option. Memory bandwidth has been a bottleneck of increasingly memory bound workloads. Sapphire Rapids plus HBM is specifically targeted to cater to these workloads, traditionally served using overprovisioning of memory devices. Please search the keyword "fake numa" in https://community.intel.com/t5/Blogs/Products-and- Solutions/HPC/Enabling-High-Bandwidth-Memory-for-HPC-and-AI- Applications-for/post/1335100 [Fix] Enable CONFIG_NUMA_EMU in our kernel config for 5.15 and later [Test Plan] Use "STREAM-triadd" algorithm* in Intel MLC** to benchmark 3 scenarios (no fake NUMA, 2U fake NUMA and 4U fake NUMA). * https://www.intel.com/content/www/us/en/developer/articles/technical/optimizing-memory-bandwidth-on-stream-triad.html ** https://www.intel.com/content/www/us/en/download/736633/intel-memory-latency-checker-intel-mlc.html An improvement to performance on a Sapphire Rapids CPU with HBM should be observed [Where problems could occur] The regression risk is low [Other Info] Jammy https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/jammy/+ref/lp_2008745_config_numa_emu_2 Kinetic https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/kinetic/+ref/lp_2008745_config_numa_emu_kinetic Lunar https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/lunar/+ref/config_numa_emu_lunar_2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2008745/+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 2003374] Re: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols
This bug is awaiting verification that the linux/5.15.0-79.86 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2003374 Title: Undefined Behavior Sanitizer (UBSAN) causes failure to match symbols Status in dh-kpatches: Unknown Status in Ubuntu on IBM z Systems: In Progress Status in kpatch package in Ubuntu: In Progress Status in linux package in Ubuntu: Incomplete Status in kpatch source package in Jammy: In Progress Status in linux source package in Jammy: Fix Committed Status in kpatch source package in Kinetic: New Bug description: [ Impact ] * When UBSAN is enabled in an s390x kernel configuration, kpatch- build can fail to find matching symbols in the vmlinux symbol table (see attached example_livepatch.patch). This was discovered in both Jammy 5.15 and Kinetic 5.19 kernels, where UBSAN was first enabled (releases up to Focal did not enable UBSAN). See attached kpatch-build console output (output.log) and kpatch-build log (build.log). * Disabling UBAAN in s390x kernel configurations resolved the issue for both Jammy 5.15 and Kinetic 5.19. Possibly this could be fixed in kpatch/kpatch-build to continue to enable UBSAN while still allowing Livepatch functionality. [ Test Plan ] * Use kpatch-build testcases to build and load a fs/proc/meminfo.c Livepatch on s390x kernel (see attached example_livepatch.patch). This should be successful. [ Where problems could occur ] * A fix in kpatch/kpatch-build to properly handle UBSAN objects shouldn't yield any regressions. If UBSAN is disabled to ultimately get past this issue, it could lead to undefined behavior not being caught. To manage notifications about this bug go to: https://bugs.launchpad.net/dh-kpatches/+bug/2003374/+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 2018566] Re: A deadlock issue in scsi rescan task while resuming from S3
This bug is awaiting verification that the linux/5.15.0-79.86 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags removed: verification-done-jammy ** Tags added: kernel-spammed-jammy-linux verification-needed-jammy -- 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/2018566 Title: A deadlock issue in scsi rescan task while resuming from S3 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: Invalid Status in linux source package in Jammy: Fix Committed 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 Lunar: Fix Committed 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: Invalid Bug description: [Impact] During the S3 stress test, the system sometimes hangs when resuming. This is due to the SCSI rescan task being unable to acquire the mutex lock during the resumption from S3. The mutex lock has already been acquired by EH and is waiting for the device to be ready for a rescan. Unfortunately, the mutex lock is never released by either party, leading to a deadlock. [Fix] Kaiheng submitted a patch to fix this issue which defers the rescan if the disk is still suspended so the resume process of the disk device can proceed. https://patchwork.ozlabs.org/project/linux-ide/patch/20230502150435.423770-2-kai.heng.f...@canonical.com/ Since the patch has not been accepted by the upstream yet, so submit it to the OEM kernel for now. The similiar patch has been included in v6.4-rc7 6aa0365a3c85 ata: libata-scsi: Avoid deadlock on rescan after device resume [Test] Verified on the machines by me and ODM. [Where problems could occur] It only defers the rescan task, and should not have any impact to current systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2018566/+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 2024900] Re: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present
This bug is awaiting verification that the linux/5.15.0-79.86 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-jammy-linux verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2024900 Title: Disable hv-kvp-daemon if /dev/vmbus/hv_kvp is not present Status in linux package in Ubuntu: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: Fix Committed Status in linux source package in Mantic: Fix Committed Bug description: SRU Justification [Impact] If the daemon is started and the vmbus is not present it will just exit with an error: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/mantic/tree/tools/hv/hv_kvp_daemon.c#n1424 Thus, it would make sense to add "ConditionPathExists=/dev/vmbus/hv_kvp" in linux-cloud-tools- common.hv-kvp-daemon.service to prevent systemd from starting the daemon if the device is not there. [Test Plan] Start an Azure cloud instance and check for /dev/vmbus/hv_kvp and that hv-kvp-daemon is running. Start a non-Azure cloud instance and check that hv-kvp-daemon is not running. [Regression potential] Its possible that kv-hvp-daemon is not started when it should be. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2024900/+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 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers
** Description changed: - Hi Ubuntu Team, + [ Impact ] - MY ISSUE: - I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). - But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. + gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder + Lake systems running older kernels such as 5.15. - ERROR: - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state - root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- - iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... - iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server - iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer - iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. - iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' - iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary - iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' - iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. - iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be
[Kernel-packages] [Bug 2027667] [NEW] Certain website floods syslog
Public bug reported: When viewing https://paris2024.sapsailing.com/gwt/RaceBoard.html?regattaName=OSG2024TEV2023+-+Men%27s+Windsurfing=iQFOiL+men+-+R4=OSG2024TEV2023+-+Men%27s+Windsurfing=83eb5c2a-d3ab-4e22-8422-1e4ab154ed34=b8220cee-9ec7-4640-b8d8-f40e079456d5=FULL_ANALYSIS syslog is flooded with hundreds of lines like these: Jul 13 11:24:47 moshe kernel: [12492.404743] audit: type=1326 audit(1689236687.177:2451): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.405092] audit: type=1326 audit(1689236687.177:2452): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.407568] audit: type=1326 audit(1689236687.181:2453): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.407827] audit: type=1326 audit(1689236687.181:2454): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.408397] audit: type=1326 audit(1689236687.181:2455): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.408622] audit: type=1326 audit(1689236687.181:2456): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.409197] audit: type=1326 audit(1689236687.181:2457): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.409429] audit: type=1326 audit(1689236687.181:2458): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.410412] audit: type=1326 audit(1689236687.185:2459): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:24:47 moshe kernel: [12492.410696] audit: type=1326 audit(1689236687.185:2460): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.337807] kauditd_printk_skb: 9 callbacks suppressed Jul 13 11:25:39 moshe kernel: [12544.337809] audit: type=1326 audit(1689236739.112:2470): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.337928] audit: type=1326 audit(1689236739.112:2471): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.338412] audit: type=1326 audit(1689236739.112:2472): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.338602] audit: type=1326 audit(1689236739.116:2473): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e syscall=312 compat=0 ip=0x7f61d497873d code=0x5 Jul 13 11:25:39 moshe kernel: [12544.785724] audit: type=1326 audit(1689236739.560:2474): auid=1000 uid=1000 gid=1000 ses=12 subj=snap.firefox.firefox pid=25764 comm="CanvasRenderer" exe="/snap/firefox/2880/usr/lib/firefox/firefox" sig=0 arch=c03e
[Kernel-packages] [Bug 2020702] Re: Jammy update: v6.1.30 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2021572] Re: dGPU cannot resume because system firmware stuck in IPCS method
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2021945] Re: Jammy update: v6.1.31 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2023264] Re: Jammy update: v6.1.32 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2024126] Re: eDP power on flow enhancement to speed up kernel boot time
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2024449] Re: Fix audio white noise while play from HDMI/DP port on AMD W6300 gfx
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2024165] Re: Jammy update: v6.1.33 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2024166] Re: Jammy update: v6.1.34 upstream stable release
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2024273] Re: Fix eDP only displays 3/4 area after switching to mirror mode with external HDMI 4K monitor
This bug was fixed in the package linux-oem-6.1 - 6.1.0-1016.16
---
linux-oem-6.1 (6.1.0-1016.16) jammy; urgency=medium
* jammy/linux-oem-6.1: 6.1.0-1016.16 -proposed tracker (LP: #2024462)
* Jammy update: v6.1.34 upstream stable release (LP: #2024166)
- scsi: megaraid_sas: Add flexible array member for SGLs
- net: sfp: fix state loss when updating state_hw_mask
- spi: mt65xx: make sure operations completed before unloading
- platform/surface: aggregator: Allow completion work-items to be executed
in
parallel
- platform/surface: aggregator_tabletsw: Add support for book mode in KIP
subsystem
- spi: qup: Request DMA before enabling clocks
- afs: Fix setting of mtime when creating a file/dir/symlink
- wifi: mt76: mt7615: fix possible race in mt7615_mac_sta_poll
- bpf, sockmap: Avoid potential NULL dereference in
sk_psock_verdict_data_ready()
- neighbour: fix unaligned access to pneigh_entry
- net: dsa: lan9303: allow vid != 0 in port_fdb_{add|del} methods
- net/ipv4: ping_group_range: allow GID from 2147483648 to 4294967294
- bpf: Fix UAF in task local storage
- bpf: Fix elem_size not being set for inner maps
- net/ipv6: fix bool/int mismatch for skip_notify_on_dev_down
- net/smc: Avoid to access invalid RMBs' MRs in SMCRv1 ADD LINK CONT
- net: enetc: correct the statistics of rx bytes
- net: enetc: correct rx_bytes statistics of XDP
- net/sched: fq_pie: ensure reasonable TCA_FQ_PIE_QUANTUM values
- Bluetooth: hci_sync: add lock to protect HCI_UNREGISTER
- Bluetooth: Fix l2cap_disconnect_req deadlock
- Bluetooth: ISO: don't try to remove CIG if there are bound CIS left
- Bluetooth: L2CAP: Add missing checks for invalid DCID
- wifi: mac80211: use correct iftype HE cap
- wifi: cfg80211: reject bad AP MLD address
- wifi: mac80211: mlme: fix non-inheritence element
- wifi: mac80211: don't translate beacon/presp addrs
- qed/qede: Fix scheduling while atomic
- wifi: cfg80211: fix locking in sched scan stop work
- selftests/bpf: Verify optval=NULL case
- selftests/bpf: Fix sockopt_sk selftest
- netfilter: nft_bitwise: fix register tracking
- netfilter: conntrack: fix NULL pointer dereference in nf_confirm_cthelper
- netfilter: ipset: Add schedule point in call_ad().
- netfilter: nf_tables: out-of-bound check in chain blob
- ipv6: rpl: Fix Route of Death.
- tcp: gso: really support BIG TCP
- rfs: annotate lockless accesses to sk->sk_rxhash
- rfs: annotate lockless accesses to RFS sock flow table
- net: sched: add rcu annotations around qdisc->qdisc_sleeping
- drm/i915/selftests: Stop using kthread_stop()
- drm/i915/selftests: Add some missing error propagation
- net: sched: move rtm_tca_policy declaration to include file
- net: sched: act_police: fix sparse errors in tcf_police_dump()
- net: sched: fix possible refcount leak in tc_chain_tmplt_add()
- bpf: Add extra path pointer check to d_path helper
- drm/amdgpu: fix Null pointer dereference error in
amdgpu_device_recover_vram
- lib: cpu_rmap: Fix potential use-after-free in irq_cpu_rmap_release()
- net: bcmgenet: Fix EEE implementation
- bnxt_en: Don't issue AP reset during ethtool's reset operation
- bnxt_en: Query default VLAN before VNIC setup on a VF
- bnxt_en: Skip firmware fatal error recovery if chip is not accessible
- bnxt_en: Prevent kernel panic when receiving unexpected PHC_UPDATE event
- bnxt_en: Implement .set_port / .unset_port UDP tunnel callbacks
- batman-adv: Broken sync while rescheduling delayed work
- Input: xpad - delete a Razer DeathAdder mouse VID/PID entry
- Input: psmouse - fix OOB access in Elantech protocol
- Input: fix open count when closing inhibited device
- ALSA: hda: Fix kctl->id initialization
- ALSA: ymfpci: Fix kctl->id initialization
- ALSA: gus: Fix kctl->id initialization
- ALSA: cmipci: Fix kctl->id initialization
- ALSA: hda/realtek: Add quirk for Clevo NS50AU
- ALSA: ice1712,ice1724: fix the kcontrol->id initialization
- ALSA: hda/realtek: Add a quirk for HP Slim Desktop S01
- ALSA: hda/realtek: Add quirks for Asus ROG 2024 laptops using CS35L41
- drm/i915/gt: Use the correct error value when kernel_context() fails
- drm/amd/pm: conditionally disable pcie lane switching for some
sienna_cichlid SKUs
- drm/amdgpu: fix xclk freq on CHIP_STONEY
- drm/amdgpu: change reserved vram info print
- drm/amd/pm: Fix power context allocation in SMU13
- drm/amd/display: Reduce sdp bw after urgent to 90%
- wifi: iwlwifi: mvm: Fix -Warray-bounds bug in iwl_mvm_wait_d3_notif()
- can: j1939: j1939_sk_send_loop_abort(): improved error queue handling in
J1939 Socket
- can: j1939: change j1939_netdev_lock type to mutex
- can: j1939: avoid possible use-after-free when j1939_can_rx_register fails
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
This bug was fixed in the package linux-aws-6.2 - 6.2.0-1007.7~22.04.1 --- linux-aws-6.2 (6.2.0-1007.7~22.04.1) jammy; urgency=medium * jammy/linux-aws-6.2: 6.2.0-1007.7~22.04.1 -proposed tracker (LP: #2026280) * Revert variable symbol length modversion in all the jammy kernels (LP: #2025134) - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion" * Miscellaneous upstream changes - Revert "UBUNTU: debian/dkms-versions -- update from kernel-versions (main/master)" [ Ubuntu: 6.2.0-1007.7 ] * lunar/linux-aws: 6.2.0-1007.7 -proposed tracker (LP: #2024531) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem -
[Kernel-packages] [Bug 2025134] Re: Revert variable symbol length modversion in all the jammy kernels
This bug was fixed in the package linux-azure-6.2 - 6.2.0-1007.7~22.04.1 --- linux-azure-6.2 (6.2.0-1007.7~22.04.1) jammy; urgency=medium * jammy/linux-azure-6.2: 6.2.0-1007.7~22.04.1 -proposed tracker (LP: #2026281) * Revert variable symbol length modversion in all the jammy kernels (LP: #2025134) - Revert "UBUNTU: SAUCE: modpost: support arbitrary symbol length in modversion" [ Ubuntu: 6.2.0-1007.7 ] * lunar/linux-azure: 6.2.0-1007.7 -proposed tracker (LP: #2024534) * Packaging resync (LP: #1786013) - [Packaging] resync update-dkms-versions helper * lunar/linux: 6.2.0-25.25 -proposed tracker (LP: #2024167) * ftrace in ubuntu_kernel_selftests failed with "check if duplicate events are caught" on J-5.15 P9 / J-kvm / L-kvm (LP: #1977827) - SAUCE: selftests/ftrace: Add test dependency * Add microphone support of the front headphone port on P3 Tower (LP: #2023650) - ALSA: hda/realtek: Add Lenovo P3 Tower platform * Add audio support for ThinkPad P1 Gen 6 and Z16 Gen 2 (LP: #2023539) - ALSA: hda/realtek: Add quirk for ThinkPad P1 Gen 6 * Fix Disable thunderbolt clx make edp-monitor garbage while moving the touchpad (LP: #2023004) - drm/i915: Use 18 fast wake AUX sync len * Fix Monitor lost after replug WD19TBS to SUT port with VGA/DVI to type-C dongle (LP: #2021949) - thunderbolt: Increase timeout of DP OUT adapter handshake - thunderbolt: Do not touch CL state configuration during discovery - thunderbolt: Increase DisplayPort Connection Manager handshake timeout * Enable Tracing Configs for OSNOISE and TIMERLAT (LP: #2018591) - [Config] Enable OSNOISE_TRACER and TIMERLAT_TRACER configs * Fix only reach PC3 when ethernet is plugged r8169 (LP: #1946433) - r8169: use spinlock to protect mac ocp register access - r8169: use spinlock to protect access to registers Config2 and Config5 - r8169: enable cfg9346 config register access in atomic context - r8169: prepare rtl_hw_aspm_clkreq_enable for usage in atomic context - r8169: disable ASPM during NAPI poll - r8169: remove ASPM restrictions now that ASPM is disabled during NAPI poll * introduce do_lib_rust=true|false to enable/disable linux-lib-rust package (LP: #2021605) - [Packaging] introduce do_lib_rust and enable it only on generic amd64 * System either hang with black screen or rebooted on entering suspend on AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics (LP: #2020685) - drm/amdgpu: refine get gpu clock counter method - drm/amdgpu/gfx11: update gpu_clock_counter logic * generate linux-lib-rust only on amd64 (LP: #2020356) - [Packaging] generate linux-lib-rust only on amd64 * No HDMI/DP audio output on dock(Nvidia GPU) (LP: #2020062) - ALSA: hda: Add NVIDIA codec IDs a3 through a7 to patch table * Add support for mdev_set_iommu_device() kABI in Ubuntu 22.10 kernel (LP: #1988806) - SAUCE: Add mdev_set_iommu_device() kABI. * Enable audio LEDs on HP laptops (LP: #2019915) - ALSA: hda/realtek: Fix mute and micmute LEDs for an HP laptop - ALSA: hda/realtek: Fix mute and micmute LEDs for yet another HP laptop * linux-*: please enable dm-verity kconfigs to allow MoK/db verified root images (LP: #2019040) - [Config] CONFIG_DM_VERITY_VERIFY_ROOTHASH_SIG_SECONDARY_KEYRING=y * Lunar update: v6.2.13 upstream stable release (LP: #2023929) - ARM: dts: rockchip: fix a typo error for rk3288 spdif node - arm64: dts: rockchip: Lower sd speed on rk3566-soquartz - arm64: dts: qcom: ipq8074-hk01: enable QMP device, not the PHY node - arm64: dts: qcom: ipq8074-hk10: enable QMP device, not the PHY node - arm64: dts: meson-g12-common: specify full DMC range - arm64: dts: meson-g12-common: resolve conflict between canvas & pmu - perf/amlogic: adjust register offsets - arm64: dts: qcom: sc8280xp-pmics: fix pon compatible and registers - arm64: dts: imx8mm-evk: correct pmic clock source - arm64: dts: imx8mm-verdin: correct off-on-delay - arm64: dts: imx8mp-verdin: correct off-on-delay - netfilter: br_netfilter: fix recent physdev match breakage - netfilter: nf_tables: Modify nla_memdup's flag to GFP_KERNEL_ACCOUNT - rust: str: fix requierments->requirements typo - regulator: fan53555: Explicitly include bits header - regulator: fan53555: Fix wrong TCS_SLEW_MASK - virtio_net: bugfix overflow inside xdp_linearize_page() - sfc: Fix use-after-free due to selftest_work - netfilter: nf_tables: fix ifdef to also consider nf_tables=m - i40e: fix accessing vsi->active_filters without holding lock - i40e: fix i40e_setup_misc_vector() error handling - netfilter: nf_tables: validate catch-all set elements - cxgb4: fix use after free bugs caused by circular dependency problem - netfilter: nf_tables: tighten netlink attribute requirements for catch-all elements - bnxt_en: Do not initialize PTP on
[Kernel-packages] [Bug 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv
It's a regression introduced in mutter 42.9 by Intel: https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7 Although they would probably argue it's not a regression so long as you have a new enough kernel. Since we don't always have a new enough kernel in jammy we probably need to revert that commit. ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: mutter (Ubuntu Mantic) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Confirmed ** Also affects: linux-intel-iotg (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Kinetic) ** No longer affects: linux (Ubuntu Lunar) ** No longer affects: linux (Ubuntu Mantic) ** No longer affects: linux-intel-iotg (Ubuntu Jammy) ** No longer affects: linux-intel-iotg (Ubuntu Kinetic) ** No longer affects: linux-intel-iotg (Ubuntu Lunar) ** No longer affects: linux-intel-iotg (Ubuntu Mantic) ** Changed in: mutter (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Kinetic) Status: New => Invalid ** Changed in: mutter (Ubuntu Lunar) Status: New => Invalid ** Changed in: mutter (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu Mantic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Mantic) Importance: High => Undecided ** Changed in: mutter (Ubuntu Jammy) Status: Confirmed => In Progress ** Summary changed: - [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) + gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Invalid Status in mutter source package in Jammy: In Progress Status in mutter source package in Kinetic: Invalid Status in mutter source package in Lunar: Invalid Status in mutter source package in Mantic: Invalid Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for
[Kernel-packages] [Bug 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv
Nevermind. This bug is affecting regular Ubuntu Desktop too, for those running the original 22.04 release. It shouldn't happen if you're using 22.04.2 though because that has a new enough kernel to support the hardware, in theory. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Jammy: New Status in linux-intel-iotg source package in Kinetic: New Status in mutter source package in Kinetic: New Status in linux-intel-iotg source package in Lunar: New Status in mutter source package in Lunar: New Status in linux-intel-iotg source package in Mantic: Confirmed Status in mutter source package in Mantic: Confirmed Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11
[Kernel-packages] [Bug 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv
Suggested workarounds: * Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment * sudo apt install linux-generic-hwe-22.04 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in mutter source package in Jammy: New Status in mutter source package in Kinetic: New Status in mutter source package in Lunar: New Status in linux-intel-iotg source package in Mantic: Confirmed Status in mutter source package in Mantic: Confirmed Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=128
[Kernel-packages] [Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
Cannot reproduce this on any recent MAAS. -- 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic
** Changed in: maas Status: Incomplete => 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/1797581 Title: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic Status in MAAS: Invalid Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Using latest MAAS master, I'm unable to compose a VM over the UI successfully when composed with 2048 MB of RAM. By that I mean that the VM is created, but it fails with a kernel panic. So far this only occurred in MAAS environments and often went away with e.g. the next daily images. Therefore to reproduce and finally debug/fix this issue we'd need data from anyone being affected. This list will grow as we identify more that is needed. If you are affected, please attach to the bug - the kernel used to boot the guest - the initrd used to boot the guest - libvirt guest XML used to define the guest - PXE config provided to the guest - the cloud image used to start the guest (That will likely not fit as bug attachment, consider storing it somewhere and contact us) TODO: The Maas Team will outline how to get all these artifacts. TODO: add reference to the comment outlining this (once added) To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1797581/+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 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-intel-iotg (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com.
[Kernel-packages] [Bug 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Inv
** Summary changed: - [intel] gnome-shell Wayland sessions fail to start on intel-iotg kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) + [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/2026887 Title: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) Status in linux package in Ubuntu: Fix Released Status in linux-intel-iotg package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Hi Ubuntu Team, MY ISSUE: I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. ERROR: iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) iul 11 19:00:11 MY-PC dbus-daemon[693]:
[Kernel-packages] [Bug 2016398] Re: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?)
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Kinetic) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Lunar) Status: Confirmed => In Progress -- 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/2016398 Title: stacked overlay file system mounts that have chroot() called against them appear to be getting locked (by the kernel most likely?) Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: Won't Fix Status in linux source package in Lunar: In Progress Status in linux source package in Mantic: Confirmed Bug description: [Impact] Opened files reported in /proc/pid/map_files can be shows with the wrong mount point using overlayfs with filesystem namspaces. This incorrect behavior is fixed: UBUNTU: SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files However, the fix introduced a new regression, the reference to the original file stored in vma->vm_prfile is not properly released when vma->vm_prfile is replaced with a new file. This can cause a reference counter unbalance, leading errors such as "target is busy" when trying to unmount overlayfs, even if the filesystem has not active reference. [Test case] Reproducer provided by original bug reporter: https://launchpadlibrarian.net/663151659/overlayfsscript_example [Fix] Fix by properly releasing the original file stored in vm_prfile. [Regression potential] This fix seems to solve the reported bug (verified with the reproducer) and it doesn't seem to introduce other regressions or behavior change. However, we may experience regressions in overlayfs or potentially other "target is busy" errors when unmounting overlayfs filesystems with this fix applied, if there are still other corner cases not covered properly. [Original bug report] Hi BACKGROUND: --- I have a set of scripts that debootstraps and builds vanilla Debian installs, where the only modifications are what packages are installed. Then that becomes the lower directory of an overlayfs mount, a tmpfs becomes the upperdir, and then that becomes the chroot where config changes are made with more scripts. This overlayfs is mounted in its own mount namespace as the script is unshare'd Within these scripts, I make packages with a fork of checkinstall I made which uses the / as the lowerdir, as overlayfs allows that, a tmpfs as the upperdir, the install command is run with chroot, and then the contents are copied. THE ISSUE: -- I noticed that it appears that my ramdisks are remaining in memory, I have isolated it out to the overlayfs mounts with the overlayfs as the lowerdir where chroot is being called on it. I tried entering the namespace myself and umounting it, and notice I get the error "Target is busy" With the "Target Is Busy" issue, I tried to `lsof` and `fuser` and `lsfd` as much as I could, but every user mode tool shows absolutely NO files open at all I was using Kubuntu 18.04, it was an old install and 32 bit, so I had no upgrade path to be using more recent versions. Now I am on 23.04, but I also think this is happening on a 22.10 laptop DIAGNOSIS: -- I am able to isolate it out, and get this to replicate in the smallest script that I could that is now attached. the chroot is important. I am able to unmount the second overlayfs if chroot is never called. Nothing ever has to run IN the chroot, trying to call a binary that does not exist, and then trying to unmount it results in "target is busy" with no open files reportable by user mode tools FURTHER TESTING: Trying to find out the version of Linux this was introduced, I made a script that builds a very minimal ext4 file for a VM with a small debootstrapped system, builds a kernel, and runs the kernel with QEMU.. but when I started, after all that, I can't replicate it at all with a vanilla 6.2.0 kernel. I used the same config out of my /boot to the .config, only tweaking a few options like SYSTEM_TRUSTED_KEYS. Trying to unmount the second filesystem actually results in success I then built a Kubuntu Lunar VM, and was able to replicate it on not just my system. When I built and install the vanilla kernel with bindeb-pkg, and then I boot the vanilla kernel, I can't replicate it, the second filesystem unmounts. When I reboot
[Kernel-packages] [Bug 2019131] Re: Add PPIN support for Intel EMR cpu
** Tags removed: verification-needed-focal verification-needed-jammy ** Tags added: verification-done-focal verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2019131 Title: Add PPIN support for Intel EMR cpu Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification [Impact] Intel has introduced support for their new Emerald Rapids CPU. It was backported to Jammy in #lp2015372 and in #lp2015855. The remaining feature needed to fully support EMR is PPIN (the Protected Processor Inventory/Identification Number). This was recently pushed to upstream in 6.4 in commit 36168bc061b4368ad19e82b06a6463c95d3bb9a7. The change is very straightforward, it adds a new entry for EMERALDRAPIDS_X in the cpuids table where cpus that support ppin are listed. The table is then used in `ppin_init`. In Jammy, this implementation is missing. Both Amd and Intel have their own implementation which is doing pretty much the same. Instead of a list of cpus supported, a switch case is used instead in their init functions (amd_detect_ppin and intel_ppin_init). To reduce duplication of code and to help backport smoothly the new addition of EMR, commit 0dcab41d3487acadf64d0667398e032341bd9918 “x86/cpu: Merge Intel and AMD ppin_init() functions” was backported too. Thus commits: - 0dcab41d3487acadf64d0667398e032341bd9918: "x86/cpu: Merge Intel and AMD ppin_init() functions" - 36168bc061b4368ad19e82b06a6463c95d3bb9a7: "x86/cpu: Add Xeon Emerald Rapids to list of CPUs that support PPIN" are needed to support PPIN for EMR. [Testing] Kernel was built on cbd and boot tested on a VM. [Regression potential] Very low, it is a small refactor that removes duplication and it should not affect the functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2019131/+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
