[Kernel-packages] [Bug 1983108] Re: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371]
** Changed in: linux-hwe-5.15 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1983108 Title: [nouveau] watchdog: BUG: soft lockup - CPU#0 stuck for ... [plymouthd:371] Status in linux-hwe-5.15 package in Ubuntu: Fix Released Bug description: It caused my pc to get stuck during boot time. At rebooting, all worked fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6.2 ProcVersionSignature: Ubuntu 5.15.0-41.44~20.04.1-generic 5.15.39 Uname: Linux 5.15.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Jul 29 16:13:04 2022 DefaultPlymouth: /usr/share/plymouth/themes/xubuntu-logo/xubuntu-logo.plymouth InstallationDate: Installed on 2020-10-02 (664 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-41-generic root=UUID=ec6d1b78-08d0-4212-889f-df1909dbc8fa ro quiet splash SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/xubuntu-text/xubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/20/2009 dmi.bios.release: 4.8 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0408 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5QL/EPU dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0408:bd07/20/2009:br4.8:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5QL/EPU:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.15/+bug/1983108/+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 1189721] Re: Ralink RT3290 doesn't have a bluetooth driver
** Project changed: bluetooth => ubuntu ** No longer affects: ubuntu -- 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/1189721 Title: Ralink RT3290 doesn't have a bluetooth driver Status in Linux: Confirmed Status in Linux Mint: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: As of Raring Ubuntu has a wifi driver for the RT3290 that works out of the box. It still does not have bluetooth support. This thread in the Ubuntu forums links to a driver that is claimed to work: http://ubuntuforums.org/showthread.php?t=2115570 --- ApportVersion: 2.9.2-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: graeme 2412 F pulseaudio CRDA: country GB: (2402 - 2482 @ 40), (N/A, 20) (5170 - 5250 @ 40), (N/A, 20) (5250 - 5330 @ 40), (N/A, 20), DFS (5490 - 5710 @ 40), (N/A, 27), DFS DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=2d107179-35e2-4b1f-8bdd-90a01132ec70 InstallationDate: Installed on 2013-05-17 (144 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: Hewlett-Packard HP ProBook 4540s MarkForUpload: True Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=ac74fd89-3445-4a6d-b91b-ae4987867afe ro quiet splash acpi_backlight=vendor vt.handoff=7 ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8 RelatedPackageVersions: linux-restricted-modules-3.8.0-31-generic N/A linux-backports-modules-3.8.0-31-generic N/A linux-firmware1.106 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: raring Uname: Linux 3.8.0-31-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin plugdev sambashare sudo dmi.bios.date: 11/06/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68IRR Ver. F.32 dmi.board.name: 17F6 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 58.1D dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68IRRVer.F.32:bd11/06/2012:svnHewlett-Packard:pnHPProBook4540s:pvrA1018C1100:rvnHewlett-Packard:rn17F6:rvrKBCVersion58.1D:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4540s dmi.product.version: A1018C1100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1189721/+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 2023201] Re: Add support of Smart Amplifier IC ALC1319D on Intel platforms
** Merge proposal linked: https://code.launchpad.net/~acelankao/ubuntu/+source/firmware-sof/+git/firmware-sof/+merge/446354 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023201 Title: Add support of Smart Amplifier IC ALC1319D on Intel platforms Status in HWE Next: New Status in firmware-sof package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-6.1 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Incomplete Status in linux source package in Jammy: Invalid Status in linux-oem-6.1 source package in Jammy: Fix Released Status in firmware-sof source package in Mantic: New Status in linux source package in Mantic: Incomplete Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] Speaker is not functional on some Dell machines of Intel RPL platforms [Fix] Here's the patch submitted by Intel. https://patchwork.kernel.org/project/alsa-devel/patch/20230602202225.249209-16-pierre-louis.boss...@linux.intel.com/ [Test Case] 1. Power on the machine and open the audio settings 2. Verify it's not `Dummy Output` shown on the Audio output option [Where problems could occur] Only affect specific Intel RPL platforms. The risk of regression is low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2023201/+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 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)
Might be a Wayland bug after all: jul 17 06:49:40 X1-carbon gnome-shell[3140]: XWAYLAND: mode -1x-1 is not available ... is the recurring error message (between lots of "thunderbird[3569]: Couldn't map window 0x7f4cbe67ab20 as subsurface because its parent is not mapped." and other processes that don't know where to put their windows) -- 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/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed) Status in GNOME Shell: New Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1970495/+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 think "This was a regression introduced by Intel in 42.9!" should be removed from the changelog. It's not something I wrote in the patch or in the merge proposal. -- 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: Fix Committed 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 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/2018297 Title: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension Status in gnome-shell package in Ubuntu: Expired Status in iio-sensor-proxy package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: The auto-rotation feature of my Laptop stoped working. - screen orientation was in landscape mode - closed the lid of my laptop => laptop entered suspension mode - opened the lid => laptop was waking up - screen orientation was in portait mode I could not change the screen orientation by rotating the laptop physically nor change the orientation manually (the "Orientation" setting in the "Display Settings" Menu showed no dropdown menu). After a quick reboot everything worked fine. This are the specs of my Device: OS: Ubuntu 23.04 x86_64 Host: 20EM000VGE ThinkPad Yoga 460 Kernel: 6.2.0-20-generic Resolution: 1920x1080 DE: GNOME 44.0 WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] CPU: Intel i7-6500U (4) @ 3.100GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 7682MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+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 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/2018297 Title: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension Status in gnome-shell package in Ubuntu: Expired Status in iio-sensor-proxy package in Ubuntu: Invalid Status in linux package in Ubuntu: Expired Bug description: The auto-rotation feature of my Laptop stoped working. - screen orientation was in landscape mode - closed the lid of my laptop => laptop entered suspension mode - opened the lid => laptop was waking up - screen orientation was in portait mode I could not change the screen orientation by rotating the laptop physically nor change the orientation manually (the "Orientation" setting in the "Display Settings" Menu showed no dropdown menu). After a quick reboot everything worked fine. This are the specs of my Device: OS: Ubuntu 23.04 x86_64 Host: 20EM000VGE ThinkPad Yoga 460 Kernel: 6.2.0-20-generic Resolution: 1920x1080 DE: GNOME 44.0 WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] CPU: Intel i7-6500U (4) @ 3.100GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 7682MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+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 2026658] Re: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake
I disabled thermald, I think bug 1 may be resolved now, but bug 2 eventually occurred again overnight. -- 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/2026658 Title: CPU frequency governor broken after upgrading from 22.10 to 23.04, stuck at 400Mhz on Alder Lake Status in linux package in Ubuntu: New Bug description: I've tried to include as much detail as possible in this bug report, I originally assembled it just after the release of ubuntu 23.04. There has been no change since then. I have had substantial performance problems since updating from ubuntu 22.10 to 23.04. The computer in question is the 17 inch Razer Blade laptop from 2022 with an intel i7-12800H. Current kernel is 6.2.0-20-generic. (now I'm on 6.2.0-24-generic and nothing has changed.) This issue occurs regardless of whether the OpenRazer (https://openrazer.github.io/) drivers etc are installed. Description of problem: I have discovered what may be two separate bugs involving low level power management details on the cpu, they involve the cpu entering different types of throttled states and never recovering. These issues appeared immediately after upgrading from ubuntu 22.10. The computer is a large ~gaming laptop with plenty of thermal headroom, cpu temperatures cannot reach concerning values except when using stress testing tools. (I don't know how to propery untangle these two issues, so I'm posting them as one. I apologize for the review complexity this causes, but I think posting the information all in one spot is more constructive here.) High level testing notes: - This issue occurs with use of both the intel_pstate driver and the cpufreq driver. (I don't have the same level of detail for cpufreq, but the issue still occurs.) - I have additionally tested a handful of intel_pstate parameters (and others) via grub kernel command line arguments to no effect. All testing reported here was done with: GRUB_CMDLINE_LINUX_DEFAULT="modprobe.blacklist=nouveau" GRUB_CMDLINE_LINUX="" (loading nouveau caused problems for me on 22.10, I have not bothered reinvestigating it on 23.04) - There is a firmware update available from the manufacture when I boot into Windows, I have not installed it (yet). - - Update: I installed it. No change. - Changing the cpu governor setting from "powersave" to "performance" using `cpupower frequency-set -g performance` has no effect. (Note: this action is separate from the intel_pstate's power-saver/balanced/performance setting visible with the `powerprofilesctl` utility. It doesn't seem to be a governor bug. - - (There is a tertiary issue where I also see substantial (+50%) performance degredation using the "performance" profile in a test suite I run constantly for my job; that is clearly a problem but it is an unrelated bug that has existed for quite some time.) Summary and my own conclusions: These are my takeaways, the ~raw data is in the followup section. Bug 1) The reported cpu power limits are progressively constrained over time. Once this failure mode starts the performance never recovers. - As this situation progresses the observed cpu speeds (I'm using htop) list as 2800Mhz at idle, but the instant any load at all is placed on a cpu core that core immediately drops to exactly 400Mhz. - This situation occurs quite quickly in human terms, frequently within 20 minutes of normal usage after a boot, but it will also occur when the computer is just sitting there unused for a handful of hours. - This occurs when using the cpufreq gevernor (by including "intel_pstate=disable" on the grub command line args.) - At boot the default value for short_term_time looks wrong to me. This is the duration of higher thermal targets in seconds, ~0.002 seconds seems extremely short. A normal value would be a handful of seconds. - This situation can be remedied by running the following python script. It uses the undervolt package (pip install undervolt==0.3.0) to force particular power limits (the provided values are intentional overkill): 1 │ from undervolt import read_power_limit, set_power_limit, PowerLimit, ADDRESSES 2 │ from pprint import pprint 3 │ 4 │ limits = read_power_limit(ADDRESSES) 5 │ pprint(vars(limits)) # print current values before setting them 6 │ 7 │ POWER_LIMITS = PowerLimit() 8 │ POWER_LIMITS.locked = True # lock means don't allow the value to be reset until a reboot. 9 │ POWER_LIMITS.backup_rest = 281474976776192 # afaik this is just a backup-on-failure setting, it has no effect here. 10 │ POWER_LIMITS.long_term_enabled = True 11 │ POWER_LIMITS.long_term_power = 160 # values are intentional overkill 12 │ POWER_LIMITS.long_term_time = 2880.0
[Kernel-packages] [Bug 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
That is unusual if even the 6.2 and 6.4 kernels can't find the HDMI port. At this stage I would usually recommend a BIOS update but it seems you already have the latest BIOS from Asus. Since the kernel does seem to know about two DisplayPorts (presumably USB-C), I would recommend finding a USB-C to HDMI cable as a workaround. -- 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 2027933] Re: spontaneous shutdown
By the way at the information attached it says (probably is a fresh install) and it is, I did it to try to solve the problem but I been experiencing this problem a long time ago both batteries are working fine I can use them for a few hours, but as I said whenever the computer tries to switch batteries the system shuts down spontaneously -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2027933 Title: spontaneous shutdown Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I use a T470 Thinkpad with two batteries, the problem occurs when one of the batteries drains, The computer does not try to switch to the other battery. It just shutdown and when I turn on my computer again the battery that supposed to be switch is being used. My English is not so well, but just think about two batteries both at 100 %, one of them goes to 0%, and when it supposed to switch to the other one, the computer just shutdown immediately. I believe is a kernel issue because of the problem itself but I really don´t know. If you guys need something else to find a solution to this, please let me know. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 16 20:40:22 2023 InstallationDate: Installed on 2023-07-16 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027933/+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 2027933] [NEW] spontaneous shutdown
Public bug reported: I use a T470 Thinkpad with two batteries, the problem occurs when one of the batteries drains, The computer does not try to switch to the other battery. It just shutdown and when I turn on my computer again the battery that supposed to be switch is being used. My English is not so well, but just think about two batteries both at 100 %, one of them goes to 0%, and when it supposed to switch to the other one, the computer just shutdown immediately. I believe is a kernel issue because of the problem itself but I really don´t know. If you guys need something else to find a solution to this, please let me know. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 16 20:40:22 2023 InstallationDate: Installed on 2023-07-16 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.19 in Ubuntu. https://bugs.launchpad.net/bugs/2027933 Title: spontaneous shutdown Status in linux-signed-hwe-5.19 package in Ubuntu: New Bug description: I use a T470 Thinkpad with two batteries, the problem occurs when one of the batteries drains, The computer does not try to switch to the other battery. It just shutdown and when I turn on my computer again the battery that supposed to be switch is being used. My English is not so well, but just think about two batteries both at 100 %, one of them goes to 0%, and when it supposed to switch to the other one, the computer just shutdown immediately. I believe is a kernel issue because of the problem itself but I really don´t know. If you guys need something else to find a solution to this, please let me know. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.19.0-46-generic 5.19.0-46.47~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 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 16 20:40:22 2023 InstallationDate: Installed on 2023-07-16 (0 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) SourcePackage: linux-signed-hwe-5.19 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.19/+bug/2027933/+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 2027932] [NEW] package nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned erro
Public bug reported: Failed to build nvidia-drier-525 package on kernel 6.5-rc2 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 Uname: Linux 6.5.0-060500rc2-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jul 16 19:45:01 2023 ErrorMessage: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-07-08 (9 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-525 Title: package nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-525 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package jammy ** Attachment added: "make.log" https://bugs.launchpad.net/bugs/2027932/+attachment/5686736/+files/make.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-525 in Ubuntu. https://bugs.launchpad.net/bugs/2027932 Title: package nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-525 package in Ubuntu: New Bug description: Failed to build nvidia-drier-525 package on kernel 6.5-rc2 ProblemType: Package DistroRelease: Ubuntu 22.04 Package: nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 Uname: Linux 6.5.0-060500rc2-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass Date: Sun Jul 16 19:45:01 2023 ErrorMessage: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2023-07-08 (9 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-525 Title: package nvidia-dkms-525 525.125.06-0ubuntu0.22.04.1 failed to install/upgrade: installed nvidia-dkms-525 package post-installation script subprocess returned error exit status 10 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-525/+bug/2027932/+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
tested on the hardware with f81604 can controller. ** 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-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 2027914] Re: missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-restricted-modules (Ubuntu) Status: New => Confirmed -- 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/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: Confirmed Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+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 2019000] Re: Use new annotations model
This bug is awaiting verification that the linux-gcp/5.15.0-1039.47 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-gcp -- 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 2020413] Re: fix typo in config-checks invocation
This bug is awaiting verification that the linux-ibm/5.15.0-1035.38 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-ibm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/2020413 Title: fix typo in config-checks invocation Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-kvm source package in Jammy: Fix Released Bug description: [Impact] After migrating to the new annotations-only model in jammy we introduced a typo in debian/rules.d/4-checks.mk, that is triggered if we opt to not migrate to the new model and still use the old configs+annotations. [Test case] With debian./config/config.common.ubuntu present run the following command: $ fakeroot debian/rules clean updateconfigs [Fix] Replace @perl -> perl. [Regression potential] It's a trivial typo fix. Regressions can be introduced only if we are still using the old configs+annotations model. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020413/+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 2020531] Re: support python < 3.9 with annotations
This bug is awaiting verification that the linux-ibm/5.15.0-1035.38 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-ibm -- 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/2020531 Title: support python < 3.9 with annotations Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Lunar: Fix Released Status in linux source package in Mantic: Fix Released Bug description: [Impact] At the moment we can't use the annotations scripts in focal, because we are using the'|=' update operator for merging dicts, that has been introduced with python 3.9. Rewrite the code that is using this operator in a more portable way and apply this change everywhere, so that annotations will work on any backport/derivative kernels. [Test case] Run `fakeroot debian/rules updateconfigs` in focal (using the new annotations model). [Fix] Try to use the '|=' operator in a try/except block, if it fails fallback to a more portable way. [Regression potential] With this change applied we may experience regressions during the updateconfigs phase. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2020531/+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 2023577] Re: cls_flower: off-by-one in fl_set_geneve_opt
This bug is awaiting verification that the linux-ibm/5.15.0-1035.38 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-ibm 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/2023577 Title: cls_flower: off-by-one in fl_set_geneve_opt Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux source package in Lunar: Fix Released Bug description: [Impact] An unprivileged user may cause an out-of-bounds write by setting up geneve options on the flower classifier. [Test case] https://seclists.org/oss-sec/2023/q2/219 [Potential regression] Users setting up geneve options on the flower tc classifier can be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023577/+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 2023220] Re: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled
This bug is awaiting verification that the linux-ibm/5.15.0-1035.38 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-ibm verification-needed-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.1 in Ubuntu. https://bugs.launchpad.net/bugs/2023220 Title: Some INVLPG implementations can leave Global translations unflushed when PCIDs are enabled Status in linux package in Ubuntu: Fix Released Status in linux-oem-6.1 package in Ubuntu: Invalid Status in linux source package in Trusty: Incomplete Status in linux-oem-6.1 source package in Trusty: Invalid Status in linux source package in Xenial: Incomplete Status in linux-oem-6.1 source package in Xenial: Invalid Status in linux source package in Bionic: Incomplete Status in linux-oem-6.1 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-6.1 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-6.1 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Status in linux-oem-6.1 source package in Kinetic: Invalid Status in linux source package in Lunar: Fix Released Status in linux-oem-6.1 source package in Lunar: Invalid Status in linux source package in Mantic: Fix Released Status in linux-oem-6.1 source package in Mantic: Invalid Bug description: [Impact] When PCIDs are enabled on Alder Lake and Raptor Lake, INVLPG will not flush the global TLB entries. This can lead to info leak or undefined behavior. [Mitigation] Boot with nopcid on affected systems. [Test case] There is no particular test case. [Potential regressions] This affects performance on the affected systems. TLB behavior could also be affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2023220/+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 2027914] [NEW] missing nvidia kernel module for generic kernel (linux-objects-nvidia-535-6.2.0-25-generic)
Public bug reported: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. ** Affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New -- 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/2027914 Title: missing nvidia kernel module for generic kernel (linux-objects- nvidia-535-6.2.0-25-generic) Status in linux-restricted-modules package in Ubuntu: New Bug description: For latest generic kernel for Ubuntu 23.04 there in no package of kernel module. Present is for previous kernel: # aptitude search linux-objects-nvidia-535.*generic i A linux-objects-nvidia-535-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-open-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-6.2.0-24-generic - Linux kernel nvidia modules for version 6.2.0-24 (objects) p linux-objects-nvidia-535-server-open-6.2.0-24-generic- Linux kernel nvidia modules for version 6.2.0-24 (objects) There is no package for 6.2.0-25 kernel. So after upgrade to new kernel - gpu isn't working, as the module is missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/2027914/+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 1987829] Re: LG Gram 12gen high CPU use when USB-C/TB is in use
Here is my elegant workaround to the problem: ``` [Unit] Description=Fixes many issues with the 2022 LG Grams running linux and sets charging limit to 80 # save this script to /etc/systemd/system/lg-gram.service # then run: # sudo systemctl daemon-reload # sudo systemctl enable lg-gram.service # sudo systemctl start lg-gram.service # more documentation: https://www.reddit.com/r/LGgram/comments/150p3rg/critical_bug_affecting_the_2022_lineup_on_linux/ [Service] Type=oneshot # Unmask GPE interrupts to resolve the issue of high temperatures and fan noise even on idle when the laptop is charging through USB-C/TB: ExecStart=/bin/bash -c "echo 'unmask' > /sys/firmware/acpi/interrupts/gpe6E" # sets charging limit to 80 to increase battery longevity: ExecStart=/bin/bash -c "echo 80 > /sys/class/power_supply/CMB0/charge_control_end_threshold" # Disable "Silent mode": ExecStart=/bin/bash -c "echo 1 > /sys/devices/platform/lg-laptop/fan_mode" # Unload the int3403 temp sensor library from the kernel to fix ACPI flood issue: # ExecStart=/bin/sh -c "rmmod int3403_thermal" # Disable turbo boost (trade single threaded performance for lower heat output and maybe battery life) # ExecStart=/bin/sh -c 'echo 1 > /sys/devices/system/cpu/intel_pstate/no_turbo' # ExecStop=/bin/sh -c 'echo 0 > /sys/devices/system/cpu/intel_pstate/no_turbo' # Fix for thermal throttle issue that on some distros can put the CPU running on low wattages: # ExecStart=/bin/bash -c "systemctl disable --now thermald" RemainAfterExit=yes [Install] WantedBy=multi-user.target ``` -- The issue seems to be caused by: ```some miscommunication between Linux thinking it can probe for thermal info on a device which did not register a handler to do so``` Source - https://www.reddit.com/r/linuxhardware/comments/x97m6l/fedora_lg_gram_16_2022_12th_gen_alder_lake/ (added to the original post) I'm happy to confirm that the kernel parameter acpi_mask_gpe=0x6E seems to fix the issue of fans blasting and high temperatures even on idle! An observed drawback from this solution is that is breaks the functionality of the screen brighness buttons: it still works, but you can hold it, and it also has a big delay in applying each setting - This doesn't bother me as I already use some scripts with a custom keyboard shortcut to set the brighness of all my displays at once. Another solution is unmasking the GPE interrupts not through a kernel parameter, but after boot with: echo unmask > /sys/firmware/acpi/interrupts/gpe6E - This way the brightness button issues don't manifest. Furthermore, setting the kernel parameter acpi_mask_gpe=0x6E, it could be affecting idle power draws if the values returned by GPE are used to put cpus into idle states. Thankfully the issue only happens when the laptops are charging, so it wouldn't kill battery life. >From the kernel documentation I could find: acpi_mask_gpe= [HW,ACPI]Due to the existence of _Lxx/_Exx, some GPEs triggeredby unsupported hardware/firmware features can result inGPE floodings that cannot be automatically disabled bythe GPE dispatcher.This facility can be used to prevent such uncontrolledGPE floodings.Format: or So the documentation is aligned with the observations of the fix/workaround. -- Furthermore, there is another possible fix: journalctl seems to output many ACPI errors, probably due to the miscommunication between Linux thinking it can probe for thermal info on a device which did not register a handler to do so. The ACPI issue is a flood caused by the int3403 temp sensor library, which can be unloaded from the kernel without any other visible system effect sudo rmmod int3403_thermal is how it's unloaded A permanent fix seems to be patching the int3403 library to add something like if (sensorNotPresent) then skip or unregister until next launch -- There seems to be yet another issue related to this: power usage goes way up to around 10W at idle (instead of like 3W) and there's a kernel thread with high load (visible in powertop) related to the i915 graphics driver The solution seems to be: echo 1 > /sys/kernel/debug/dri/1/i915_hpd_short_storm_ctl That should be run on every boot to stop another interrupt flooding from happening, but this solution: it might break multi-stream transport on DisplayPort - the short storm detection is enabled by default unless multi-stream transport is supported -- Another finding: The laptop is by default running on "Silent mode" which can be disabled by: echo 1 > /sys/devices/platform/lg-laptop/fan_mode -- The laptop indeed seems to have no BIOS updates. -- Another issue seems to be that on some distros the laptop might thermal throttle to very low wattages, and the fix is: systemctl disable --now thermald -- 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/1987829 Title: LG Gram 12gen high CPU use when USB-C/TB is in use Status in
[Kernel-packages] [Bug 2025538] Re: Unrequested kernel update
In lunar / 23.04, there is no linux-objects-nvidia-535-6.2.0-25-generic package, but the linux-image-6.2.0-25-generic package has been available for some time. Package upgrades therefore insist on switching to nvidia- dkms, no matter what I try to do. So I'm still on 6.2.0-24. Is this just another aspect of this bug, or is the linux-objects- nvidia-* package discontinued and we are actually supposed to switch to dkms? -- 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 2025040] Re: increased power usage after upgrade from kinetic to lunar
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2025040 Title: increased power usage after upgrade from kinetic to lunar Status in linux package in Ubuntu: Confirmed Bug description: Hi I have just upgrade and power usage is double or more under lunar. Kernel version went from 5.19.0-43 to 6.2.0-20. Running powertop, I see that C8 is being used with 5.19 but 6.2 does not go to a higher power saving state than C3. I tried the Ubuntu kernel from jammy ie 5.15.0-73. It also uses C8. I have also tried the 5.15.108 & 5.10.17 mainline kernels. Both of these do not go to higher power saving state than C3. All these tests have been run on the same partition ie. only the kernel version has changed. Laptop is a HP 15s-fq4011TU 11th Gen Intel with Tiger Lake Iris Xe graphics. So it seems to me: 1) Ubuntu has applied a patch to the mainline kernel that improves power saving in 5.15 and 5.19 2) This patch either hasn't been applied to 6.2 or no longer works. Could you pls let me know what other info you need or what I could look at next? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025040/+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 2025040] Re: increased power usage after upgrade from kinetic to lunar
I can also confirm this one also on a HP 15s-fq4xxx series laptop I tested this on the kinetic kernel 5.19. -- 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/2025040 Title: increased power usage after upgrade from kinetic to lunar Status in linux package in Ubuntu: Confirmed Bug description: Hi I have just upgrade and power usage is double or more under lunar. Kernel version went from 5.19.0-43 to 6.2.0-20. Running powertop, I see that C8 is being used with 5.19 but 6.2 does not go to a higher power saving state than C3. I tried the Ubuntu kernel from jammy ie 5.15.0-73. It also uses C8. I have also tried the 5.15.108 & 5.10.17 mainline kernels. Both of these do not go to higher power saving state than C3. All these tests have been run on the same partition ie. only the kernel version has changed. Laptop is a HP 15s-fq4011TU 11th Gen Intel with Tiger Lake Iris Xe graphics. So it seems to me: 1) Ubuntu has applied a patch to the mainline kernel that improves power saving in 5.15 and 5.19 2) This patch either hasn't been applied to 6.2 or no longer works. Could you pls let me know what other info you need or what I could look at next? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2025040/+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 2006797] Re: MT7922 firmware not working
Thanks for the update. I have applied the patch on 6.4.3 but no effect. I see the following error in the kernel log - ``` Jul 16 12:51:26 andrew-laptop kernel: mt7921e :03:00.0: enabling device ( -> 0002) Jul 16 12:51:26 andrew-laptop kernel: mt7921e :03:00.0: driver own failed Jul 16 12:51:26 andrew-laptop kernel: mt7921e: probe of :03:00.0 failed with error -5 ``` -- 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/2006797 Title: MT7922 firmware not working Status in linux package in Ubuntu: Confirmed Bug description: Hey I have a "ASUS ROG Strix B650-A Gaming WIFI" (https://rog.asus.com/motherboards/rog-strix/rog-strix-b650-a-gaming- wifi-model/) Motherboard and the WiFi/Bluetooth is not working. On windows, the module is working fine. Using "Kubuntu 22.10" with Kernel "5.19.0-35-generic" lshw -class network: *-network description: Network controller product: MT7922 802.11ax PCI Express Wireless Network Adapter vendor: MEDIATEK Corp. physical id: 0 bus info: pci@:0b:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: pciexpress msi pm bus_master cap_list configuration: driver=mt7921e latency=0 resources: iomemory:fc0-fbf irq:119 memory:fc3030-fc303f memory:fc50-fc507fff #dmesg | grep mt7921e [ 17.001057] mt7921e :0b:00.0: enabling device ( -> 0002) [ 17.001199] mt7921e :0b:00.0: ASIC revision: 79220010 [ 20.247369] mt7921e :0b:00.0: Message 0004008a (seq 1) timeout [ 23.575534] mt7921e :0b:00.0: Message 0004008a (seq 2) timeout [ 26.907372] mt7921e :0b:00.0: Message 0004008a (seq 3) timeout [ 30.231376] mt7921e :0b:00.0: Message 0004008a (seq 4) timeout [ 33.559704] mt7921e :0b:00.0: Message 0004008a (seq 5) timeout [ 36.887365] mt7921e :0b:00.0: Message 0004008a (seq 6) timeout [ 40.215367] mt7921e :0b:00.0: Message 0004008a (seq 7) timeout [ 43.543670] mt7921e :0b:00.0: Message 0004008a (seq 8) timeout [ 46.871378] mt7921e :0b:00.0: Message 0004008a (seq 9) timeout [ 50.199714] mt7921e :0b:00.0: Message 0004008a (seq 10) timeout [ 50.280219] mt7921e :0b:00.0: hardware init failed ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-35-generic 5.19.0-35.36 ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17 Uname: Linux 5.19.0-35-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: KDE Date: Fri Feb 10 03:33:02 2023 InstallationDate: Installed on 2023-02-09 (0 days ago) InstallationMedia: Kubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: ASUS System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-35-generic root=/dev/mapper/vgkubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-35-generic N/A linux-backports-modules-5.19.0-35-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/21/2022 dmi.bios.release: 8.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0823 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B650-A GAMING WIFI dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0823:bd11/21/2022:br8.23:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB650-AGAMINGWIFI:rvrRev1.xx: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/2006797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2016459] Re: NVRM: RmInitAdapter failed! , failed to copy vbios to system memory
Hi, after initial joy, the nvidia 390 started to work after kernel/driver updates i notice nvidia 390 is broken again. latest kernel: 6.2.0-25-generic gives the nvrm copy error: [zo jul 16 12:33:03 2023] [drm] [nvidia-drm] [GPU ID 0x0100] Loading driver [zo jul 16 12:33:03 2023] NVRM: failed to copy vbios to system memory. [zo jul 16 12:33:03 2023] NVRM: RmInitAdapter failed! (0x30:0x:663) [zo jul 16 12:33:03 2023] NVRM: rm_init_adapter failed for device bearing minor number 0 while trying to be smart and boot still installed 6.2.0-24-generic there is no NVRM failed to copy vbios error, but instead later in process it locks up screen/keyboard while trying to start X. last message is Xorg.0.log is about glx: /var/log$ tail Xorg.0.log [21.663] (II) Initializing extension XVideo-MotionCompensation [21.663] (II) Initializing extension SELinux [21.663] (II) SELinux: Disabled on system [21.663] (II) Initializing extension XFree86-VidModeExtension [21.663] (II) Initializing extension XFree86-DGA [21.663] (II) Initializing extension XFree86-DRI [21.663] (II) Initializing extension DRI2 [21.663] (II) Initializing extension GLX [21.663] (II) Initializing extension GLX [21.663] (II) Indirect GLX disabled. not entirely sure, but logical i would say it broke after installing updates 13/7 grep -i nvidia dpkg.log 2023-07-05 08:56:42 upgrade libnvidia-common-390:all 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:42 status half-configured libnvidia-common-390:all 390.157-0ubuntu5 2023-07-05 08:56:42 status unpacked libnvidia-common-390:all 390.157-0ubuntu5 2023-07-05 08:56:42 status half-installed libnvidia-common-390:all 390.157-0ubuntu5 2023-07-05 08:56:42 status unpacked libnvidia-common-390:all 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:42 upgrade nvidia-driver-390:amd64 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:42 status half-configured nvidia-driver-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:42 status unpacked nvidia-driver-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:42 status half-installed nvidia-driver-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:43 status unpacked nvidia-driver-390:amd64 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:43 upgrade libnvidia-gl-390:amd64 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:43 status half-configured libnvidia-gl-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:43 status unpacked libnvidia-gl-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:43 status half-configured libnvidia-gl-390:i386 390.157-0ubuntu5 2023-07-05 08:56:43 status half-installed libnvidia-gl-390:amd64 390.157-0ubuntu5 2023-07-05 08:56:43 status unpacked libnvidia-gl-390:amd64 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:44 upgrade libnvidia-gl-390:i386 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:44 status unpacked libnvidia-gl-390:i386 390.157-0ubuntu5 2023-07-05 08:56:44 status half-installed libnvidia-gl-390:i386 390.157-0ubuntu5 2023-07-05 08:56:44 status unpacked libnvidia-gl-390:i386 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:44 upgrade nvidia-dkms-390:amd64 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:56:44 status half-configured nvidia-dkms-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:09 status unpacked nvidia-dkms-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:09 status half-installed nvidia-dkms-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:10 status unpacked nvidia-dkms-390:amd64 390.157-0ubuntu5.23.04.1 2023-07-05 08:57:10 upgrade nvidia-kernel-source-390:amd64 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:57:10 status half-configured nvidia-kernel-source-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:10 status unpacked nvidia-kernel-source-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:10 status half-installed nvidia-kernel-source-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:11 status unpacked nvidia-kernel-source-390:amd64 390.157-0ubuntu5.23.04.1 2023-07-05 08:57:11 upgrade nvidia-kernel-common-390:amd64 390.157-0ubuntu5 390.157-0ubuntu5.23.04.1 2023-07-05 08:57:11 status half-configured nvidia-kernel-common-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:11 status unpacked nvidia-kernel-common-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:11 status half-installed nvidia-kernel-common-390:amd64 390.157-0ubuntu5 2023-07-05 08:57:12 status unpacked nvidia-kernel-common-390:amd64 390.157-0ubuntu5.23.04.1 2023-07-05 08:57:12 upgrade linux-modules-nvidia-390-generic:amd64 6.2.0-24.24 6.2.0-24.24+2 2023-07-05 08:57:12 status half-configured linux-modules-nvidia-390-generic:amd64 6.2.0-24.24 2023-07-05 08:57:12 status unpacked linux-modules-nvidia-390-generic:amd64 6.2.0-24.24 2023-07-05 08:57:12 status half-installed linux-modules-nvidia-390-generic:amd64 6.2.0-24.24 2023-07-05 08:57:12 status unpacked linux-modules-nvidia-390-generic:amd64 6.2.0-24.24+2 2023-07-05 08:57:12 upgrade linux-modules-nvidia-390-6.2.0-24-generic:amd64 6.2.0-24.24 6.2.0-24.24+2 2023-07-05
[Kernel-packages] [Bug 2027848] Re: Soft-lockup caused by snd_hda_intel
No apologies neccesary, this is exactly how a community should work. I will take a look at the issue you posted. -- 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/2027848 Title: Soft-lockup caused by snd_hda_intel Status in linux package in Ubuntu: Confirmed Bug description: I report this bug the the 6.5rc1 kernel. Kernel before 6.5 hang even before there is any logging going on. The problem is gone when i blacklist snd_hda_core. jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 78s! [kworker/1:1:90] jul 15 09:02:52 nick-HP-Laptop-15s-fq4xxx kernel: Modules linked in: snd_seq_dummy snd_hrtimer rfcomm cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci_intel_tgl snd_sof_intel_hda_common soundwire_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: hp_wmi snd_timer videodev input_leds spi_nor rapl cec sparse_keymap cfg80211 intel_cstate wmi_bmof serio_raw platform_profile videobuf2_common snd mei_> jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: CPU: 1 PID: 90 Comm: kworker/1:1 Tainted: G U WL 6.5.0-060500rc1-generic #202307092131 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Hardware name: HP HP Laptop 15s-fq4xxx/89BC, BIOS F.31 03/25/2023 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Workqueue: events azx_probe_work [snd_hda_intel] jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RIP: 0010:_raw_spin_unlock_irq+0x15/0x50 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: Code: cc cc 0f 1f 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 00 fb 0f 1f 44 00 00 <65> ff 0d 5c 61 52 > jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RSP: 0018:b450c05dbb30 EFLAGS: 0246 jul 15 09:03:07 nick-HP-Laptop-15s-fq4xxx kernel: RAX: 0007 RBX: 0007 RCX: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027848/+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
