[Kernel-packages] [Bug 1930813] Re: touchpad not recognised after upgrade 21.04
Any update ? -- 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/1930813 Title: touchpad not recognised after upgrade 21.04 Status in linux package in Ubuntu: New Bug description: Touchpad doesn't work anymore after upgrading to 21.04 on a notebook asus zenbook UX306. Worked perfectly before upgrade ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thilu 11394 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Jun 4 09:15:12 2021 InstallationDate: Installed on 2020-04-23 (406 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=884c588c-71bb-489c-a602-bb6c0463c7c0 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-04 (0 days ago) dmi.bios.date: 08/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.301:bd08/09/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930813/+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 1933023] [NEW] tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
Public bug reported: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? ** Affects: iproute2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Description changed: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? + + P.S. I did try pulling iproute2 directly from 20.04 repos using apt + pinning, but then had glibc version incomptibility problems. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1933023] Re: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel
** Tags added: upgrade-software-version ** Tags added: iproute2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1933023 Title: tc lacks Cake qdisc in 18.04 + HWE 5.4 kernel Status in iproute2 package in Ubuntu: New Bug description: I am using the 5.4 HWE kernel in 18.04, and even though this kernel has the CAKE qdisc, I am unable to use it as the version of tc, which is used to configure it, is too old. Even the backported tc is too old. Can we get the 20.04 iproute2 package, which does support the CAKE qdisc, backported to 18.04 to fix this? P.S. I did try pulling iproute2 directly from 20.04 repos using apt pinning, but then had glibc version incomptibility problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1933023/+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 1923291] Re: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10
** Changed in: zfs-linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1923291 Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 Status in zfs-linux package in Ubuntu: Fix Released Bug description: Trying to get new PC running, combination of Ryzen CPU, B550 motherboard & zfs filesystems means I need to use recent kernel, but cannot install zfs ProblemType: Package DistroRelease: Ubuntu 20.10 Package: zfs-dkms (not installed) Uname: Linux 5.11.12-051112-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Apr 10 16:59:29 2021 ErrorMessage: installed zfs-dkms package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2021-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10ubuntu0.3 SourcePackage: zfs-linux Title: package zfs-dkms (not installed) failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1923291/+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 1908090] Re: ubuntu 20.04 kdump fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: kexec-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1908090 Title: ubuntu 20.04 kdump fails Status in kexec-tools package in Ubuntu: Confirmed Bug description: When linux-crashdump (5.4.0.58.61) is enabled on Ubuntu 20.04 LTS, everything appears to be in good working order, according to "systemctl status kdump-tools" and "kdump-config status". However, upon an actual crash, the system hangs, and no crash files are produced. I've investigated and have learned that the capture kernel does indeed start, but it is unable to unpack the rootfs/initrd, and thus fails and hangs. [1.070469] Trying to unpack rootfs image as initramfs... [1.333182] swapper/0 invoked oom-killer: gfp_mask=0x100cc2(GFP_HIGHUSER), order=0, oom_score_adj=0 [1.335074] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-26-generic #30-Ubuntu [1.336396] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Ubuntu-1.8.2-1ubuntu1 04/01/2014 [1.336396] Call Trace: [1.336396] dump_stack+0x6d/0x9a [1.336396] dump_header+0x4f/0x1eb [1.336396] out_of_memory.part.0.cold+0x39/0x83 [1.336396] out_of_memory+0x6d/0xd0 ... [1.413202] ---[ end Kernel panic - not syncing: System is deadlocked on memory ]--- On this system with 8G of memory, the crash memory as specified on the kernel command line is "crashkernel=512M-:192M". I changed the 192M to 256M, and now kdump works. Not sure how the 192M value is chosen, but it does not work. I think this used value used to work for 16.04 and maybe 18.04 (I didn't try), but is no longer useful for 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1908090/+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 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
I've gotten part way through the bisect. Make has been giving me several errors and warnings and then hanging when I try to create the test kernel and I don't really have the knowledge, time, or inclination to debug what is wrong with it on my own. Since it seems like this suspend bug only affects me and kernel 5.13 fixes the problem, I am fine with living with the suspend issue until 5.13 is released. If this ends up being a more widespread/critical problem and you want me to reopen the issue, I can, but otherwise I am going to stop here. Thank you for your help with the bisect. Here is as far as I have gotten in the bisect, in case it is helpful $ git bisect log # bad: [d07f6ca923ea0927a1024dfccafc5b53b61cfecc] Linux 5.13-rc2 # good: [bf05bf16c76bb44ab5156223e1e58e26dfe30a88] Linux 5.12-rc8 git bisect start 'v5.13-rc2' 'v5.12-rc8' # bad: [35655ceb31b56cd1cb52635a725dfcdb9662d7b7] Merge tag 'clk-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux git bisect bad 35655ceb31b56cd1cb52635a725dfcdb9662d7b7 # good: [55ba0fe059a577fa08f23223991b24564962620f] Merge tag 'for-5.13-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux git bisect good 55ba0fe059a577fa08f23223991b24564962620f # bad: [a1a1ca70deb3ec600eeabb21de7f3f48aaae5695] Merge tag 'drm-misc-next-fixes-2021-04-22' of git://anongit.freedesktop.org/drm/drm-misc into drm-next git bisect bad a1a1ca70deb3ec600eeabb21de7f3f48aaae5695 -- 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/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+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 1932055] Re: Mute/Mic mute LEDs and right speaker are not work on HP platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1932055 Title: Mute/Mic mute LEDs and right speaker are not work on HP platforms Status in OEM Priority Project: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP Elite Dragonfly G2 Notebook PC 2) HP EliteBook x360 1040 G8 Notebook PC 3) HP EliteBook 840 Aero G8 Notebook PC 4) HP ZBook Power 15.6 inch G8 Mobile Workstation PC The right channel of internal speaker doesn't work on 1) HP Elite Dragonfly G2 Notebook PC 2) HP EliteBook x360 1040 G8 Notebook PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/speaker are work good on 1) HP Elite Dragonfly G2 Notebook PC 2) HP EliteBook x360 1040 G8 Notebook PC 3) HP EliteBook 840 Aero G8 Notebook PC 4) HP ZBook Power 15.6 inch G8 Mobile Workstation PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/speaker will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1932055/+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 1930707] Re: Mic-mute/mute LEDs not work on some HP platforms
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930707 Title: Mic-mute/mute LEDs not work on some HP platforms Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC The right channel of internal speaker doesn't work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/function are work good on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/function will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930707/+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 1933041] [NEW] Issues on Lenovo Legion 5 Pro 16ACH6
Public bug reported: Hi, I have some issues on my new Lapton on Ubuntu 21.04. I can't change brightness for the screen and I can't use hdmi and usb-c ports for external screens with dynamic gpu usage (amd graphic solution). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcarrere 1584 F pulseaudio /dev/snd/controlC0: mcarrere 1584 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 21:14:52 2021 InstallationDate: Installed on 2021-06-20 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82JQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b8dc7c13-4a58-450e-8f58-beae03846177 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 Pro 16ACH6H dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrGKCN36WW:bd04/21/2021:br1.36:efr1.36:svnLENOVO:pn82JQ:pvrLegion5Pro16ACH6H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion5Pro16ACH6H: dmi.product.family: Legion 5 Pro 16ACH6H dmi.product.name: 82JQ dmi.product.sku: LENOVO_MT_82JQ_BU_idea_FM_Legion 5 Pro 16ACH6H dmi.product.version: Legion 5 Pro 16ACH6H dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- 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/1933041 Title: Issues on Lenovo Legion 5 Pro 16ACH6 Status in linux package in Ubuntu: New Bug description: Hi, I have some issues on my new Lapton on Ubuntu 21.04. I can't change brightness for the screen and I can't use hdmi and usb-c ports for external screens with dynamic gpu usage (amd graphic solution). ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mcarrere 1584 F pulseaudio /dev/snd/controlC0: mcarrere 1584 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 20 21:14:52 2021 InstallationDate: Installed on 2021-06-20 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 82JQ ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=b8dc7c13-4a58-450e-8f58-beae03846177 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/21/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 5 Pro 16ACH6H dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrGKCN36WW:bd04/21/2021:br1.36:efr1.36:svnLENOVO:pn82JQ:pvrLegion5Pro16ACH6H:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion5Pro16ACH6H: dmi.product.family: Legion 5 Pro 16ACH6H dmi.product.name: 82JQ dmi.product.sku: LENOVO_MT_82JQ_BU_idea_FM_Legion 5 Pro 16ACH6H dmi.product.version: Legion 5 Pro 16ACH6H dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1933041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1873052] Re: X11 fractional scaling causes two cursors after login (usually with amdgpu)
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1344 https://gitlab.gnome.org/GNOME/mutter/-/issues/1344 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1344 Importance: Unknown Status: Unknown -- 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/1873052 Title: X11 fractional scaling causes two cursors after login (usually with amdgpu) Status in Mutter: Unknown Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873052/+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 1932965] Re: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found)
** Tags added: ubuntu-kernel-selftests -- 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/1932965 Title: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Found this on G/RISC-V, cycle sru-20210531: 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 02:41:52 DEBUG| [stdout] # PASS: vrf 02:41:54 DEBUG| [stdout] # PASS: vxlan 02:41:55 DEBUG| [stdout] # PASS: fou 02:41:55 DEBUG| [stdout] # PASS: macsec 02:41:58 DEBUG| [stdout] # PASS: ipsec 02:42:01 DEBUG| [stdout] # PASS: ipsec_offload 02:42:02 DEBUG| [stdout] # PASS: bridge fdb get 02:42:03 DEBUG| [stdout] # PASS: neigh get 02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 Seems uuidgen is from package "uuid-runtime", not sure if this was not installed in the environment where test ran. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932965/+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 1928889] Re: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range)
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => 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/1928889 Title: devlink_port_split in net from ubuntu_kernel_selftests linux ADT test failure with linux/5.11.0-18.19 ( list index out of range) Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Hirsute: New Status in linux-oem-5.10 source package in Hirsute: New Bug description: This is a scripted bug report about ADT failures while running linux tests for linux/5.11.0-18.19 on hirsute. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Not a regression. Found to occur previously on hirsute/linux 5.11.0-14.15 Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/amd64/l/linux/20210515_005957_75e5a@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/arm64/l/linux/20210513_203508_96fd3@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/ppc64el/l/linux/20210513_163708_c0203@/log.gz s390x: https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute/hirsute/s390x/l/linux/20210513_144454_54b04@/log.gz 17:39:37 DEBUG| [stdout] # selftests: net: devlink_port_split.py 17:39:37 DEBUG| [stdout] # Traceback (most recent call last): 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 277, in 17:39:37 DEBUG| [stdout] # main() 17:39:37 DEBUG| [stdout] # File "/tmp/autopkgtest.ojlWKQ/build.XZw/src/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net/./devlink_port_split.py", line 242, in main 17:39:37 DEBUG| [stdout] # dev = list(devs.keys())[0] 17:39:37 DEBUG| [stdout] # IndexError: list index out of range 17:39:37 DEBUG| [stdout] not ok 43 selftests: net: devlink_port_split.py # exit=1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1928889/+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 1923049] Re: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
Test failed with 2hr timeout, I will give it a try manually to see how long we will need. -- 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/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+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 1932965] Re: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found)
Hmm, didn't see this failure in generic kernel (and other variants). And it looks like this uuid-runtime will be installed automatically on a freshly deployed system (checked with generic kernel and gcp), so I think this is limited to riscv. We can either: 1. Just install this package on this node (it's manually provisioned) 2. Add this package to the required packages of this test. -- 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/1932965 Title: selftests/net/rtnetlink - Failure in RISC-V (uuidgen command not found) Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed Bug description: Found this on G/RISC-V, cycle sru-20210531: 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # ./rtnetlink.sh: line 366: uuidgen: command not found 02:41:52 DEBUG| [stdout] # FAIL: set interface alias test-dummy0 to 02:41:52 DEBUG| [stdout] # PASS: vrf 02:41:54 DEBUG| [stdout] # PASS: vxlan 02:41:55 DEBUG| [stdout] # PASS: fou 02:41:55 DEBUG| [stdout] # PASS: macsec 02:41:58 DEBUG| [stdout] # PASS: ipsec 02:42:01 DEBUG| [stdout] # PASS: ipsec_offload 02:42:02 DEBUG| [stdout] # PASS: bridge fdb get 02:42:03 DEBUG| [stdout] # PASS: neigh get 02:42:03 DEBUG| [stdout] not ok 11 selftests: net: rtnetlink.sh # exit=1 Seems uuidgen is from package "uuid-runtime", not sure if this was not installed in the environment where test ran. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1932965/+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 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
Maybe upgrade to Hirsute? It uses 5.11 kernel. -- 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/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+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 1923049] Re: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: ubuntu-kernel-tests Status: New => 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/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+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 1925055] Re: Boot stuck in UEFI after enrolling keys for drivers
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925055 Title: Boot stuck in UEFI after enrolling keys for drivers Status in linux package in Ubuntu: Expired Status in systemd package in Ubuntu: Invalid Bug description: Hello, I faced the following problem. After the fresh installation of Ubuntu, everything works well. But after I install some drivers (NVidia or VirtualBox) that require key enrolling I stuck on boot. See below detailed description. Normal behavior: 1. Press the power button on Laptop. 2. Enter to Grub menu, select Ubuntu and continue. 3. See boot logo. 4. Successfully boot in Ubuntu. Bad behavior: 1. Install drivers (for example VirtualBox via $ sudo apt-get install virtualbox). 2. Enter a password for Secure boot during installation. 3. Shut down the system. 4. Press the power button on Laptop. 5. Enter to Grub menu, select Ubuntu and continue. 6. See boot logo. 7. System stuck, only black screen and blinking white underscore cursor. After some time I realized that to continue boot after step 7 I need the following. 8. Change console by Alt+Fn+F2. 9. Return to the original console by Alt+Fn+F1 (after that booting continues immediately). 10. Successfully boot in Ubuntu. Issue occurrence: 100%. Removing drivers (apt-get purge virtualbox) doesn't help. Disabling of secure boot in BIOS doesn't help. Expected behavior: To be able to boot successfully. Actual result: Stuck on boot. Environment: $ lsb_release -rd Description: Ubuntu Hirsute Hippo (development branch) Release: 21.04 $ uname -a Linux tiptop 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Please find dmesg attached. Any help is appreciated! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gluttton 1602 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-06 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 82A1 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=30921e6b-67db-4b36-aa12-16e269548c95 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute wayland-session Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: Upgraded to hirsute on 2021-03-06 (46 days ago) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/14/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: DHCN31WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14IIL05 dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvrDHCN31WW:bd01/14/2021:br1.31:efr1.29:svnLENOVO:pn82A1:pvrYogaSlim714IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrYogaSlim714IIL05: dmi.product.family: Yoga Slim 7 14IIL05 dmi.product.name: 82A1 dmi.product.sku: LENOVO_MT_82A1_BU_idea_FM_Yoga Slim 7 14IIL05 dmi.product.version: Yoga Slim 7 14IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925055/+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 1930279] Re: [Ivy Bridge] flashing triangles on screen
** Changed in: linux (Ubuntu) Assignee: Amirhossein (bokensmile8) => (unassigned) -- 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/1930279 Title: [Ivy Bridge] flashing triangles on screen Status in linux package in Ubuntu: New Status in mesa package in Ubuntu: New Bug description: when i did upgrade my ubuntu from 20.04 to 20.10 i have small winking triangles on my screen, they sometimes will appear when i watching a youtube video they will appear on the video's seek bar or when i typing they will appear on selected texts,but the main and most annoying state of it happens when I am playing minecraft,my entire game screen has these little triangles ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 18:05:33 2021 DistUpgraded: 2021-05-27 14:18:07,483 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.16, 5.4.0-73-generic, x86_64: installed virtualbox, 6.1.16, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [1043:844d] InstallationDate: Installed on 2020-01-10 (507 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=a5a5279f-cdf5-4129-94fa-8f17f7401833 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to groovy on 2021-05-27 (4 days ago) dmi.bios.date: 03/19/2014 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd03/19/2014:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLXR2.0:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930279/+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 1930275] Re: [nvidia] System does not wake up after suspend
** Tags removed: groovy ** Tags added: hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1930275 Title: [nvidia] System does not wake up after suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-460 package in Ubuntu: Incomplete Bug description: Ubuntu 20.10 suspend is not working. After suspend it does not wake up. And I have to hard reboot machine. It is happening since last few days. Here is error message I see from logs: "Failed to start Application launched by gnome-session-binary. A start job for unit UNIT has finished with a failure. The job identifier is 368 and the job result is failed. Failed to start LSB: OpenIPMI Driver init script. A start job for unit openipmi.service has finished with a failure. The job identifier is 151 and the job result is failed. " ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-53.60-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..0a.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.73.01 Thu Apr 1 21:40:36 UTC 2021 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 31 09:04:06 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.73.01, 5.8.0-50-generic, x86_64: installed nvidia, 460.73.01, 5.8.0-53-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Several times a day GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Within the last few days GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] [10de:1f06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. TU106 [GeForce RTX 2060 SUPER] [3842:3061] InstallationDate: Installed on 2020-02-15 (471 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-53-generic root=UUID=ae47d531-67a5-47ff-ba8c-fd3928cd4cad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7b dmi.board.asset.tag: Default string dmi.board.name: X570 AORUS MASTER dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7b:bd09/17/2019:br5.14:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: X570 AORUS MASTER dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930275/+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 1932993] Re: AMDGPU: Support to load new MC firmware for Polaris12 32bit ASIC
** Description changed: [Impact] AMD introduce a new firmware and has been SRUed in this public bug. https://bugs.launchpad.net/ubuntu/focal/+source/linux-firmware/+bug/1929147 For the kernel(oem-5.10/groovy), also need other patches to load this firmware. [Fix] Support to load polaris12_32_mc.bin [Test] 1. Check by modinfo and cnofirm polaris12_32_mc.bin is loaded by amdgpu.ko + #modinfo amdgpu | grep polaris12_32_mc.bin + firmware: amdgpu/polaris12_32_mc.bin + 2. Equipped the rx540(PD5001) that would trigger issue and system would bootup successfully into desktop. *some rx540(PD5000) can't trigger the issue. [Regression Potential] Medium, introduce a brand new firmware may cause regression. -- 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/1932993 Title: AMDGPU: Support to load new MC firmware for Polaris12 32bit ASIC Status in HWE Next: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: New Status in linux source package in Focal: New Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux-oem-5.10 source package in Groovy: New Bug description: [Impact] AMD introduce a new firmware and has been SRUed in this public bug. https://bugs.launchpad.net/ubuntu/focal/+source/linux-firmware/+bug/1929147 For the kernel(oem-5.10/groovy), also need other patches to load this firmware. [Fix] Support to load polaris12_32_mc.bin [Test] 1. Check by modinfo and cnofirm polaris12_32_mc.bin is loaded by amdgpu.ko #modinfo amdgpu | grep polaris12_32_mc.bin firmware: amdgpu/polaris12_32_mc.bin 2. Equipped the rx540(PD5001) that would trigger issue and system would bootup successfully into desktop. *some rx540(PD5000) can't trigger the issue. [Regression Potential] Medium, introduce a brand new firmware may cause regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932993/+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 1932586] Re: Processes launched during the NIC load is high may hang up.
** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1932586 Title: Processes launched during the NIC load is high may hang up. Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Hirsute: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu ❯ lsb_release -rd Description:Ubuntu 21.04 Release:21.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center ❯ LANG=C apt-cache policy linux-raspi linux-raspi: Installed: 5.11.0.1009.7 Candidate: 5.11.0.1009.7 Version table: *** 5.11.0.1009.7 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute-updates/main arm64 Packages 500 http://ports.ubuntu.com/ubuntu-ports hirsute-security/main arm64 Packages 100 /var/lib/dpkg/status 5.11.0.1007.5 500 500 http://ports.ubuntu.com/ubuntu-ports hirsute/main arm64 Packages 3) What you expected to happen Processes launched during the NIC load is high will exit normally. 4) What happened instead I'm using hirsute on Raspberry Pi 4 model B(4GB RAM). Some processes launched during the NIC load is high might not exit. What "NIC load is high" means: - I have configured crontab to run Ookla's speedtest-cli which generates heavy network traffic every 15 minites. - During speedtest-cli, Softirq becomes higher. - SoC(BCM2711) built-in NIC(driver is bcmgenet) What "may not exit" means: - Some processes launched during speedtest-cli is running will not exit. It remains with consuming CPU 100% and not accept any signals including SIGKILL. - Those processes can't be attached by gdb or strace. Trying to do so, gdb and strace will freeze. I could't terminate the processes in any way. But the system could be rebooted by "sudo reboot" command. I configured RFS/RPS to distribute Softirq among CPU cores. It was quite effective, but did not prevent the problem completely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1932586/+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 1931239] Re: System crash regulary
Please also be sure to only install the Nvidia driver using the 'Additional Drivers' app. ** Summary changed: - System crash regulary + [Nvidia Quadro RTX 4000] System crash regularly ** Tags added: nouveau nvidia -- 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/1931239 Title: [Nvidia Quadro RTX 4000] System crash regularly Status in linux package in Ubuntu: Incomplete Bug description: I saw the following error in the kernel log (kern.log) directly after the crash occurred. I was watching my system with a tail -f kern.log on a remote shell. --- Jun 8 11:29:56 workstation kernel: [49956.666945] general protection fault, probably for non-canonical address 0xe365a4770fa8af10: [#1] SMP NOPTI Jun 8 11:29:56 workstation kernel: [49956.666958] CPU: 8 PID: 706155 Comm: git Tainted: G IOE 5.11.0-18-generic #19-Ubuntu Jun 8 11:29:56 workstation kernel: [49956.666966] Hardware name: Dell Inc. Precision 5820 Tower X-Series/0X75JG, BIOS 2.2.0 04/14/2020 Jun 8 11:29:56 workstation kernel: [49956.666969] RIP: 0010:__kmalloc+0xb2/0x250 Jun 8 11:29:56 workstation kernel: [49956.666983] Code: 83 72 63 49 8b 00 49 83 78 10 00 48 89 45 c0 0f 84 85 01 00 00 48 85 c0 0f 84 7c 01 00 00 41 8b 4c 24 28 49 8b 3c 24 48 01 c1 <48> 8b 19 48 89 ce 49 33 9c 24 b8 00 00 00 48 8d 4a 01 48 0f ce 48 Jun 8 11:29:56 workstation kernel: [49956.666989] RSP: :ae48650b7878 EFLAGS: 00010282 Jun 8 11:29:56 workstation kernel: [49956.666996] RAX: e365a4770fa8aee0 RBX: RCX: e365a4770fa8af10 Jun 8 11:29:56 workstation kernel: [49956.667000] RDX: 00044185 RSI: 0d40 RDI: 000310c0 Jun 8 11:29:56 workstation kernel: [49956.667004] RBP: ae48650b78c0 R08: 9f9c9fa310c0 R09: 0001 Jun 8 11:29:56 workstation kernel: [49956.667008] R10: 0001 R11: R12: 9f8d40043a00 Jun 8 11:29:56 workstation kernel: [49956.667012] R13: 0060 R14: 9f8d40043a00 R15: 0d40 Jun 8 11:29:56 workstation kernel: [49956.667016] FS: 7f2038755f80() GS:9f9c9fa0() knlGS: Jun 8 11:29:56 workstation kernel: [49956.667021] CS: 0010 DS: ES: CR0: 80050033 Jun 8 11:29:56 workstation kernel: [49956.667024] CR2: 7f2038a1c000 CR3: 0002ac41e004 CR4: 003726e0 Jun 8 11:29:56 workstation kernel: [49956.667029] DR0: DR1: DR2: Jun 8 11:29:56 workstation kernel: [49956.667032] DR3: DR6: fffe0ff0 DR7: 0400 Jun 8 11:29:56 workstation kernel: [49956.667036] Call Trace: Jun 8 11:29:56 workstation kernel: [49956.667039] ? ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667051] ext4_find_extent+0x381/0x450 Jun 8 11:29:56 workstation kernel: [49956.667058] ext4_ext_map_blocks+0x72/0x980 Jun 8 11:29:56 workstation kernel: [49956.667064] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667073] ? find_get_entry+0xcd/0x160 Jun 8 11:29:56 workstation kernel: [49956.667080] ? ext4_es_lookup_extent+0x164/0x210 Jun 8 11:29:56 workstation kernel: [49956.667087] ext4_map_blocks+0x261/0x590 Jun 8 11:29:56 workstation kernel: [49956.667093] ? xas_load+0x9/0x80 Jun 8 11:29:56 workstation kernel: [49956.667103] ? xa_load+0x61/0x90 Jun 8 11:29:56 workstation kernel: [49956.667110] ext4_mpage_readpages+0x533/0xa70 Jun 8 11:29:56 workstation kernel: [49956.667118] ? __mod_lruvec_state+0x3a/0x50 Jun 8 11:29:56 workstation kernel: [49956.667127] ext4_readahead+0x33/0x40 Jun 8 11:29:56 workstation kernel: [49956.667132] read_pages+0x89/0x270 Jun 8 11:29:56 workstation kernel: [49956.667140] page_cache_ra_unbounded+0x137/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667147] do_page_cache_ra+0x3d/0x40 Jun 8 11:29:56 workstation kernel: [49956.667152] do_sync_mmap_readahead+0x10d/0x1c0 Jun 8 11:29:56 workstation kernel: [49956.667159] filemap_fault+0x571/0x840 Jun 8 11:29:56 workstation kernel: [49956.667166] ? xas_find+0x17a/0x1d0 Jun 8 11:29:56 workstation kernel: [49956.667172] ? filemap_map_pages+0x215/0x3f0 Jun 8 11:29:56 workstation kernel: [49956.667179] ext4_filemap_fault+0x32/0x50 Jun 8 11:29:56 workstation kernel: [49956.667185] __do_fault+0x3c/0xe0 Jun 8 11:29:56 workstation kernel: [49956.667194] do_fault+0xc4/0x1f0 Jun 8 11:29:56 workstation kernel: [49956.667201] handle_pte_fault+0x1e5/0x260 Jun 8 11:29:56 workstation kernel: [49956.667207] __handle_mm_fault+0x599/0x7c0 Jun 8 11:29:56 workstation kernel: [49956.667216] handle_mm_fault+0xd7/0x2b0 Jun 8 11:29:56 workstation kernel: [49956.667224] do_user_addr_fault+0x1a3/0
[Kernel-packages] [Bug 1928744] Re: Disk IO very slow on kernel 4.15.0-142-generic
Hey, We experienced the performance issue on different hardware servers: LENOVO System x3650 M5 Lenovo ThinkSystem SR650 with the following kernels: 4.15.0-137-generic: disk performance issue 4.15.0-139-generic: disk performance issue 4.15.0-140-generic: disk performance issue 4.15.0-142-generic: disk performance issue I haven't seen this issue on virtual machines (VMware VMs Ubuntu 18/20). At the moment, I'm testing "4.15.0-144-generic". To early to say it is free of the bug - I will come back in a week. Thanks Mariusz -- 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/1928744 Title: Disk IO very slow on kernel 4.15.0-142-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: After upgrading Ubuntu 18.04 kernel from 4.15.0-136-generic to kernel 4.15.0-142-generic disk IOs (writes) are suffering from terrible delay. Time required to write 1GB of data to the dist is ~12 minutes. 1GB in 12 minutes: strace -ttvvff -o mel.strace dd bs=1024k count=1024 if=/dev/zero of=/data/disk_test/dd_test Before the upgrade, it took seconds to complete. The only change which was done on the system was security upgrade done with unattended-upgrade utility and main repositories for bionic and bionic-security. This is physical server LENOVO System x3650 M5, with Symbios Logic MegaRAID SAS-3 3108 disk controller. The only difference which I see is that there are more modules loaded by the latest kernel. I would expect that the performance would be the same. There were no changes to the physical server and the disks are reported as online and healthy. No only dd is affected but also all disk-based operation by barman (we are using postgres steaming backup along with rsync/ssh archiving). I think this could be a kernel bug. I would be happy to provide other information which would help in fixing this problem. = Details: lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 lsmod Module Size Used by ip6_tables 28672 0 iptable_filter 16384 0 ip_tables 28672 1 iptable_filter x_tables 40960 3 iptable_filter,ip6_tables,ip_tables tcp_diag 16384 0 udp_diag 16384 0 raw_diag 16384 0 inet_diag 24576 3 tcp_diag,raw_diag,udp_diag unix_diag 16384 0 binfmt_misc20480 1 ipmi_ssif 32768 0 kvm_intel 217088 0 kvm 614400 1 kvm_intel irqbypass 16384 1 kvm crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 pcbc 16384 0 aesni_intel 188416 0 aes_x86_64 20480 1 aesni_intel crypto_simd16384 1 aesni_intel glue_helper16384 1 aesni_intel cryptd 24576 3 crypto_simd,ghash_clmulni_intel,aesni_intel ipmi_si57344 0 ipmi_devintf 20480 0 ipmi_msghandler53248 3 ipmi_devintf,ipmi_si,ipmi_ssif acpi_pad 180224 0 bonding 163840 0 lp 20480 0 parport49152 1 lp autofs440960 2 mgag20045056 1 i2c_algo_bit 16384 1 mgag200 ttm 106496 1 mgag200 drm_kms_helper172032 1 mgag200 syscopyarea16384 1 drm_kms_helper tg3 167936 0 sysfillrect16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops16384 1 drm_kms_helper ptp20480 1 tg3 drm 401408 4 drm_kms_helper,mgag200,ttm pps_core 20480 1 ptp megaraid_sas 143360 12 lspci -vnn -s 0b:00.0 0b:00.0 RAID bus controller [0104]: LSI Logic / Symbios Logic MegaRAID SAS-3 3108 [Invader] [1000:005d] (rev 02) Subsystem: IBM MegaRAID SAS-3 3108 [Invader] [1014:0454] Physical Slot: 9 Flags: bus master, fast devsel, latency 0, IRQ 31, NUMA node 0 I/O ports at 2e00 [size=256] Memory at 903f (64-bit, non-prefetchable) [size=64K] Memory at 9040 (64-bit, non-prefetchable) [size=1M] Expansion ROM at [disabled] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product Data Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=97 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting
[Kernel-packages] [Bug 1923049] Re: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
** Tags added: sru-20210531 -- 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/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+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 1931870] [NEW] System freezes several times per week, sometimes more than once per day
You have been subscribed to a public bug: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-55-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug fonts groovy kubuntu nouveau ubuntu -- System freezes several times per week, sometimes more than once per day https://bugs.launchpad.net/bugs/1931870 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 1931870] Re: System freezes several times per week, sometimes more than once per day
The open source 'nouveau' driver you are using is known to be unstable. Please use the 'Additional Drivers' app to install the official Nvidia driver. ** Tags added: nouveau ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Summary changed: - System freezes several times per week, sometimes more than once per day + [nouveau] System freezes several times per week, sometimes more than once per day -- 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/1931870 Title: [nouveau] System freezes several times per week, sometimes more than once per day Status in linux package in Ubuntu: New Bug description: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-55.62-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Jun 14 15:18:03 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] [10de:1fb9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117GLM [Quadro T1000 Mobile] [17aa:2297] InstallationDate: Installed on 2021-01-15 (150 days ago) InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20QQS0KL13 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.8.0-55-generic root=UUID=35cef147-e021-4bdd-b8db-31a3192c8a6a ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/04/2020 dmi.bios.release: 1.23 dmi.bios.vendor: LENOVO dmi.bios.version: N2NET38W (1.23 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QQS0KL13 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: ZF211710 dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.14 dmi.modalias: dmi:bvnLENOVO:bvrN2NET38W(1.23):bd06/04/2020:br1.23:efr1.14:svnLENOVO:pn20QQS0KL13:pvrThinkPadP53:rvnLENOVO:rn20QQS0KL13:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P53 dmi.product.name: 20QQS0KL13 dmi.product.sku: LENOVO_MT_20QQ_BU_Think_FM_ThinkPad P53 dmi.product.version: ThinkPad P53 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931870/+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 1923049] Re: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
It takes almost 3 hours to complete... $ time sudo /opt/ltp/runltp -f /opt/ltp/runtest/dio real176m50.182s user11m8.089s sys 2m7.213s -- 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/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+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
