[Kernel-packages] [Bug 1989164] [NEW] 5.15.0-47
Public bug reported: With kernel 5.15.0-47 in Linux Mint, all Windows and Linux VirtualBox machines have problems. Softwares in these VM are crashing, checksum of downloaded packages are bad etc. https://forums.linuxmint.com/viewtopic.php?f=231=381272 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Description changed: - With kernel 5.15.0-47 in Linux Mint, all Windows and Linux VirtualBox machines have problems. Softwares in these VM are crashing, checksum are bed etc. + With kernel 5.15.0-47 in Linux Mint, all Windows and Linux VirtualBox machines have problems. Softwares in these VM are crashing, checksum of downloaded packages are bad etc. https://forums.linuxmint.com/viewtopic.php?f=231=381272 -- 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/1989164 Title: 5.15.0-47 Status in linux package in Ubuntu: New Bug description: With kernel 5.15.0-47 in Linux Mint, all Windows and Linux VirtualBox machines have problems. Softwares in these VM are crashing, checksum of downloaded packages are bad etc. https://forums.linuxmint.com/viewtopic.php?f=231=381272 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989164/+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 1989162] [NEW] The r8188eu kernel module does not depend on the rtlwifi/rtl8188eufw.bin firmware file in the 20.04 HWE kernel
Public bug reported: I would like to use a Wi-Fi card supported by the r8188eu kernel module in the initramfs, in Ubuntu 20.04. I add the module using a custom initramfs-tools hook. My problem is that there is a difference in the firmware dependencies of the module between the standard 5.4 kernel and the current HWE 5.15 kernel: in 5.4, the module depends on /lib/firmware/rtlwifi/rtl8188eufw.bin, while in 5.15 it no longer does so. You can verify it using `modinfo -F firmware r8188eu` (perhaps with the `-k` parameter if you do not want to check the currently run kernel). The card requires the mentioned firmware file. In order to use it with both kernels, in addition to `manual_add_modules r8188eu`, I have to put something like `copy_file firmware /lib/firmware/rtlwifi/rtl8188eufw.bin` in my initramfs-tools hook. The bug is fixed (https://lore.kernel.org/lkml/YulcdKfhA8dPQ78s@nx64de- df6d00/) in Linux 5.15.66 (https://lwn.net/Articles/907524/). Please consider backporting the fix or updating the HWE kernel package to 5.15.66. ** Affects: linux-meta-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1989162 Title: The r8188eu kernel module does not depend on the rtlwifi/rtl8188eufw.bin firmware file in the 20.04 HWE kernel Status in linux-meta-hwe-5.15 package in Ubuntu: New Bug description: I would like to use a Wi-Fi card supported by the r8188eu kernel module in the initramfs, in Ubuntu 20.04. I add the module using a custom initramfs-tools hook. My problem is that there is a difference in the firmware dependencies of the module between the standard 5.4 kernel and the current HWE 5.15 kernel: in 5.4, the module depends on /lib/firmware/rtlwifi/rtl8188eufw.bin, while in 5.15 it no longer does so. You can verify it using `modinfo -F firmware r8188eu` (perhaps with the `-k` parameter if you do not want to check the currently run kernel). The card requires the mentioned firmware file. In order to use it with both kernels, in addition to `manual_add_modules r8188eu`, I have to put something like `copy_file firmware /lib/firmware/rtlwifi/rtl8188eufw.bin` in my initramfs-tools hook. The bug is fixed (https://lore.kernel.org/lkml/YulcdKfhA8dPQ78s@nx64de-df6d00/) in Linux 5.15.66 (https://lwn.net/Articles/907524/). Please consider backporting the fix or updating the HWE kernel package to 5.15.66. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-hwe-5.15/+bug/1989162/+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 1987711] 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Confirmed Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+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 1987711] Re: [i915] Ubuntu display get shifted after some time.
Can you try different computers on the same monitor? Just in case it is the monitor. ** 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Confirmed Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1799679] Re: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows
** 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 nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1799679 Title: Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows Status in Mutter: Unknown Status in metacity package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-410 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-418 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Bug description: Nvidia driver causes Xorg to use 100% CPU and shows high lag and stutter... but only when dragging glxgears/glxheads, or any window over them. Other apps do not exhibit the problem. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nvidia-driver-390 390.87-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12 Uname: Linux 4.18.0-10-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 Date: Wed Oct 24 19:11:15 2018 InstallationDate: Installed on 2018-05-26 (151 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-graphics-drivers-390 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1799679/+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 1989102] Re: Dragging windows is very slow and choppy
*** This bug is a duplicate of bug 1799679 *** https://bugs.launchpad.net/bugs/1799679 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1799679, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-470 (Ubuntu) ** This bug has been marked a duplicate of bug 1799679 Nvidia driver causes Xorg to use 100% CPU and huge lag when dragging OpenGL app windows -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1989102 Title: Dragging windows is very slow and choppy Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: 1. UBUNTU VERSION Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy 2. PACKAGE VERSION gdm3: Installed: 42.0-1ubuntu7 Candidate: 42.0-1ubuntu7 Version table: *** 42.0-1ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. WHAT I EXPECTED TO HAPPEN When dragging a window, the window follows the mouse cursor smoothly. 4. WHAT ACTUALLY HAPPENS Dragging windows is extremely slow and choppy. You grab a window and start to drag it. For a very brief moment, around .5s, the window moves smoothly. Then it stops being re-drawn for around 3s. Then there's another brief .5s of smoothness, and the cycle repeats. This occurs with all windows. 5. ADDITIONAL INFORMATION - I was previously on Ubuntu 18.04 and have just upgraded to 22.04. - I am using the nVidia proprietary driver: NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 - I have three monitors. Two standard 60Hz monitors, and one Gigabyte G27Q Freesync compatible 144Hz monitor (I have tried all refresh settings for the monitor, and it makes no difference). - I am running X and do not have the option on login to switch to Wayland (no cog shown). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:41:49 2022 InstallationDate: Installed on 2021-01-05 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-05 (33 days ago) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2022-09-08T10:42:52.395463 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1989102/+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 1989102] [NEW] Dragging windows is very slow and choppy
You have been subscribed to a public bug: 1. UBUNTU VERSION Distributor ID: Ubuntu Description:Ubuntu 22.04.1 LTS Release:22.04 Codename: jammy 2. PACKAGE VERSION gdm3: Installed: 42.0-1ubuntu7 Candidate: 42.0-1ubuntu7 Version table: *** 42.0-1ubuntu7 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-1ubuntu6 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages 3. WHAT I EXPECTED TO HAPPEN When dragging a window, the window follows the mouse cursor smoothly. 4. WHAT ACTUALLY HAPPENS Dragging windows is extremely slow and choppy. You grab a window and start to drag it. For a very brief moment, around .5s, the window moves smoothly. Then it stops being re-drawn for around 3s. Then there's another brief .5s of smoothness, and the cycle repeats. This occurs with all windows. 5. ADDITIONAL INFORMATION - I was previously on Ubuntu 18.04 and have just upgraded to 22.04. - I am using the nVidia proprietary driver: NVIDIA-SMI 470.141.03 Driver Version: 470.141.03 CUDA Version: 11.4 - I have three monitors. Two standard 60Hz monitors, and one Gigabyte G27Q Freesync compatible 144Hz monitor (I have tried all refresh settings for the monitor, and it makes no difference). - I am running X and do not have the option on login to switch to Wayland (no cog shown). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46 Uname: Linux 5.15.0-47-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:41:49 2022 InstallationDate: Installed on 2021-01-05 (610 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) SourcePackage: gdm3 UpgradeStatus: Upgraded to jammy on 2022-08-05 (33 days ago) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2022-09-08T10:42:52.395463 ** Affects: nvidia-graphics-drivers-470 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- Dragging windows is very slow and choppy https://bugs.launchpad.net/bugs/1989102 You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 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 1639924] Re: Kernel livepatch support for for s390x
Config and Packaging of kinetic:linux-unstable and kinetic:linux are incomplete. ** Changed in: linux (Ubuntu Kinetic) Status: Fix Committed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Triaged Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: New Status in linux package in Ubuntu: In Progress Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: New Status in linux source package in Jammy: New Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: New Status in linux source package in Kinetic: In Progress Bug description: Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). But the kpatch-build tool does only support amd64 as of today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+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 1987711] Re: [i915] Ubuntu display get shifted after some time.
Well, looks like bug occured again. In drm-tip, and also it occured in version v5.19.5 I realized, that I have also computer with se same(i believe) graphic card, and i do not remember for problem to occur on this pc even once. so I looked for difference in these two computers. I tried these commands to find difference: glxinfo -B lscpu lshw And (from my point of view) interesting difference is: glxinfo: Pc where error does not occures: Version: 22.0.1 Video memory: 3072MB pc where error occures: Version: 22.0.5 Video memory: 15928MB (note, that pc where error does not occures has 8GB ram, and the one where error occures has total 16GB ram.) ie, probably video memory can consume entire ram? But I did not remember setting that, so these have to be default settings, or do not know.) lshw: pc ok: lshw product: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.78.3 size: 2800MHz width: 64 bits pc nok: lshw product: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz vendor: Intel Corp. physical id: 1 bus info: cpu@0 version: 6.78.3 size: 2700MHz capacity: 2800MHz width: 64 bits there is different "size" value, and pc that does not shows screen shifting misses "capacity". lscpu differs in these two rows: pc ok: lscpu Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; IBRS, IBPB conditional, RSB filling pc nok: lscpu Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl Vulnerability Spectre v1:Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2:Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected Main difference is in seccomp, and PBRSB-eIRBS Not affected... have no idea if it is something interesting. anyway, full list of response commands is in attachment. I may try to downgrade from version 22.0.5 to 22.0.1 but i am not sure what exactly to downgrade. ** Attachment added: "bugrep8.9.zip" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+attachment/5614739/+files/bugrep8.9.zip -- 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic
[Kernel-packages] [Bug 1639924] Re: Kernel livepatch support for for s390x
The PR is attached here. Notice the build (in PPA) succeeds either with having: 0014-Set-y-as-default-for-new-CONFIG_EXPOLINE_EXTERN-kern.patch NOT included, or with having zfs DKMS disabled (either having the entire zfs related line removed from debian/dkms-versions or just the "arch=s390x" parameter). Otherwise the build seems to fails for me with an zfs issue. ** Patch added: "-pull.patch" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+attachment/5614736/+files/-pull.patch -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Triaged Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: New Status in linux source package in Jammy: New Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: New Status in linux source package in Kinetic: Fix Committed Bug description: Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). But the kpatch-build tool does only support amd64 as of today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+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 1639924] Re: Kernel livepatch support for for s390x
The minimal patch set for the jammy master-next kernel I've used is: 3d79d0079cae sched: Improve try_invoke_on_locked_down_task() 914f948c313a sched,rcu: Rework try_invoke_on_locked_down_task() 702fa42757b0 sched,livepatch: Use task_call_func() 5516e7085fca sched: Simplify wake_up_*idle*() 86db6bfb3dc8 sched,livepatch: Use wake_up_if_idle() 6fe095210f38 sched: Improve wake_up_all_idle_cpus() take #2 4168d69c57d1 s390/entry: remove unused expoline thunk a73c3438e6f2 s390: remove unused expoline to BC instructions 1e3807c786b1 s390/nospec: generate single register thunks if possible [ 0378d08bd3c3 s390/nospec: add an option to use thunk-extern ] ==> 0010-s390-nospec-add-an-option-to-use-thunk-extern.patch a7f928d3ef3a s390/nospec: align and size extern thunks 298b3cbf7d0e bug: Use normal relative pointers in 'struct bug_entry' [ 0013 - 816b355fa9ed s390/nospec: build expoline.o for modules_prepare target ] ==> 0013-s390-nospec-build-expoline.o-for-modules_prepare-tar.patch ==> 0014-Set-y-as-default-for-new-CONFIG_EXPOLINE_EXTERN-kern.patch The two backports and the kernel option patch are attached. ** Attachment added: "lp1639924_patches.tgz" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+attachment/5614735/+files/lp1639924_patches.tgz -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Triaged Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: New Status in linux source package in Jammy: New Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: New Status in linux source package in Kinetic: Fix Committed Bug description: Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). But the kpatch-build tool does only support amd64 as of today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+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 1639924] Re: Kernel livepatch support for for s390x
** Summary changed: - kernel livepatch not available for s390x + Kernel livepatch support for for s390x -- 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/1639924 Title: Kernel livepatch support for for s390x Status in Ubuntu on IBM z Systems: Triaged Status in gcc-11 package in Ubuntu: Fix Released Status in kpatch package in Ubuntu: New Status in linux package in Ubuntu: Fix Committed Status in gcc-11 source package in Jammy: Fix Released Status in kpatch source package in Jammy: New Status in linux source package in Jammy: New Status in gcc-11 source package in Kinetic: Fix Released Status in kpatch source package in Kinetic: New Status in linux source package in Kinetic: Fix Committed Bug description: Kernel live-patch is afaik fully upstream and available for 'all' platforms (incl. s390x). But the kpatch-build tool does only support amd64 as of today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1639924/+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 1989144] [NEW] unprivileged users may trigger page cache invalidation WARN
Public bug reported: [Impact] Unprivileged users may trigger a page cache invalidation failure when doing parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN. [ 22.415082] WARNING: CPU: 3 PID: 3404 at /build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460 [ 22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd psmouse ahci libahci virtio_blk virtio_net [ 22.415099] CPU: 3 PID: 3404 Comm: xfs_io Not tainted 4.15.0-192-generic #203-Ubuntu [ 22.415100] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.15.0-1 04/01/2014 [ 22.415103] RIP: 0010:iomap_dio_actor+0xbd/0x460 [ 22.415104] RSP: 0018:b7c782fe7bf0 EFLAGS: 00010202 [ 22.415104] RAX: 0002 RBX: RCX: 0009 [ 22.415105] RDX: 01ff RSI: RDI: b7c782fe7e20 [ 22.415105] RBP: b7c782fe7c68 R08: b7c782fe7c88 R09: 9bbc9f48fba0 [ 22.415106] R10: 0001 R11: R12: 0009 [ 22.415106] R13: 9bbc9f48fba0 R14: b7c782fe7c88 R15: 1000 [ 22.415107] FS: 7f2b802ed700() GS:9bbcbfd8() knlGS: [ 22.415107] CS: 0010 DS: ES: CR0: 80050033 [ 22.415108] CR2: 01639000 CR3: 1e6b0003 CR4: 00760ee0 [ 22.415110] PKRU: 5554 [ 22.415110] Call Trace: [ 22.415122] ? iomap_dio_zero+0x130/0x130 [ 22.415123] iomap_apply+0xa5/0x120 [ 22.415124] ? iomap_dio_zero+0x130/0x130 [ 22.415125] iomap_dio_rw+0x2f3/0x430 [ 22.415126] ? iomap_dio_zero+0x130/0x130 [ 22.415148] xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415157] ? xfs_file_dio_aio_read+0x68/0xf0 [xfs] [ 22.415165] xfs_file_read_iter+0xbf/0xe0 [xfs] [ 22.415170] new_sync_read+0xe4/0x130 [ 22.415171] __vfs_read+0x29/0x40 [ 22.415172] vfs_read+0x8e/0x130 [ 22.415173] SyS_pread64+0x95/0xb0 [ 22.415176] do_syscall_64+0x73/0x130 [ 22.415183] entry_SYSCALL_64_after_hwframe+0x41/0xa6 [ 22.415184] RIP: 0033:0x7f2b7fbc0b73 [ 22.415185] RSP: 002b:7ffc134e1a58 EFLAGS: 0246 ORIG_RAX: 0011 [ 22.415186] RAX: ffda RBX: RCX: 7f2b7fbc0b73 [ 22.415186] RDX: 1000 RSI: 01639000 RDI: 0003 [ 22.415186] RBP: R08: R09: [ 22.415187] R10: R11: 0246 R12: 7ffc134e1b00 [ 22.415187] R13: 0002 R14: R15: [ 22.415188] Code: 21 d0 48 89 45 a0 0f 85 aa 03 00 00 41 0f b7 46 18 66 83 f8 03 0f 84 7e 02 00 00 66 83 f8 04 74 52 66 83 f8 01 0f 84 c8 02 00 00 <0f> 0b 48 c7 45 a0 fb ff ff ff 48 8b 5d d0 65 48 33 1c 25 28 00 [Test case] Run xfstests generic/446 test. [Potential regressions] Data corruption could be caused, though it is expected to be caused in such scenarions anyway. That should affecte direct I/O. ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Bionic) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: In Progress ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1989144 Title: unprivileged users may trigger page cache invalidation WARN Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [Impact] Unprivileged users may trigger a page cache invalidation failure when doing parallel direct I/O and buffered I/O. On some kernels, that may lead to a WARN. [ 22.415082] WARNING: CPU: 3 PID: 3404 at /build/linux-GtMq7R/linux-4.15.0/fs/iomap.c:903 iomap_dio_actor+0xbd/0x460 [ 22.415083] Modules linked in: xfs isofs kvm_intel kvm irqbypass joydev input_leds serio_raw ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear
[Kernel-packages] [Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround
I just upgraded to Ubuntu 22.04 and I'm still affected by this bug. I tried with the latest kernel (5.15.0-47) and it won't boot without intremap=off Thanks! -- 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/1808418 Title: Thinkpad T430u won't boot without noapic workaround Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: (For anyone coming to this bug for the first time, the current workaround is to add this to the kernel boot parameters: intremap=off) I've used Ubuntu on this specific machine for years without problems, but starting with the 4.13 kernel that came with the 17.10 HWE and continuing into 18.04 kernels my computer would no longer boot, hanging at various screens: - A blank screen with a flashing cursor - A screen with this message: Loading Linux 4.13.0.36-generic ... Loading initial ramdisk ... - A screen with kernel messages, ending in: APCI: EC: interrupt blocked I've encountered the bug in a number of kernels, including: - 4.13.0-32 - 4.13.0-36 - 4.13.0-37 - 4.15.0-24 - 4.15.0-34 - 4.15.0-36 - 4.15.0-38 - 4.15.0-42 - 4.20.0-rc7 I was able to work around the issue by adding noapic to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic" I'm not entirely sure of the consequences of this workaround, but one thing I've noticed is significantly reduced battery life. This bug seems very similar to what's described here for the Thinkpad E485/E585: https://evilazrael.de/node/401 I'll attach screenshots of various times I've encountered this bug over the last year. $ lsb_release -rd Description:Ubuntu 18.04.1 LTS Release:18.04 $ apt-cache policy linux-image-4.15.0-42-generic linux-image-4.15.0-42-generic: Installed: 4.15.0-42.45 Candidate: 4.15.0-42.45 Version table: *** 4.15.0-42.45 500 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-42-generic 4.15.0-42.45 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bryan 2349 F pulseaudio CurrentDesktop: XFCE Date: Thu Dec 13 15:31:15 2018 HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac InstallationDate: Installed on 2014-05-08 (1680 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 3351CTO ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago) dmi.bios.date: 06/01/2018 dmi.bios.vendor: LENOVO dmi.bios.version: H6ETA0WW (2.18 ) dmi.board.asset.tag: Not Available dmi.board.name: 3351CTO dmi.board.vendor: LENOVO dmi.board.version: Win8 STD DPK TPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T430u dmi.product.name: 3351CTO dmi.product.version: ThinkPad T430u dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808418/+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 1989047] Re: ADL: Fix System hang up when run Prime95 with i9-12900K CPU
@Timo, i was just looking for more suggestions and provide this to Lucasz. this's not a SRU and just for record. didn't mention this would be got automatically by Foundation. -- 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/1989047 Title: ADL: Fix System hang up when run Prime95 with i9-12900K CPU Status in thermald package in Ubuntu: New Bug description: [Impact] * System hang up when run Prime95 10~15 minutes [Test Plan] 1. Find a unit with i9-12900k CPU and liquid cooling 2. Connect to Internet and install below tools >sudo apt update >sudo apt install stress-ng >sudo apt install s-tui >sudo systemctl stop thermald >sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) >./mprime #decompressed from p95*.tar.gz >sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. >sudo s-tui -c [Where problems could occur] * it install Passive Policy as default and use PL1 max/min from PPCC, there may be some edge cases that don't handle well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989047/+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 1982479] Re: [Medion Akoya E3223] Latest kernel breaks LCD screen
Interesting effect: When the distortion is shown and I do plugin a second screen, then both screens are working well. Obviously, some sort of reconfiguration happens. -- 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/1982479 Title: [Medion Akoya E3223] Latest kernel breaks LCD screen Status in linux package in Ubuntu: Confirmed Bug description: Hi, I just installed Lubuntu 22.04 on a brandnew notebook, and everything was working well until rebooting after update: Both the boot splash and the X11 screens are jumping and appear instable afer a few seconds, as out of sync and running through. It absolutely looks like a hardware problem like a broken LCD connector cable, but it isn't: booting fresh from the Lubuntu usb stick and evernything works. I have a second machine, exactly same model and installation procedure, which was working well for some weeks and had exactly the same problem after upgrading. disabling the boot splash did not help. But booting into the older vmlinuz-5.15.0-25-generic , that came with the Lubuntu installation iso file, instead of the latest vmlinuz-5.15.0-41-generic solved the problem. With the older kernel, everything is stable and fine. So between the 25 and the 41 revision of the kernel there came something in which reliably breaks the screen configuration on both my two notebooks of identical hardware. Both the X11 login screen and the desktop do work normally for about five seconds and then start running through like one of these old days analog screens when out of sync or a cable not plugged in correctly. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-41-generic 5.15.0-41.44 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hadmut 1857 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Thu Jul 21 12:28:31 2022 InstallationDate: Installed on 2022-07-20 (0 days ago) InstallationMedia: Lubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Lsusb: Bus 002 Device 002: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 002: ID 0c45:6321 Microdia HP Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MEDION E3223 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=ab20c954-2973-48a4-a73c-491b5bdeddc2 ro quiet cryptdevice=UUID=abc35d02-7e06-4152-b214-01f17a4740bb:luks-abc35d02-7e06-4152-b214-01f17a4740bb root=/dev/mapper/luks-abc35d02-7e06-4152-b214-01f17a4740bb nosplash RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/13/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GeminiLake_YS13GR_V3.0.2 dmi.board.asset.tag: Default string dmi.board.name: YS13GR dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 31 dmi.chassis.vendor: MEDION dmi.chassis.version: GD7387P dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGeminiLake_YS13GR_V3.0.2:bd09/13/2021:br5.13:svnMEDION:pnE3223:pvrELAN:rvnMEDION:rnYS13GR:rvrDefaultstring:cvnMEDION:ct31:cvrGD7387P:skuML-24100630032549: dmi.product.family: Akoya dmi.product.name: E3223 dmi.product.sku: ML-241006 30032549 dmi.product.version: ELAN dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1982479/+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 1988721] Re: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD
kinetic has 5.19 ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1988721 Title: [SRU][OEM-5.17][PATCH 0/1] Fix output issue of USB-C to DP dongle on AMD Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Bug description: [Impact] There is no output of external 4k DP monitor via USB-C to DP dongle. [Fix] Isolate link training sequence, the external DP monitor will be good. [Test] Verified on hardware, external 4k monitor works fine after re-plugin and suspend. [Where problems could occur] It may break the display output on AMD GPU. This commit is from 5.18-rc1, and no issue on jammy kernel. SRU for oem-5.17 only. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1988721/+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 1989047] Re: ADL: Fix System hang up when run Prime95 with i9-12900K CPU
that's not how you sru a new upstream version.. didn't we discuss this already? -- 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/1989047 Title: ADL: Fix System hang up when run Prime95 with i9-12900K CPU Status in thermald package in Ubuntu: New Bug description: [Impact] * System hang up when run Prime95 10~15 minutes [Test Plan] 1. Find a unit with i9-12900k CPU and liquid cooling 2. Connect to Internet and install below tools >sudo apt update >sudo apt install stress-ng >sudo apt install s-tui >sudo systemctl stop thermald >sudo thermald --no-daemon --loglevel=debug --adaptive --ignore-cpuid-check > thermald_log.txt & download prime95 linux version: p95v308b15.linux64.tar.gz and decompress 4. Stress test: (you may need to open multiple terminals for the test) >./mprime #decompressed from p95*.tar.gz >sudo stress-ng -a 0 --class cpu,cpu-cache --ignite-cpu -v 5. monitor cpu temperature for 6 hours if you didn’t hit overheat and shutdown issue. >sudo s-tui -c [Where problems could occur] * it install Passive Policy as default and use PL1 max/min from PPCC, there may be some edge cases that don't handle well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1989047/+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 1987312] Re: IWLMEI may cause device down at resuming from s2idle
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987312 Title: IWLMEI may cause device down at resuming from s2idle Status in HWE Next: New Status in OEM Priority Project: New Status in backport-iwlwifi-dkms package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in backport-iwlwifi-dkms source package in Jammy: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux-oem-6.0 source package in Jammy: Fix Committed Status in backport-iwlwifi-dkms source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justification] [Impact] WiFi interfaces unsolicitedly down at resuming from s2idle. [Fix] Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. [Test Case] Make sure iwlmei.ko is not built. [Where problems could occur] iwlmei was not enabled before 5.17 and was turned on automatically since then. This restores the state and shall not have impact on existing devices. == original bug report == Intel confirmed there is no CSME for WLAN POR for Linux. CSME for WLAN POR is only for Windows project design. Please remove or disable CONFIG_IWLMEI from Linux. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987312/+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 1983297] Re: Additional fix for TGL + AUO panel flickering
** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1983297] Re: Additional fix for TGL + AUO panel flickering
** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1983297 Title: Additional fix for TGL + AUO panel flickering Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel" alone used to fix the issue on the AUO panel. But the panel starts to flicker like crazy on top of the new stable commits. [Fix] Backport full fix for PSR2 selective fetch, but only enable it on TGL + specific AUO panel. The last three patches which enable PSR2 on ADL-P are dropped. [Test] Originally the backport regressed ADL + BOE panel, so this time we put extra effort to ensure those system are unaffected, while TGL + AUO panel is still fixed. [Where problems could occur] Most code changes only have functional impact when PSR2 selective fetch is enabled. Some of changes are under more general call path for hardware cursor rendering. Notes are added to describe the functional impact for each patch, so if regression really occurrs it's easier to spot the offending commit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1983297/+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 1980307] Re: Suppress harmless warning from hp-wmi
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1980307 Title: Suppress harmless warning from hp-wmi Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [Impact] Harmless warning is spewed from hp-wmi driver. [Fix] Ignore the unhandled event. [Test] No more such warning in dmesg. [Where problems could occur] The action for the event is not implemented, so ignoring it won't change any existing behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1980307/+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 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
CONFIG_PWM_SIFIVE=m could be a workaround. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1988984 Title: earlyconsole prints on 5.19.0-1002-generic Status in linux-meta-riscv package in Ubuntu: New Bug description: With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole output looks like: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... ��� With a defconfig 5.19.6 kernel this does not occr. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+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 1988984] Re: earlyconsole prints ������������������������ on 5.19.0-1002-generic
Bisecting the kernel configuration file points to CONFIG_PWM_SIFIVE=y causing the problem. The setting was already enabled in out v5.15 kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1988984 Title: earlyconsole prints on 5.19.0-1002-generic Status in linux-meta-riscv package in Ubuntu: New Bug description: With Kernel 5.19.0-1002-generic on the SiFive Unmatched earlyconsole output looks like: EFI stub: Booting Linux Kernel... EFI stub: Using DTB from configuration table EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path EFI stub: Exiting boot services... ��� With a defconfig 5.19.6 kernel this does not occr. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-riscv/+bug/1988984/+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 1988836] Re: Enable the open NVIDIA kernel modules
** Also affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Changed in: ubuntu-drivers-common (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: New => In Progress ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in ubuntu-drivers-common source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Jammy: In Progress Bug description: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1988836] Re: Enable the open NVIDIA kernel modules
** Also affects: nvidia-graphics-drivers-515 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-515 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Status: New => In Progress ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Focal) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-515 (Ubuntu Jammy) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-515 (Ubuntu) Status: In Progress => Fix Released ** Also affects: linux-restricted-modules (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-restricted-modules (Ubuntu) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-restricted-modules (Ubuntu) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-restricted-modules (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-restricted-modules (Ubuntu Focal) Assignee: (unassigned) => Andy Whitcroft (apw) ** Changed in: linux-restricted-modules (Ubuntu Jammy) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: In Progress Status in nvidia-graphics-drivers-515 source package in Focal: In Progress Status in linux-restricted-modules source package in Jammy: In Progress Status in nvidia-graphics-drivers-515 source package in Jammy: In Progress Bug description: The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu- kernel-modules/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+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 1980602] Re: grub failures 22.10
** Tags added: kinetic ** 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/1980602 Title: grub failures 22.10 Status in linux package in Ubuntu: Incomplete Bug description: On initial power -up , each morning , grub fails to complete. It reports problems with accessing / processing /dev/sde13 when the actual OS being used , according to grub . is /dev/sde14 . It will load / process when second attempt is made on same /dev/sde14 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980602/+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 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
sponsored into bionic-proposed unapproved queue ** Changed in: lttng-modules (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in lttng-modules source package in Bionic: In Progress Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Released Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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 1983468] Re: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status)
Firmware version 218.0.152.0 is mentioned in this HPE advisory regarding packet drop: https://support.hpe.com/hpesc/public/docDisplay?docId=a00120518en_us=en_US -- 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/1983468 Title: tx checksumming offload results in TCP/UDP packet drops (was Octavia amphora loadbalancer gets stuck at PENDING_CREATE status) Status in OpenStack Octavia Charm: Invalid Status in linux package in Ubuntu: Confirmed Bug description: In a new focal-yoga deployment, the creation of a loadbalancer gets stuck at PENDING_CREATE status. Checking the amphora we could see that it stays at BOOTING status: $ openstack loadbalancer amphora show ef48089d-ba40-46db-92e8-e369f764f017 --format yaml id: ef48089d-ba40-46db-92e8-e369f764f017 loadbalancer_id: dcd17d9e-6a27-43c5-9c3f-eb2b266d compute_id: 5efe11a8-93d8-4278-94c2-4efc8b015009 lb_network_ip: fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa vrrp_ip: null ha_ip: null vrrp_port_id: null ha_port_id: null cert_expiration: '2022-09-01T20:27:05' cert_busy: false role: null status: BOOTING vrrp_interface: null vrrp_id: null vrrp_priority: null cached_zone: nova created_at: '2022-08-02T20:27:05' updated_at: '2022-08-02T20:30:13' image_id: 6c6cd911-197f-45d3-a6d5-4ff1789d4ee7 compute_flavor: 638fa4c5-e81b-438f-a12b-1ef7faf81c3e /var/log/octavia/octavia-worker.log shows several warnings about connection failure to the amphora. 2022-08-02 20:30:22.589 149659 WARNING octavia.amphorae.drivers.haproxy.rest_api_driver [-] Could not connect to instance. Retrying.: requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa', port=9443): Max retries exceeded with url: // (Caused by ConnectTimeoutError(, 'Connection to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa timed out. (connect timeout=10.0)')) It is possible to ping the amphora from an octavia unit: # ping -M do -s 1452 fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa PING fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa(fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa) 1452 data bytes 1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=1 ttl=64 time=2.45 ms 1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=2 ttl=64 time=1.01 ms 1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=3 ttl=64 time=0.532 ms 1460 bytes from fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa: icmp_seq=4 ttl=64 time=0.417 ms Also, the port tcp/22 is reacheable from the octavia unit: # telnet fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa 22 Trying fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa... Connected to fc00:b81a:629a:59a6:f816:3eff:fe0a:68fa. Escape character is '^]'. SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.5 After running the config-changed hook as described at the bug https://bugs.launchpad.net/charm-octavia/+bug/1961088 , the creation of a loadbalancer ends with a ERROR provisioning_status. To manage notifications about this bug go to: https://bugs.launchpad.net/charm-octavia/+bug/1983468/+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 1980602] 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 1980602 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/1980602 Title: grub failures 22.10 Status in linux package in Ubuntu: Incomplete Bug description: On initial power -up , each morning , grub fails to complete. It reports problems with accessing / processing /dev/sde13 when the actual OS being used , according to grub . is /dev/sde14 . It will load / process when second attempt is made on same /dev/sde14 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1980602/+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 1980602] [NEW] grub failures 22.10
You have been subscribed to a public bug: On initial power -up , each morning , grub fails to complete. It reports problems with accessing / processing /dev/sde13 when the actual OS being used , according to grub . is /dev/sde14 . It will load / process when second attempt is made on same /dev/sde14 . ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: kinetic -- grub failures 22.10 https://bugs.launchpad.net/bugs/1980602 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 1986921] Re: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51
Fix for the 5.4 kernel in bionic reported in attach. ** Patch added: "lttng-support-kernel-5.4-without-random-tracepoints.debdiff" https://bugs.launchpad.net/ubuntu/+source/lttng-modules/+bug/1986921/+attachment/5614597/+files/lttng-support-kernel-5.4-without-random-tracepoints.debdiff -- 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/1986921 Title: lttng-modules/2.13.1-1 ADT test failure with linux/5.15.0-47.51 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Won't Fix Status in lttng-modules package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in lttng-modules source package in Bionic: Confirmed Status in linux source package in Focal: Won't Fix Status in lttng-modules source package in Focal: Fix Released Status in linux source package in Jammy: Won't Fix Status in lttng-modules source package in Jammy: Fix Released Bug description: SRU Justification: Impact: The kernel upstream changed in v5.18 and dropped tracepoints for random. This change was backported to 5.15/jammy in upstream stable 5.15.44. With that the build of lttng-modules-dkms fails. Fix: Backport of an upstream change which checks for the kernel header file which got removed in the process. Additionally the DKMS spec file has to do the same check to be aware of the missing probe module. Testcase: Installing lttng-modules-dkms for a kernel < 5.15.0-47 and -47 or later. Currently -47 and later will fail. With the change both should complete. Regression Potential: This changes whether lttng-probe-random.ko is available or not (if it is available the code is unchanged). User- space might be affected if this module is always expected. --- This is a scripted bug report about ADT failures while running lttng- modules tests for linux/5.15.0-47.51 on jammy. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/lttng-modules/20220817_074711_55044@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/l/lttng-modules/20220817_075639_1a4d1@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/l/lttng-modules/20220817_074544_d2849@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/l/lttng-modules/20220817_075106_d2849@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1986921/+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 1989054] 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/1989054 Title: Brightness bar not working properly on HP EliteBook 8460p Status in linux package in Ubuntu: Confirmed Bug description: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989054/+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 1989054] Re: Brightness bar not working properly on HP EliteBook 8460p
** Summary changed: - Brightness bar not working properly + Brightness bar not working properly on HP EliteBook 8460p ** Package changed: xorg (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/1989054 Title: Brightness bar not working properly on HP EliteBook 8460p Status in linux package in Ubuntu: New Bug description: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989054/+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 1989054] [NEW] Brightness bar not working properly on HP EliteBook 8460p
You have been subscribed to a public bug: My brightness doesn't change and stays at lowest brightness level till about 70% of the slider, after that the brightness starts increasing ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Sep 8 10:47:44 2022 DistUpgraded: Fresh install DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family Integrated Graphics Controller [103c:161c] MachineType: Hewlett-Packard HP EliteBook 8460p ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=f97ede9e-1a56-449e-81ae-d3b99491cdef ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/26/2011 dmi.bios.release: 15.8 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCF Ver. F.08 dmi.board.name: 161C dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.asset.tag: CNU147038F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.ec.firmware.release: 151.69 dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:br15.8:efr151.69:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001C02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:skuSN119UC#ABA: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 8460p dmi.product.sku: SN119UC#ABA dmi.product.version: A0001C02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy ubuntu -- Brightness bar not working properly on HP EliteBook 8460p https://bugs.launchpad.net/bugs/1989054 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 1962674] Re: Add IIO sensors ID for ACPI based platform
** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg in Ubuntu. https://bugs.launchpad.net/bugs/1962674 Title: Add IIO sensors ID for ACPI based platform Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-iotg package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: Fix Released Status in linux-intel-iotg source package in Focal: Invalid Status in linux-intel-5.13 source package in Jammy: Invalid Status in linux-intel-iotg source package in Jammy: Fix Released Status in linux-intel-5.13 source package in Kinetic: Invalid Status in linux-intel-iotg source package in Kinetic: New Bug description: [Impact] On ACPI based platforms, some sensors aren't probed because driver doesn't have ACPI IDs, so they are useless. [Fix] For pressure sensor: 72ff282819d0526d3e4417c2a61414557981b5af iio: pressure: dps310: Add ACPI HID table For humidity sensor: 711b6a3f4af137c4a7f759136ccd50d455095b95 iio: humidity: hdc100x: Add ACPI HID table For accelerator sensor: b9493d595226b598ed79b3769f7038fda1a5391b iio: accel: adxl345: Add ACPI HID table The commit is part of patch series, for the whole series, please cherry-pick 01676b0f3b625a9aa608d5b716898e9dba2fb63e^..4781f3e0e6cadf332f49f723ba820f35960a058d [Test] All sensors are working under /sys/bus/iio. [Where problems could occur] Unless there's an ID collision, these patches don't really bring any change, hence no regression risk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1962674/+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 1986520] Re: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS
Hey, the error message inside libvirt is from parsing PCI VPD Data. If you say removing that card removes the message it seems to indicate that the VPD of that device is either a) broken as coming from the device and needs a FW Update (or report to Intel to create one) or b) valid VPD data but uncommon and breaking the parser in libvirt #1. libvirt You could gather some info and then decide if it is more (a) or (b) to then report it directly to intel or to upstream libvirt [1] to have a look. I think to check what libvirt can (or can not read) you could run $ virsh nodedev-list # now select the i350 OCP $ virsh nodedev-dumpxml That should cause libvirt to try to read and report you the VPD data of the device. I'd expect this triggers the issue, maybe you find anything odd in there already ... 1b. debug If 1 recerates the issue you might want to run the same with livbirt debug info enabled [3] and report that here and/or upstream depending what you see. #2. kernel This is rather kernel dependent, it might be worth trying a few older/newer mainline kernels [2] to see if any might already behave different #3. data It might be great to report the actual VPD data exposed. That would be $ sudo cat /sys/devices/pci...///vpd Until we (or intel or upstreams) have that data there is not much we can do, hence setting the bug to incomplete for now. [1]: https://gitlab.com/libvirt/libvirt/-/issues [2]: https://kernel.ubuntu.com/~kernel-ppa/mainline/ [3]: https://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Debug.html ** Changed in: libvirt (Ubuntu) Status: Confirmed => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1986520 Title: There are libvirtd errors in /var/log/syslog when powering on or off virtual machine in Ubuntu 22.04 LTS Status in libvirt package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hardware Configuration: Server MTM: Bona POR SE450 OS installed: Ubuntu 22.04 LTS (ubuntu-22.04-live-server-amd64.iso) BMC Version: 1.40 (Build ID: USX311E) UEFI Version: 1.03 (Build ID: CME105C) LXPM Version: 3.19 (Build ID: CML103A) CPU: Xeon Silver 4314 16C 135W 2.4GHz DIMM2,4,7,9: Hynix 32GB 2Rx4 3200 MHz RDIMM HMA84GR7CJR4N-XNTG; HMA84GR7CJR4N-XNT4 DIMM1,3,8,10: Intel Optane DCPMM_128GB QVR2 IO Config: RAID: Intel VROC (VMD NVMe RAID) Premium SLOT5: NIC: ThinkSystem Mellanox ConnectX-6 Dx 100GbE QSFP56 2-port PCIe 4 Ethernet Adapter SLOT7: NIC: Intel I350 1GbE RJ45 4-port Internal Lock OCP Ethernet Adapter Storage: DISK1: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD DISK2: ThinkSystem 2.5” 7mm U.3 7400P 1.92TB Read Intensive NVMe PCIe 4.0 x4 Trayless SSD PSU1: CFFv4 AC 1100W (Delta) 110V PSU2: CFFv4 AC 1100W (Delta) 110V M/B build version: PASS5 MB Steps: 1. Power on SUT and install Ubuntu 22.04 LTS on VROC NVMe RAID 0 disk. 2. Install KVM features and desktop GUI. 3. Run "apt upgrade" to update packages. 4. Create a namespace on BPS DIMM App Direct Not Interleaved mode. 5. Run "virt-manager" then install Windows Server 2022 on the namespace. 6. Reboot Guest OS and Host OS to check if there is any unexpected error in system logs. (=> failed, there are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] ) Expected behaviors: There are no any unexpected errors in system logs. Current behaviors: There are libvirtd errors in /var/log/syslog when booting into OS or powering on/off the virtual machine: libvirtd: internal error: A field data length violates the resource length boundary. libvirtd: message repeated 3 times: [internal error: A field data length violates the resource length boundary.] --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-18 (0 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220816) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0624:0407 Avocent Corp. IBM 39M2894 Bus 001 Device 004: ID 17ef:b000 Lenovo Virtual Keyboard and Mouse Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root
