[Kernel-packages] [Bug 1931660] Re: PANIC at zfs_znode.c:339:zfs_znode_sa_init()
It stared to happen recently on my encrypted pool. The FS scrub reported no errors. -- 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/1931660 Title: PANIC at zfs_znode.c:339:zfs_znode_sa_init() Status in linux package in Ubuntu: Confirmed Bug description: I'm seeing a non-deterministic panic in the ZFS code. Last boot, this occurred in systemd-udevd, resulting in a failed boot. The boot before that, firefox hit the same thing, and this boot it looks like it's hit an Evolution component. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.11.0-18-generic 5.11.0-18.19+21.10.1 ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu67 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: chris 4988 F pulseaudio /dev/snd/controlC1: chris 4988 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:49:47 2021 InstallationDate: Installed on 2021-05-13 (28 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9575 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_z8j7yc@/vmlinuz-5.11.0-18-generic root=ZFS=rpool/ROOT/ubuntu_z8j7yc ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.198 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-05-13 (28 days ago) dmi.bios.date: 07/07/2019 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd07/07/2019:br1.7:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931660/+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 1944407] [NEW] Linux didnt detect my touchpad upon installation
Public bug reported: After installing Ubuntu 20.04 LTS I couldnt use my touch pad at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 14:56:54 2021 InstallationDate: Installed on 2021-09-19 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1944407 Title: Linux didnt detect my touchpad upon installation Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: After installing Ubuntu 20.04 LTS I couldnt use my touch pad at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-34-generic 5.11.0-34.36~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-34.36~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-34-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Sep 21 14:56:54 2021 InstallationDate: Installed on 2021-09-19 (2 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 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.11/+bug/1944407/+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 1944402] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1944402 Title: Chromebook Pixel 2013 not waking up from suspend Status in linux package in Ubuntu: Confirmed Bug description: I'm using a Chromebook Pixel 2013 (link) on Ubuntu 21.04 and my laptop wouldn't wake from suspend and show black screen despite I could hear the fan & lightbar LED running. This is the kernel bug part from the /var/log/syslog Sep 21 09:58:01 yeowool-Link kernel: [ 407.473841] BUG: unable to handle page fault for address: ff95 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473853] #PF: supervisor read access in kernel mode Sep 21 09:58:01 yeowool-Link kernel: [ 407.473858] #PF: error_code(0x) - not-present page Sep 21 09:58:01 yeowool-Link kernel: [ 407.473863] PGD 121415067 P4D 121415067 PUD 121417067 PMD 0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473875] Oops: [#1] SMP PTI Sep 21 09:58:01 yeowool-Link kernel: [ 407.473882] CPU: 1 PID: 1080 Comm: kworker/1:5 Not tainted 5.11.0-34-generic #36-Ubuntu Sep 21 09:58:01 yeowool-Link kernel: [ 407.473890] Hardware name: GOOGLE Link/Link, BIOS MrChromebox-4.14 07/25/2021 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473895] Workqueue: pm pm_runtime_work Sep 21 09:58:01 yeowool-Link kernel: [ 407.473907] RIP: 0010:snd_hda_codec_load_dsp_prepare+0x64/0x130 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.473937] Code: 00 00 00 8b 8b a0 05 00 00 4c 8d a0 18 ff ff ff eb 18 49 8b 84 24 e8 00 00 00 4c 8d a0 18 ff ff ff 48 39 c2 0f 84 8a 00 00 00 <41> 0f b6 44 24 7d 39 c8 75 de 4c 8d ab 98 04 00 00 4c 89 4d d0 4c Sep 21 09:58:01 yeowool-Link kernel: [ 407.473944] RSP: 0018:964680e83b38 EFLAGS: 00010286 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473951] RAX: RBX: 895487c19018 RCX: 0004 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473956] RDX: 895487c19490 RSI: 0047 RDI: 89548d9ce000 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473960] RBP: 964680e83b70 R08: 0001 R09: 895381c030c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473964] R10: 0001 R11: R12: ff18 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473969] R13: 0001 R14: 0047 R15: 0008 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473974] FS: () GS:8954cb28() knlGS: Sep 21 09:58:01 yeowool-Link kernel: [ 407.473979] CS: 0010 DS: ES: CR0: 80050033 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473984] CR2: ff95 CR3: 00010a7fc003 CR4: 001706e0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473990] Call Trace: Sep 21 09:58:01 yeowool-Link kernel: [ 407.473997] dspxfr_one_seg.constprop.0+0x30e/0x5e0 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474019] dspxfr_image.constprop.0+0x20a/0x440 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474036] dspload_image.constprop.0+0x5e/0x310 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474053] ca0132_download_dsp_images+0xc1/0x240 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474069] ca0132_download_dsp+0x145/0x180 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474086] ca0132_init+0xdc/0x540 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474101] hda_call_codec_resume+0x149/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474123] hda_codec_runtime_resume+0x3e/0x70 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474144] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474165] __rpm_callback+0x8c/0x160 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474172] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474196] rpm_callback+0x24/0x80 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474203] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474225] rpm_resume+0x52a/0x7e0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474232] ? __switch_to+0x1fb/0x400 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474241] pm_runtime_work+0x7d/0xa0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474248] process_one_work+0x220/0x3c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474256] worker_thread+0x50/0x370 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474263] kthread+0x11f/0x140 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474271] ? process_one_work+0x3c0/0x3c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474277] ? set_kthread_struct+0x50/0x50 Sep 21
[Kernel-packages] [Bug 1944402] [NEW] Chromebook Pixel 2013 not waking up from suspend
Public bug reported: I'm using a Chromebook Pixel 2013 (link) on Ubuntu 21.04 and my laptop wouldn't wake from suspend and show black screen despite I could hear the fan & lightbar LED running. This is the kernel bug part from the /var/log/syslog Sep 21 09:58:01 yeowool-Link kernel: [ 407.473841] BUG: unable to handle page fault for address: ff95 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473853] #PF: supervisor read access in kernel mode Sep 21 09:58:01 yeowool-Link kernel: [ 407.473858] #PF: error_code(0x) - not-present page Sep 21 09:58:01 yeowool-Link kernel: [ 407.473863] PGD 121415067 P4D 121415067 PUD 121417067 PMD 0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473875] Oops: [#1] SMP PTI Sep 21 09:58:01 yeowool-Link kernel: [ 407.473882] CPU: 1 PID: 1080 Comm: kworker/1:5 Not tainted 5.11.0-34-generic #36-Ubuntu Sep 21 09:58:01 yeowool-Link kernel: [ 407.473890] Hardware name: GOOGLE Link/Link, BIOS MrChromebox-4.14 07/25/2021 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473895] Workqueue: pm pm_runtime_work Sep 21 09:58:01 yeowool-Link kernel: [ 407.473907] RIP: 0010:snd_hda_codec_load_dsp_prepare+0x64/0x130 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.473937] Code: 00 00 00 8b 8b a0 05 00 00 4c 8d a0 18 ff ff ff eb 18 49 8b 84 24 e8 00 00 00 4c 8d a0 18 ff ff ff 48 39 c2 0f 84 8a 00 00 00 <41> 0f b6 44 24 7d 39 c8 75 de 4c 8d ab 98 04 00 00 4c 89 4d d0 4c Sep 21 09:58:01 yeowool-Link kernel: [ 407.473944] RSP: 0018:964680e83b38 EFLAGS: 00010286 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473951] RAX: RBX: 895487c19018 RCX: 0004 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473956] RDX: 895487c19490 RSI: 0047 RDI: 89548d9ce000 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473960] RBP: 964680e83b70 R08: 0001 R09: 895381c030c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473964] R10: 0001 R11: R12: ff18 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473969] R13: 0001 R14: 0047 R15: 0008 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473974] FS: () GS:8954cb28() knlGS: Sep 21 09:58:01 yeowool-Link kernel: [ 407.473979] CS: 0010 DS: ES: CR0: 80050033 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473984] CR2: ff95 CR3: 00010a7fc003 CR4: 001706e0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.473990] Call Trace: Sep 21 09:58:01 yeowool-Link kernel: [ 407.473997] dspxfr_one_seg.constprop.0+0x30e/0x5e0 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474019] dspxfr_image.constprop.0+0x20a/0x440 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474036] dspload_image.constprop.0+0x5e/0x310 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474053] ca0132_download_dsp_images+0xc1/0x240 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474069] ca0132_download_dsp+0x145/0x180 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474086] ca0132_init+0xdc/0x540 [snd_hda_codec_ca0132] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474101] hda_call_codec_resume+0x149/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474123] hda_codec_runtime_resume+0x3e/0x70 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474144] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474165] __rpm_callback+0x8c/0x160 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474172] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474196] rpm_callback+0x24/0x80 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474203] ? hda_call_codec_resume+0x160/0x160 [snd_hda_codec] Sep 21 09:58:01 yeowool-Link kernel: [ 407.474225] rpm_resume+0x52a/0x7e0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474232] ? __switch_to+0x1fb/0x400 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474241] pm_runtime_work+0x7d/0xa0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474248] process_one_work+0x220/0x3c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474256] worker_thread+0x50/0x370 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474263] kthread+0x11f/0x140 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474271] ? process_one_work+0x3c0/0x3c0 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474277] ? set_kthread_struct+0x50/0x50 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474285] ret_from_fork+0x22/0x30 Sep 21 09:58:01 yeowool-Link kernel: [ 407.474295] Modules linked in: exfat ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_ca0132 joydev snd_hda_intel intel_rapl_msr snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence isl29018 industrialio atmel_mxt_ts snd_hda_codec snd_hda_core intel_rapl_common
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
I wonder if it was the crash Nvidia mentioned in their latest release: https://www.nvidia.com/en-us/drivers/results/180475/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1939417] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu:
[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
Crash also confirmed in 5.14.0-051400drmtip20210904-generic (bug 1944122) ** 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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: New Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Comment #30 is a crash in the 'nvidia' kernel module. To work around that I can only recommend uninstalling the 470 driver and installing the 460 or 465 driver instead. ** Also affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.la
[Kernel-packages] [Bug 1944397] [NEW] hdmi-audio error breaks hdmi
Public bug reported: Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image impish package-from-proposed raspi-image -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1944397 Title: hdmi-audio error breaks hdmi Status in linux-raspi package in Ubuntu: New Bug description: Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user) SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1944397/+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 1913186] Re: Backport the adaptive engine from v2.4.1 upstream
This fix caused another bug: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389 -- 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/1913186 Title: Backport the adaptive engine from v2.4.1 upstream Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Groovy: Fix Released Bug description: Impact: DPTM provides an adaptive power policy that allows for improved integration between the platform and the OS. Firmware can provide a set of complex conditions to the OS, and an OS agent (in this case thermal_daemon) is responsible for evaluating them, potentially making use of information that is easily available to the OS and not the firmware. The agent evaluates each set of conditions in turn, and once the first evaluates completely it triggers a set of actions. Fix: Backport the adaptive engine (and all its dependencies) from upstream v.2.4.1 Regression potential: Both Focal and Groovy backports are substantial (Focal in particular is pretty large), so there's definitely a regression potential. On the other hand, the entire patchset is a clean backport, taking no shortcut or trying to adapt any patch, but rather picking up all the necessary dependencies to make the entire stack apply cleanly. -- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186/+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 1944389] Re: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
Try the upstream version https://github.com/intel/thermal_daemon May be missing some backports. -- 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/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1944389/+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 1912811] Re: Update dwarves-dfsg in focal to version 1.21 from impish
Uploaded new dwarves-dfsg SRUs that use embeded libbpf (which in turn is updated to the same source as used in impish). This makes dwarves-dfsg SRU stand-alone, without introducing or upgrading the system-wide libbpf. ** Changed in: libbpf (Ubuntu Focal) Status: Confirmed => Won't Fix ** Changed in: libbpf (Ubuntu Hirsute) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to libbpf in Ubuntu. https://bugs.launchpad.net/bugs/1912811 Title: Update dwarves-dfsg in focal to version 1.21 from impish Status in dwarves-dfsg package in Ubuntu: Invalid Status in libbpf package in Ubuntu: Fix Released Status in dwarves-dfsg source package in Focal: Confirmed Status in libbpf source package in Focal: Won't Fix Status in dwarves-dfsg source package in Groovy: Won't Fix Status in libbpf source package in Groovy: Won't Fix Status in dwarves-dfsg source package in Hirsute: Confirmed Status in libbpf source package in Hirsute: Won't Fix Bug description: [Impact] BTF is an extremely useful tool for BPF developers. Enabling BTF support in the HWE kernel requires pahole from dwarves-dfsg 1.21 or later, but in focal we have only 1.15. The simplest path for us to get a sufficiently updated version of pahole is to backport dwarves-dfsg from hirsute, which is at version 1.21 with v5.13 compat fixes. [Test Case] Building a v5.13 based kernel with CONFIG_DEBUG_INFO_BTF enabled fails with the version of pahole currently in focal, complaining that pahole 1.16 or later is needed. Building with a newer version of pahole is successful. [Where problems could occur] Moving the package forward carries significant risks. The biggest risk is clearly new bugs. There may also be interface changes which break existing workflows. I believe the following factors indicate that the level of risk here is acceptable: * Currently there are no bug reports open against the package in groovy (there are virtually no bug reports open at all against the package in fact). * I have done a review of the changes between 1.15 and 1.21. The bulk of the changes are for the required BTF support, and the vast majority of these are an update of its local copy of libbpf. The balance of the changes are bug fixes and enhancements to pahole, none of which look to change the user interface in a way which will break existing workflows. Note that in later releases libbpf is now packaged stand alone, so this SRU covers libbpf as well. * But also the 1.15 dwarves is kind of useless, as it doesn't work with latest kernels for the BPF features. * No packages in focal have dependencies or build dependencies on the dwarves package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dwarves-dfsg/+bug/1912811/+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 1944390] [NEW] Fix ignoring ct state match of OVS offload to TC/HW
Public bug reported: * Explain the bug When using OVS with tc to offload connection tracking flows, if user matches on ct_state other then trk and est, such as ct_state +rpl, it will be silently ignored by TC/HW and might result in wrong actions being executed. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules which match on ct_state +rpl and do different actions based on that match. e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, actions=$dev1" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, actions=$dev2" With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl match, and without they don't have, meaning the match is ignored. * What it could break. NA ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1944390 Title: Fix ignoring ct state match of OVS offload to TC/HW Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug When using OVS with tc to offload connection tracking flows, if user matches on ct_state other then trk and est, such as ct_state +rpl, it will be silently ignored by TC/HW and might result in wrong actions being executed. * How to test Create OVS bridge with 2 devices $dev1, $dev2 (can be any devices) Enable HW offload and configure connection tracking OpenFlow rules which match on ct_state +rpl and do different actions based on that match. e.g: ovs-ofctl del-flows br-ovs ovs-ofctl add-flow br-ovs arp,actions=normal ovs-ofctl add-flow br-ovs "table=0, ip,ct_state=-trk actions=ct(table=1)" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+new actions=ct(commit),normal" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est-rpl, actions=$dev1" ovs-ofctl add-flow br-ovs "table=1, ip,ct_state=+trk+est+rpl, actions=$dev2" With commits, ovs dump-flows (or tc show on devs) will have ct_state +rpl match, and without they don't have, meaning the match is ignored. * What it could break. NA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1944390/+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 1935855] Re: dbgsym contains no debug symbols
** Also affects: linux-kvm (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-kvm (Ubuntu Bionic) Assignee: (unassigned) => Kelsey Skunberg (kelsey-skunberg) ** Changed in: linux-kvm (Ubuntu Focal) Assignee: dann frazier (dannf) => Kelsey Skunberg (kelsey-skunberg) ** Changed in: linux-kvm (Ubuntu Bionic) Status: New => Fix Committed ** Changed in: linux-kvm (Ubuntu Focal) Status: In Progress => Fix Committed -- 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/1935855 Title: dbgsym contains no debug symbols Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Bionic: Fix Committed Status in linux-kvm source package in Focal: Fix Committed Status in linux-kvm source package in Hirsute: Fix Released Status in linux-kvm source package in Impish: Fix Released Bug description: [Impact] linux-image-unsigned-5.4.0-77-generic-dbgsym provides a /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any debug symbols. Turn on CONFIG_DEBUG_INFO to include those debug symbols. [Test Case] Compare: $ file /usr/lib/debug/boot/vmlinux-* /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not stripped [What Could Go Wrong] Since linux-kvm is tuned for performance, it's possible there's some side-effect of producing debug symbols that negatively impacts this. I've not noticed any issues empirically, but I didn't try to measure it. This config is already succesfully turned on in Hirsute/kvm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1935855/+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 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11
** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Assignee: (unassigned) => Dimitri John Ledkov (xnox) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939287 Title: dbgsym package is missing for ubuntu focal hwe kernel 5.11 Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in linux-hwe-5.13 source package in Focal: In Progress Bug description: [Impact] * Due to disk space constraints previously hwe-5.11 disabled building dbgsyms packages * This has been resolved in hwe-5.13, thus builds with debug symbols can be re-enabled [Test Plan] * Build new kernel, check that dbgsyms packages are published & have a debug image [Where problems could occur] * Build may grow in size, again, and fail to build from source, again. At the moment we don't see any such issues with v5.13 in impish. [Other Info] * Original Bug description: Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing from http://ddebs.ubuntu.com/dists/focal-updates/main/binary- amd64/Packages This breaks our workflow when the system is automatically upgraded from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic- dbgsym" for focal, which is also an HWE kernel. So why not do the same for 5.11.0 kernels? Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which depends on the unsigned one, but the latter does not exist. This seems to indicate something is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939287/+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 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11
** Description changed: + [Impact] + + * Due to disk space constraints previously hwe-5.11 disabled building + dbgsyms packages + + * This has been resolved in hwe-5.13, thus builds with debug symbols + can be re-enabled + + [Test Plan] + + * Build new kernel, check that dbgsyms packages are published & have a + debug image + + [Where problems could occur] + + * Build may grow in size, again, and fail to build from source, again. + At the moment we don't see any such issues with v5.13 in impish. + + [Other Info] + + * Original Bug description: + Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing from http://ddebs.ubuntu.com/dists/focal-updates/main/binary-amd64/Packages This breaks our workflow when the system is automatically upgraded from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic-dbgsym" for focal, which is also an HWE kernel. So why not do the same for 5.11.0 kernels? Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which depends on the unsigned one, but the latter does not exist. This seems to indicate something is broken. ** Changed in: linux-hwe-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-hwe-5.13 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939287 Title: dbgsym package is missing for ubuntu focal hwe kernel 5.11 Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: Confirmed Status in linux-hwe-5.11 source package in Focal: Confirmed Status in linux-hwe-5.13 source package in Focal: Confirmed Bug description: [Impact] * Due to disk space constraints previously hwe-5.11 disabled building dbgsyms packages * This has been resolved in hwe-5.13, thus builds with debug symbols can be re-enabled [Test Plan] * Build new kernel, check that dbgsyms packages are published & have a debug image [Where problems could occur] * Build may grow in size, again, and fail to build from source, again. At the moment we don't see any such issues with v5.13 in impish. [Other Info] * Original Bug description: Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing from http://ddebs.ubuntu.com/dists/focal-updates/main/binary- amd64/Packages This breaks our workflow when the system is automatically upgraded from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic- dbgsym" for focal, which is also an HWE kernel. So why not do the same for 5.11.0 kernels? Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which depends on the unsigned one, but the latter does not exist. This seems to indicate something is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939287/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Just did it again. This time, it didn't do a blackscreen outright. Rather, the audio just suddenly started insta-repeating, and the system clenched up and froze, and became completely unresponsive. Is there anything I can do to help figure out what the problem is? Any sort of tests I can run? Having my computer Epstein itself multiple times a day is getting seriously infuriating. ** Attachment added: "prevboot-2021-09-20-b.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5526557/+files/prevboot-2021-09-20-b.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.
[Kernel-packages] [Bug 1944389] [NEW] Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz
Public bug reported: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 ** Affects: thermald (Ubuntu) Importance: Undecided Status: New -- 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/1944389 Title: Thermald 1.9.1-1ubuntu0.6 keeps Tigerlake GPU frequency on 400 MHz Status in thermald package in Ubuntu: New Bug description: After update to 1.9.1-1ubuntu0.6 from 1.9.1-1ubuntu0.4 thermald keeps Tigerlake Iris Xe GPU frequency on 400 MHz after reaching some high temperature value. It became impossible to play video games on the laptop. System: Ubuntu 20.04.3 LTS Kernel: 5.10.0-1045-oem Laptop: Dell XPS 9310, CPU: Intel Core i7-1165G7 (Tigerlake), Integrated GPU Iris Xe. BIOS 2.1.1 03/25/2021 Display: 2560x1440 144Hz HDMI USB-C connection Room temperature is 23.5-25.4 degrees Game: Stalker Clear Sky (Wine/Proton Steam) Note: The game itself is very old and loads 100% of one CPU core disregarding of frequency. GPU frequency is monitored by intel-gpu-top GPU frequencies (according to /sys/class/drm/card0/) min/max/boost/efficiency: 100/1300/1300/400 Previous behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. After some time when threshold temperature value (~78 degrees) is reached the GPU frequency decreases to ~660 MHz and FPS to 40-48 FPS. Package temperature decreases to 66-68 degrees. It's possible to play for indefinite amount of time. New behavior (1.9.1-1ubuntu0.4) After starting the game at first GPU reaches the boost value of 1300 MHz and CPU/package temperatures continuously increase. At this point game renders at ~80FPS. But after reaching the threshold temperature (about 81 degrees) GPU frequency decreases to 400 MHz (gt_RP1_freq_mhz -- "efficiency" temperature for the GPU) and stays on this value for the indefinite amount of time. The temperature is maintained on 70-74 degrees. FPS is about 25-30 FPS, it is not possible to play the game anymore. The only way to return the good FPS and frequency is to fold the game window, wait some time and open it again. Also there is a workaround -- limit the CPU frequency to 2001 MHz and disable Intel turbo boost. With such approach package temperature never reaches 80 degrees and it is possible to play game with 500 MHz and 35-40 FPS. Better than nothing. If it is needed I can perform any additional checks, provide CPU frequencies and so on. Most probably regression happened with 1.9.1-1ubuntu0.5, but I tried only versions 0.4 and 0.6 To manage notific
[Kernel-packages] [Bug 1935855] Re: dbgsym contains no debug symbols
** Description changed: [Impact] - linux-image-unsigned-5.4.0-77-generic-dbgsym provides a /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any debug symbols. + + linux-image-unsigned-5.4.0-77-generic-dbgsym provides a + /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any + debug symbols. + + Turn on CONFIG_DEBUG_INFO to include those debug symbols. [Test Case] + Compare: $ file /usr/lib/debug/boot/vmlinux-* /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not stripped [What Could Go Wrong] - linux-kvm seems heavily tuned for performance (quick booting?) - it's possible that there's some side-effect of producing debug symbols that negatively impacts this. I've not noticed any issues empirically, but I didn't try to measure it. + + Since linux-kvm is tuned for performance, it's possible there's some + side-effect of producing debug symbols that negatively impacts this. I've not + noticed any issues empirically, but I didn't try to measure it. + + This config is already succesfully turned on in Hirsute/kvm. -- 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/1935855 Title: dbgsym contains no debug symbols Status in linux-kvm package in Ubuntu: Fix Released Status in linux-kvm source package in Focal: In Progress Status in linux-kvm source package in Hirsute: Fix Released Status in linux-kvm source package in Impish: Fix Released Bug description: [Impact] linux-image-unsigned-5.4.0-77-generic-dbgsym provides a /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm, but it does not contain any debug symbols. Turn on CONFIG_DEBUG_INFO to include those debug symbols. [Test Case] Compare: $ file /usr/lib/debug/boot/vmlinux-* /usr/lib/debug/boot/vmlinux-5.4.0-1040-kvm: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=514891d64a7d18db4fa58aa5cfea213e0951ca9d, not stripped /usr/lib/debug/boot/vmlinux-5.4.0-77-generic: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, BuildID[sha1]=773d8ee85333fe092635f65d2b6850909085c11d, with debug_info, not stripped [What Could Go Wrong] Since linux-kvm is tuned for performance, it's possible there's some side-effect of producing debug symbols that negatively impacts this. I've not noticed any issues empirically, but I didn't try to measure it. This config is already succesfully turned on in Hirsute/kvm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1935855/+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 1937296] Re: Kernel Hang During "Loading initial ramdisk..."
On a personal note, I'm unable to be productive at work because I can no longer find a kernel that will boot with networking in a non-line environment. Never had this happen with the Debian installation I have on System76 (but not-Serval) hardware I have at home. 5.11.0-7620-generic never booted. 5.11.0-7633-generic never booted. -- 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/1937296 Title: Kernel Hang During "Loading initial ramdisk..." Status in System76: New Status in linux package in Ubuntu: Incomplete Bug description: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1937296/+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 1937296] Re: Kernel Hang During "Loading initial ramdisk..."
5.11.0-7614-generic was updated last week, and no longer boots. 5.13.0-7614-generic had never booted. 5.8.0-43-generic boots, but comes up without audio devices or network devices (neither wired nor wireless). This is particularly weird since the Ubuntu Live environment I'm writing this update from is using 5.8.0-43, and has both audio and networking working fine. 5.4.0-84-generic boots, but comes up without audio devices or network devices. I still need to try 5.4.0-26, but I'm not hopeful. -- 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/1937296 Title: Kernel Hang During "Loading initial ramdisk..." Status in System76: New Status in linux package in Ubuntu: Incomplete Bug description: This is specific to the System 76 PPA. linux-image-5.11.0-7614-generic boots with no problems. ``` % uname -a Linux system76-pc 5.11.0-7614-generic #15~1622578982~20.04~383c0a9~dev-Ubuntu SMP Wed Jun 2 00:50:47 U x86_64 x86_64 x86_64 GNU/Linux ``` linux-image-5.11.0-7620-generic hangs at "Loading initial ramdisk...". This is true in recovery mode as well. /etc/os-release: ``` NAME="Ubuntu" VERSION="20.04.2 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.2 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ``` Hardware is Serval: ``` System Information Manufacturer: System76 Product Name: Serval Version: serw11-b UUID: 6c5bfa80-9b7c--- Wake-up Type: Power Switch ``` All packages / firmware is up-to-date, and EFI was updated a couple of months ago. To manage notifications about this bug go to: https://bugs.launchpad.net/system76/+bug/1937296/+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 1943030] Re: Enable riscv64 build of nvidia-settings
This bug was fixed in the package nvidia-settings - 470.57.01-0ubuntu3 --- nvidia-settings (470.57.01-0ubuntu3) impish; urgency=medium * control: Enable build of nvidia-settings package on riscv64. (LP: #1943030) -- Alexandre Ghiti Thu, 16 Sep 2021 11:11:52 -0700 ** Changed in: nvidia-settings (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1943030 Title: Enable riscv64 build of nvidia-settings Status in nvidia-settings package in Ubuntu: Fix Released Bug description: Please enable the build on riscv64 architecture of nvidia-settings since it works fine using the attached debdiff: https://launchpad.net/~alexghiti/+archive/ubuntu/riscv/+build/22050736 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1943030/+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 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
And another blackscreen from just now. Do these logs say anything useful? It happens at the absolute minimum, at least once a day. These constant crashes are getting seriously infuriating. It doesn't happen on Kubuntu. Just Xubuntu. Is there anything I can do to help you guys diagnose the problem? ** Attachment added: "prevboot-2021-09-20.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5526499/+files/prevboot-2021-09-20.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226
[Kernel-packages] [Bug 1922334] Re: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16)
Latest BIOS 1.9.1, TBT firmware v65, TB16 firmware 1.0.5 and kernel 5.13.0-1012-oem still affected -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1922334 Title: External monitor does not wake up on Titan Ridge laptops when docked (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: In Progress Status in linux-meta-oem-5.6 package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock and an external monitor (Benq EX2780Q) connected to the dock via USB-C to USB-C (DP alternate mode), most of the time the monitor fails to wake up after going blank. details: Simplest way to reproduce is for hit Super+L, wait for the monitor to properly go in standby, then type something in or move the mouse to wake it up. 8 times out of 10 it does not wake up when using XPS 9500. Most of the time this can be fixed by power cycling the monitor, however this has a seemingly random chance of triggering two other issues: 1. The system to lose sight of the monitor for a brief period of time, which sometimes causes it to hang with a black screen and needs some combination of restarting the monitor, the dock, and the laptop, because there is a separate USB issue making hot-plugging unusable. 2. The monitor itself gets stuck in a weird standby state where it stops reacting to button presses and I need to hold the power button a bit longer for it to sort of hard reset? Notably, it wakes up fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages. This becomes particularly troublesome when screens go into short-lived standby during boot: after the Dell logo, after entering the LUKS password, after logging in. Each of these points has a chance of triggering the bug, because it looks like there is some sort of mode change and waking signal submission happening between them that triggers it. I had to disable screen timeout as a temporary workaround to be able to work on this system at all without having to play "monitor wake lottery" every time I go brew a cuppa. The workaround at boot time is to either re-roll the lottery, or boot with the dock connected and lid open, then close the lid and keep working from there. The dock, the monitor, all USB peripherals are the same in both cases - it's literally just the TB16 cable plugged into a different laptop. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted disabling USB autosuspend via a GRUB kernel parameter to usbcore. I have attempted both NVidia and Intel GPUs. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik and several reports of the same problem scattered across the internet: https://www.dell.com/community/XPS/XPS-13-9300-with-WD19TB-External-display-not-coming-on-after/td-p/7676922 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342 (may be a duplicate, but for WD19TB dock on 9300, so may be slightly different too) https://www.reddit.com/r/linuxquestions/comments/ka0w2j/monitor_doesnt_wake_from_sleep/ etc etc. Those reports suggest high bandwidth usage sometimes affects it, so it's worth noting that my external monitor is a 1440p 144Hz one that uses tons of bandwidth indeed. The only hint in terms of logs seems to be this message in dmesg that I see when power cycling the monitor and getting back into the system: [ 250.777684] pcieport :09:04.0: pciehp: Slot(0-1): Card not present [ 250.777695] xhci_hcd :0b:00.0: can't change power state from D3cold to D0 (config space inaccessible) [ 250.778293] xhci_hcd :0b:00.0: can't change power state from D3hot to D0 (config space inaccessible) [ 250.778336] xhci_hcd :0b:00.0: Control
[Kernel-packages] [Bug 1944212] [NEW] Focal update: v5.4.143 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.143 upstream stable release from git://git.kernel.org/ ext4: fix EXT4_MAX_LOGICAL_BLOCK macro x86/fpu: Make init_fpstate correct with optimized XSAVE ath: Use safer key clearing with key cache entries ath9k: Clear key cache explicitly on disabling hardware ath: Export ath_hw_keysetmac() ath: Modify ath_key_delete() to not need full key entry ath9k: Postpone key cache entry deletion for TXQ frames reference it mtd: cfi_cmdset_0002: fix crash when erasing/writing AMD cards media: zr364xx: propagate errors from zr364xx_start_readpipe() media: zr364xx: fix memory leaks in probe() media: drivers/media/usb: fix memory leak in zr364xx_probe USB: core: Avoid WARNings for 0-length descriptor requests dmaengine: xilinx_dma: Fix read-after-free bug when terminating transfers dmaengine: usb-dmac: Fix PM reference leak in usb_dmac_probe() ARM: dts: am43x-epos-evm: Reduce i2c0 bus speed for tps65218 dmaengine: of-dma: router_xlate to return -EPROBE_DEFER if controller is not yet available scsi: megaraid_mm: Fix end of loop tests for list_for_each_entry() scsi: scsi_dh_rdac: Avoid crash during rdac_bus_attach() scsi: core: Avoid printing an error if target_alloc() returns -ENXIO scsi: core: Fix capacity set to zero after offlinining device ARM: dts: nomadik: Fix up interrupt controller node names net: usb: lan78xx: don't modify phy_device state concurrently drm/amd/display: Fix Dynamic bpp issue with 8K30 with Navi 1X Bluetooth: hidp: use correct wait queue when removing ctrl_wait iommu: Check if group is NULL before remove device cpufreq: armada-37xx: forbid cpufreq for 1.2 GHz variant dccp: add do-while-0 stubs for dccp_pr_debug macros virtio: Protect vqs list access vhost: Fix the calculation in vhost_overflow() bpf: Clear zext_dst of dead insns bnxt: don't lock the tx queue from napi poll bnxt: disable napi before canceling DIM net: 6pack: fix slab-out-of-bounds in decode_data ptp_pch: Restore dependency on PCI bnxt_en: Add missing DMA memory barriers vrf: Reset skb conntrack connection on VRF rcv virtio-net: support XDP when not more queues virtio-net: use NETIF_F_GRO_HW instead of NETIF_F_LRO net: qlcnic: add missed unlock in qlcnic_83xx_flash_read32 net: mdio-mux: Don't ignore memory allocation errors net: mdio-mux: Handle -EPROBE_DEFER correctly ovs: clear skb->tstamp in forwarding path i40e: Fix ATR queue selection iavf: Fix ping is lost after untrusted VF had tried to change MAC ovl: add splice file read write helper mmc: dw_mmc: Fix hang on data CRC error ALSA: hda - fix the 'Capture Switch' value change notifications tracing / histogram: Fix NULL pointer dereference on strcmp() on NULL event name slimbus: messaging: start transaction ids from 1 instead of zero slimbus: messaging: check for valid transaction id slimbus: ngd: reset dma setup during runtime pm ipack: tpci200: fix many double free issues in tpci200_pci_probe ipack: tpci200: fix memory leak in the tpci200_register btrfs: prevent rename2 from exchanging a subvol with a directory from different parents PCI: Increase D3 delay for AMD Renoir/Cezanne XHCI ASoC: intel: atom: Fix breakage for PCM buffer address setup mm, memcg: avoid stale protection values when cgroup is above protection mm: memcontrol: fix occasional OOMs due to proportional memory.low reclaim fs: warn about impending deprecation of mandatory locks netfilter: nft_exthdr: fix endianness of tcp option cast Linux 5.4.143 UBUNTU: upstream stable to v5.4.143 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating eithe
[Kernel-packages] [Bug 1922336] Re: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16)
FWIW, the C-states workaround from this post works for me and resolves the hot-plugging issue with TB16: https://www.dell.com/community/XPS/XPS-13-9300-and-WD19TB-linux- problem/m-p/7842208/highlight/true#M81522 Currently running BIOS 1.9.1, TBT firmware V65, TB16 firmware 1.0.5 and kernel 5.13.0-1012-oem. I hope this helps pin down the bug or at least becomes useful for others who run into this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1922336 Title: ACPI errors and USB reset loop when hot-plugging a Titan Ridge laptop into a dock (9500, TB16) Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Status in linux-meta-oem-5.6 package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: New Status in linux-oem-5.13 package in Ubuntu: New Bug description: I've recently upgraded my workhorse from XPS 9560 (2016) to a newer generation XPS 9500 (2020) and ran into several things that feel like regressions, but are probably related to hardware changes. This is one of them. tl;dr: When using XPS 9500 with a TB16 dock, hot-plugging the dock causes ACPI errors in dmesg and some kind of reset loop with USB peripherals connected via the dock. details: USB peripherals keep reconnecting according to dmesg, but in practice they barely ever finish registering with the system before disappearing again. Maybe 1 out of 40 USB keyboard presses registers while this is happening. At this point my choices are to either reboot with the dock connected or work without the dock and consequently without any peripherals on my desk. Booting with an open lid and the dock connected works fine until I re-plug the dock. Notably, it hot-plugs fine every time when using XPS 9560 or Precision 5520 in the same setup which I have been using for ages and which had similar problems until around kernel 4.13. Since it was fine with 9560, 5520 and a friend with a 9570 has no issues either, my gut feeling is that this is due to the upgrade from Alpine Ridge to a Titan Ridge Thunderbolt controller that happened in this generation - something wrong with the driver, or the firmware may have missed some of the "lessons learned" in Alpine Ridge and caused this regression. That would also make it applicable to 9300, which has a "developer edition" option under Project Sputnik. I have attempted 5.8 Ubuntu generic, 5.6 OEM (-20.04) and 5.10 OEM (-20.04b and -20.04-edge) kernels on the 9500 with same results. I have attempted rebinding the XHCI controller after reconnecting the dock. I have attempted disabling USB autosuspend and ASPM via a GRUB kernel parameter. I have attempted playing with BIOS settings: wake on dell usb-c docks, disable early sign of life for both checkboxes, disabling SGX and SMM, checking all 3 boxes for Thunderbolt and switching off Thunderbolt security. None of these make a noticeable difference. System config: XPS 9500, i7, 32GB RAM BIOS 1.6.1, TB3 firmware NVM60 Ubuntu 20.04.02 LTS, kernels 5.6-oem, 5.8-generic, 5.10-oem (same behaviour) TB16 dock firmware 1.0.4 (MST 3.12.02) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: gboiko 1990 F pulseaudio /dev/snd/controlC2: gboiko 1990 F pulseaudio /dev/snd/controlC1: gboiko 1990 F pulseaudio /dev/snd/controlC0: gboiko 1990 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-03-31 (6 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Dell Inc. XPS 15 9500 NonfreeKernelModules: nvidia_modeset nvidia Package: linux-meta-oem-5.6 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.6.0-1052-oem root=/dev/mapper/vgubuntu-root ro net.ifnames=0 biosdevname=0 ipv6.disable=1 quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1052.56-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1052-oem N/A linux-backports-modules-5.6.0-1052-oem N/A linux-firmware 1.187.10 Tags: focal Uname: Linux 5.6.0-1052-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/24/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0RHXRG dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn0RHXRG:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9500
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Okay, not exactly the same thing. It didn't do the blackscreen crash. What happened this time was that it stopped accepting input from the keyboard. I have no idea if it's related, but it might be, so I'm sending this one anyway. Maybe it might have some helpful answers. ** Attachment added: "prevboot-2021-09-19-desktop-and-keyboard-lockup.txt" https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939966/+attachment/5526477/+files/prevboot-2021-09-19-desktop-and-keyboard-lockup.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video
[Kernel-packages] [Bug 1944202] [NEW] Focal update: v5.4.142 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.142 upstream stable release
from git://git.kernel.org/
iio: adc: ti-ads7950: Ensure CS is deasserted after reading channels
iio: humidity: hdc100x: Add margin to the conversion time
iio: adc: Fix incorrect exit of for-loop
ASoC: xilinx: Fix reference to PCM buffer address
ASoC: intel: atom: Fix reference to PCM buffer address
i2c: dev: zero out array used for i2c reads from userspace
ceph: reduce contention in ceph_check_delayed_caps()
ACPI: NFIT: Fix support for virtual SPA ranges
libnvdimm/region: Fix label activation vs errors
ieee802154: hwsim: fix GPF in hwsim_set_edge_lqi
ieee802154: hwsim: fix GPF in hwsim_new_edge_nl
ASoC: cs42l42: Correct definition of ADC Volume control
ASoC: cs42l42: Don't allow SND_SOC_DAIFMT_LEFT_J
ASoC: cs42l42: Fix inversion of ADC Notch Switch control
ASoC: cs42l42: Remove duplicate control for WNF filter frequency
netfilter: nf_conntrack_bridge: Fix memory leak when error
ASoC: cs42l42: Fix LRCLK frame start edge
net: dsa: mt7530: add the missing RxUnicast MIB counter
platform/x86: pcengines-apuv2: revert wiring up simswitch GPIO as LED
platform/x86: pcengines-apuv2: Add missing terminating entries to gpio-lookup
tables
net: phy: micrel: Fix link detection on ksz87xx switch"
ppp: Fix generating ifname when empty IFLA_IFNAME is specified
net: sched: act_mirred: Reset ct info when mirror/redirect skb
iavf: Set RSS LUT and key in reset handle path
psample: Add a fwd declaration for skbuff
net/mlx5: Fix return value from tracer initialization
drm/meson: fix colour distortion from HDR set during vendor u-boot
net: dsa: microchip: Fix ksz_read64()
net: Fix memory leak in ieee802154_raw_deliver
net: igmp: fix data-race in igmp_ifc_timer_expire()
net: dsa: lan9303: fix broken backpressure in .port_fdb_dump
net: dsa: lantiq: fix broken backpressure in .port_fdb_dump
net: dsa: sja1105: fix broken backpressure in .port_fdb_dump
net: bridge: fix memleak in br_add_if()
net: linkwatch: fix failure to restore device state across suspend/resume
tcp_bbr: fix u32 wrap bug in round logic if bbr_init() called after 2B packets
net: igmp: increase size of mr_ifc_count
xen/events: Fix race in set_evtchn_to_irq
vsock/virtio: avoid potential deadlock when vsock device remove
nbd: Aovid double completion of a request
powerpc/kprobes: Fix kprobe Oops happens in booke
x86/tools: Fix objdump version check again
genirq: Provide IRQCHIP_AFFINITY_PRE_STARTUP
x86/msi: Force affinity setup before startup
x86/ioapic: Force affinity setup before startup
x86/resctrl: Fix default monitoring groups reporting
genirq/msi: Ensure deactivation on teardown
genirq/timings: Prevent potential array overflow in __irq_timings_store()
PCI/MSI: Enable and mask MSI-X early
PCI/MSI: Mask all unused MSI-X entries
PCI/MSI: Enforce that MSI-X table entry is masked for update
PCI/MSI: Enforce MSI[X] entry updates to be visible
PCI/MSI: Do not set invalid bits in MSI mask
PCI/MSI: Correct misleading comments
PCI/MSI: Use msi_mask_irq() in pci_msi_shutdown()
PCI/MSI: Protect msi_desc::masked for multi-MSI
KVM: VMX: Use current VMCS to query WAITPKG support for MSR emulation
ceph: add some lockdep assertions around snaprealm handling
ceph: clean up locking annotation for ceph_get_snap_realm and
__lookup_snap_realm
ceph: take snap_empty_lock atomically with snaprealm refcount change
vmlinux.lds.h: Handle clang's module.{c,d}tor sections
iommu/vt-d: Fix agaw for a supported 48 bit guest address width
Linux 5.4.142
UBUNTU: upstream stable to v5.4.142
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Invalid
** Affects: linux (Ubuntu Focal)
Importance: Medium
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is
[Kernel-packages] [Bug 1939417] Re: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu 0000:09:00.0: [gfxhub0] retry page fault
sorry, my stupid fault. Now it says peter:~/Downloads$ uname -a Linux peter 5.14.0-051400drmtip20210904-generic #202109040225 SMP Sat Sep 4 02:34:06 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux And I'll keep looking at it. Sorry for the confusion. -- 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/1939417 Title: Ubuntu GUI crashes (w and w/o Wayland), VM_L2_PROTECTION_FAULT, amdgpu :09:00.0: [gfxhub0] retry page fault Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu GUI crashes (w and w/o Wayland) on AMD Ryzen 5 3400G with Radeon Vega Graphics (family: 0x17, model: 0x18, stepping: 0x1) sometimes total OS crash, sometimes ssh access still possible. 1) The release of Ubuntu you are using Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal 2) The version of the package you are using the GUI crashes at different times in different situations, no specific application or package identified. 3) What you expected to happen Ubuntu working, applications like LibreOffice do their job. 4) What happened instead After some time of successful work (from seconds to hour) suddenly no input by keyboard possible; OS crashes: GUI frozen, most times mouse movement frozen (sometimes not), one time flickering GUI. Sometimes remote ssh reboot possible. Sometimes not even successful ping to the network interface possible. No results: Tried to start "Ubuntu" w/o Wayland, same issue as "Ubuntu with Wayland"; several reboots; no issues experienced when accessing machine via ssh (remote). Using application like LibreOffice or OracleVM or Nemo via remote ssh (IPv6) did not show this issue. dmesg says when crashed: [ 4926.673857] [drm] enabling link 0 failed: 15 [ 6478.430465] gmc_v9_0_process_interrupt: 15 callbacks suppressed [ 6478.430474] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430481] amdgpu :09:00.0: in page starting at address 0x80010ea95000 from client 27 [ 6478.430484] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430487] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430490] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430492] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430495] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430497] amdgpu :09:00.0: RW: 0x0 [ 6478.430506] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6478.430509] amdgpu :09:00.0: in page starting at address 0x80010eac9000 from client 27 [ 6478.430511] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6478.430514] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6478.430516] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6478.430518] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6478.430520] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6478.430522] amdgpu :09:00.0: RW: 0x0 [ 6478.430530] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:c s0 pid 7854) [ 6488.436541] amdgpu :09:00.0: [gfxhub0] retry page fault (src_id:0 ring:0 vmid:3 pasid:32772, for process Xorg pid 7853 thread Xorg:cs0 pid 7854) [ 6488.436542] amdgpu :09:00.0: in page starting at address 0x80010eae3000 from client 27 [ 6488.436544] amdgpu :09:00.0: VM_L2_PROTECTION_FAULT_STATUS:0x00301031 [ 6488.436545] amdgpu :09:00.0: MORE_FAULTS: 0x1 [ 6488.436546] amdgpu :09:00.0: WALKER_ERROR: 0x0 [ 6488.436547] amdgpu :09:00.0: PERMISSION_FAULTS: 0x3 [ 6488.436548] amdgpu :09:00.0: MAPPING_ERROR: 0x0 [ 6488.436549] amdgpu :09:00.0: RW: 0x0 [ 6488.615178] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, but soft recovered --- --- [0.00] Linux version 5.4.0-80-generic (buildd@lcy01-amd64-030) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #90-Ubuntu SMP Fr i Jul 9 22:49:44 UTC 2021 (Ubuntu 5.4.0-80.90-generic 5.4.124) [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.4.0-80-generic root=UUID=2fac2ccc-b353-4ced-a8e5-7e5a7f0fe5f3 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/
[Kernel-packages] [Bug 1944104] Re: nested vm on vm not running
Thanks Masato, since thta sounds more like an issue in the kernel you refer to I have added a bug task for `linux-oem-5.13` to be triaged from the kernel POV as well. ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1944104 Title: nested vm on vm not running Status in linux-oem-5.13 package in Ubuntu: New Status in qemu package in Ubuntu: Incomplete Bug description: The host machine ubuntu 20.04 kernel is 5.13.0-1012-oem, When the kernel of the guest machine is ubuntu 20.04 kernel 5.4.0-84-generic, vm cannot be started on the guest machine. - KVM: entry failed, hardware error 0x7 EAX= EBX= ECX= EDX=000a0671 ESI= EDI= EBP= ESP= EIP=fff0 EFL=0002 [---] CPL=0 II=0 A20=1 SMM=0 HLT=0 ES = 9300 CS =f000 9b00 SS = 9300 DS = 9300 FS = 9300 GS = 9300 LDT= 8200 TR = 8b00 GDT= IDT= CR0=6010 CR2= CR3= CR4= DR0= DR1= DR2= DR3= DR6=0ff0 DR7=0400 EFER= Code=90 90 90 90 eb c3 90 90 90 90 90 90 00 00 00 00 56 54 46 00 <90> 90 eb ac 90 90 90 90 90 90 90 90 90 90 90 90 00 00 00 00 00 00 00 00 00 00 00 00 00 00 - host kernel 5.4.0-84-generic gust kernel 5.4.0-84-generic: OK gust kernel 5.13.0-1012-oem : OK host kernel 5.13.0-1012-oem gust kernel 5.4.0-84-generic: NG gust kernel 5.13.0-1012-oem : OK ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu-system-x86 1:4.2-3ubuntu6.17 ProcVersionSignature: Ubuntu 5.4.0-84.94-generic 5.4.133 Uname: Linux 5.4.0-84-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: pass Date: Mon Sep 20 14:05:09 2021 ExecutablePath: /usr/bin/qemu-system-x86_64 InstallationDate: Installed on 2021-09-20 (0 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcEnviron: PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-84-generic root=/dev/mapper/vg-lv_root ro intel_iommu=on amd_iommu=on SourcePackage: qemu UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: EFI Development Kit II / OVMF dmi.bios.version: 0.0.0 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.13/+bug/1944104/+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 1939287] Re: dbgsym package is missing for ubuntu focal hwe kernel 5.11
** Also affects: linux-hwe-5.13 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1939287 Title: dbgsym package is missing for ubuntu focal hwe kernel 5.11 Status in linux-hwe-5.11 package in Ubuntu: Confirmed Status in linux-hwe-5.13 package in Ubuntu: New Status in linux-hwe-5.11 source package in Focal: Confirmed Status in linux-hwe-5.13 source package in Focal: New Bug description: Package "linux-image-unsigned-5.11.0-25-generic-dbgsym" is missing from http://ddebs.ubuntu.com/dists/focal-updates/main/binary- amd64/Packages This breaks our workflow when the system is automatically upgraded from 5.8.0 to 5.11.0. We have "linux-image-unsigned-5.8.0-63-generic- dbgsym" for focal, which is also an HWE kernel. So why not do the same for 5.11.0 kernels? Also, on focal, we have "linux-image-5.11.0-25-generic-dbgsym", which depends on the unsigned one, but the latter does not exist. This seems to indicate something is broken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1939287/+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 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64
** Tags added: sru-20210906 -- 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/1836169 Title: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux source package in Focal: Confirmed Bug description: This issue can be found on both ThunderX and Moonshot ARM64 <<>> incrementing stop Name: cpuhotplug04 Date: Thu Jul 11 08:34:50 UTC 2019 Desc: Does it prevent us from offlining the last CPU? sh: echo: I/O error cpuhotplug04 1 TFAIL: Could not offline cpu0 <<>> initiation_status="ok" duration=0 termination_type=exited termination_id=1 corefile=no cutime=9 cstime=4 <<>> Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug04 cpuhotplug04.sh -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jul 11 08:28:42 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-25-generic N/A linux-backports-modules-4.18.0-25-generic N/A linux-firmware 1.175.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+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 1944103] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1944103 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** 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/1944103 Title: ubuntu suspends even if automatic suspend is disabled Status in linux package in Ubuntu: Incomplete Bug description: Even if automatic suspend is disabled in "Power Saving" settings, my computer will suspend after minutes of inactivity if disconnected from power. Other users are experiencing the same issue since 20.04 and apparently the only way out of this is to "systemctl mask suspend.target" https://itectec.com/ubuntu/ubuntu-ubuntu-20-04-suspends-when-idle- even-if-relevant-power-settings-are-disabled/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944103/+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 1944103] Re: ubuntu suspends even if automatic suspend is disabled
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1944103 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. ** Package changed: ubuntu => linux (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/1944103 Title: ubuntu suspends even if automatic suspend is disabled Status in linux package in Ubuntu: Incomplete Bug description: Even if automatic suspend is disabled in "Power Saving" settings, my computer will suspend after minutes of inactivity if disconnected from power. Other users are experiencing the same issue since 20.04 and apparently the only way out of this is to "systemctl mask suspend.target" https://itectec.com/ubuntu/ubuntu-ubuntu-20-04-suspends-when-idle- even-if-relevant-power-settings-are-disabled/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944103/+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 1944103] [NEW] ubuntu suspends even if automatic suspend is disabled
You have been subscribed to a public bug: Even if automatic suspend is disabled in "Power Saving" settings, my computer will suspend after minutes of inactivity if disconnected from power. Other users are experiencing the same issue since 20.04 and apparently the only way out of this is to "systemctl mask suspend.target" https://itectec.com/ubuntu/ubuntu-ubuntu-20-04-suspends-when-idle-even- if-relevant-power-settings-are-disabled/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- ubuntu suspends even if automatic suspend is disabled https://bugs.launchpad.net/bugs/1944103 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1901470] Re: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1920x1080 instead
** Tags added: hirsute -- 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/1901470 Title: [i915] HDMI monitor's native resolution (EDID detailed mode) not available, defaults to 1920x1080 instead Status in linux package in Ubuntu: Confirmed Bug description: The PG278QR monitor supports 2560x1440. After installing Ubuntu 20.4, the max resolution presented in the Settings app is 1920x1080, and this resolution is the one that it uses. Switching between the Nvidia driver or the Intel driver (laptop has low-power intel gpu too) doesn't correct the problem. Digging in deeper, based on https://wiki.ubuntu.com/X/Troubleshooting/Resolution#Problem:__Wrong_resolutions.2C_refresh_rates.2C_or_monitor_specs Under Wrong resolutions/refresh rates/or monitor specs, step 3 is to use get-edid | parse-edid. After applying the mode that I wanted manually via xrandr --newmode and xrandr --addmode, I was able to select the max resolution of the monitor and works correctly, until reboot. I will add it to my xorg.conf next. Here is information I collected: output from xrandr after fresh boot: ~$ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.01*+ 60.0159.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 HDMI-1-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 598mm x 336mm 1920x1080 60.00* 50.0059.94 1280x720 60.0050.0059.94 1024x768 60.00 800x600 60.32 720x576 50.00 720x480 60.0059.94 640x480 60.0059.94 DP-1-1 disconnected (normal left inverted right x axis y axis) output from get-edid | parse-edid: ~$ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 9 No EDID on bus 10 3 potential busses found: 0 4 8 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 256-byte EDID successfully retrieved from i2c bus 4 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "ROG PG278QR" ModelName "ROG PG278QR" VendorName "AUS" # Monitor Manufactured week 47 of 2016 # EDID version 1.3 # Digital Display DisplaySize 600 340 Gamma 2.20 Option "DPMS" "false" Horizsync 30-140 VertRefresh 24-60 # Maximum pixel clock is 300MHz #Extension block found. Parsing... Modeline"Mode 1" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 0" 241.50 2560 2608 2640 2720 1440 1443 1448 1481 +hsync -vsync Modeline"Mode 2" 148.500 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync Modeline"Mode 3" 74.250 1280 1390 1420 1650 720 725 730 750 +hsync +vsync Modeline"Mode 4" 74.250 1280 1720 1760 1980 720 725 730 750 +hs
