[Kernel-packages] [Bug 1931432] Re: crash FTBFS on riscv64
Seems to fail with a seg fault on the version in 21.04, https://bugs.launchpad.net/ubuntu/+source/crash/7.2.9-2ubuntu2 . Not rebuilt on Impish, but would assume the same might happen there. ** Tags added: focal ftbfs groovy hirsute impish -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931432 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: Confirmed Status in crash source package in Focal: Confirmed Status in crash source package in Groovy: Confirmed Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931432/+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 1931431] Re: crash FTBFS on riscv64
*** This bug is a duplicate of bug 1931432 *** https://bugs.launchpad.net/bugs/1931432 ** This bug has been marked a duplicate of bug 1931432 crash FTBFS on riscv64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1931431 Title: crash FTBFS on riscv64 Status in crash package in Ubuntu: New Bug description: Crash fails to build from source on riscv at least for Focal and Groovy, later releases may also be affected but I haven't confirm it. Examples of failed builds : Groovy : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.10.1/+build/21630864 Focal : https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu1.20.04.1/+build/21630885 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1931431/+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 1931630] [NEW] Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
You have been subscribed to a public bug: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` ** Affects: linux-meta-kvm (Ubuntu) Importance: Undecided Status: New -- Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail https://bugs.launchpad.net/bugs/1931630 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm 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 1931630] Re: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail
** Package changed: procps (Ubuntu) => linux-meta-kvm (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1931630 Title: Linux images for virtual machines with unset `CONFIG_MAGIC_SYSRQ` cause `10-magic-sysrq.conf` to fail Status in linux-meta-kvm package in Ubuntu: New Bug description: *procps* ships `/etc/sysctl.d/10-magic-sysrq.conf:kernel.sysrq = 176`, which is run by `systemd-sysctl.service`. This fails on a system run with a Linux image built for virtual machines *linux-image-kvm*, which has `CONFIG_MAGIC_SYSRQ` not set. ``` $ sudo /lib/systemd/systemd-sysctl Couldn't write '176' to 'kernel/sysrq', ignoring: No such file or directory Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Couldn't write 'fq_codel' to 'net/core/default_qdisc', ignoring: No such file or directory Couldn't write '4194304' to 'kernel/pid_max': Invalid argument $ grep SYSRQ /boot/config-5.4.0-1009-kvm # CONFIG_MAGIC_SYSRQ is not set ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-kvm/+bug/1931630/+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 1786013] Autopkgtest regression report (linux-meta-raspi/5.4.0.1037.72)
All autopkgtests for the newly accepted linux-meta-raspi (5.4.0.1037.72) for focal have finished running. The following regressions have been reported in tests triggered by the package: lime-forensics/unknown (arm64) systemd/unknown (arm64) nat-rtsp/unknown (arm64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (armhf) zfs-linux/unknown (arm64) wireguard/unknown (arm64) virtualbox-hwe/unknown (arm64) r8168/unknown (arm64) wireguard-linux-compat/1.0.20201112-1~20.04.1 (arm64) xtables-addons/unknown (arm64) v4l2loopback/unknown (arm64) rtl8812au/unknown (arm64) openafs/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-raspi [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1931763] [NEW] package linux-modules-extra-4.15.0-144-generic (not installed) failed to install/upgrade: kunde inte öppna "/lib/modules/4.15.0-144-generic/kernel/drivers/net/eth
Public bug reported: cannot upgrade 18.04-->20.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-144-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1530 F pulseaudio niklas 2071 F pulseaudio Date: Sat Jun 12 12:08:04 2021 DpkgHistoryLog: Start-Date: 2021-06-12 12:07:42 Commandline: apt --fix-broken install Requested-By: niklas (1000) Install: linux-modules-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-image-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-modules-extra-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-headers-4.15.0-144:amd64 (4.15.0-144.148, automatic), linux-headers-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.39.41, 4.15.0.144.131), linux-image-generic:amd64 (4.15.0.39.41, 4.15.0.144.131), linux-headers-4.15.0-39:amd64 (4.15.0-39.42, 4.15.0-39.42), linux-generic:amd64 (4.15.0.39.41, 4.15.0.144.131) ErrorMessage: kunde inte öppna "/lib/modules/4.15.0-144-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko.dpkg-new": Operationen inte tillåten InstallationDate: Installed on 2018-09-29 (986 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: FUJITSU ESPRIMO Q510 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=2027fa3f-b667-4e87-abf8-91844f68a7a2 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.02-2ubuntu8.4 SourcePackage: linux Title: package linux-modules-extra-4.15.0-144-generic (not installed) failed to install/upgrade: kunde inte öppna "/lib/modules/4.15.0-144-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko.dpkg-new": Operationen inte tillåten UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/17/2013 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V4.6.5.3 R1.23.0 for D3173-A1x dmi.board.name: D3173-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3173-A1 dmi.chassis.type: 16 dmi.chassis.vendor: FUJITSU dmi.chassis.version: C$NONE dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV4.6.5.3R1.23.0forD3173-A1x:bd01/17/2013:svnFUJITSU:pnESPRIMOQ510:pvr:rvnFUJITSU:rnD3173-A1:rvrS26361-D3173-A1:cvnFUJITSU:ct16:cvrC$NONE: dmi.product.name: ESPRIMO Q510 dmi.sys.vendor: FUJITSU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- 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/1931763 Title: package linux-modules-extra-4.15.0-144-generic (not installed) failed to install/upgrade: kunde inte öppna "/lib/modules/4.15.0-144-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko .dpkg-new": Operationen inte tillåten Status in linux package in Ubuntu: New Bug description: cannot upgrade 18.04-->20.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: linux-modules-extra-4.15.0-144-generic (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1530 F pulseaudio niklas 2071 F pulseaudio Date: Sat Jun 12 12:08:04 2021 DpkgHistoryLog: Start-Date: 2021-06-12 12:07:42 Commandline: apt --fix-broken install Requested-By: niklas (1000) Install: linux-modules-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-image-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-modules-extra-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic), linux-headers-4.15.0-144:amd64 (4.15.0-144.148, automatic), linux-headers-4.15.0-144-generic:amd64 (4.15.0-144.148, automatic) Upgrade: linux-headers-generic:amd64 (4.15.0.39.41, 4.15.0.144.131), linux-image-generic:amd64 (4.15.0.39.41, 4.15.0.144.131), linux-headers-4.15.0-39:amd64 (4.15.0-39.42, 4.15.0-39.42), linux-generic:amd64 (4.15.0.39.41, 4.15.0.144.131) ErrorMessage: kunde inte öppna "/lib/modules/4.15.0-144-generic/kernel/drivers/net/ethernet/broadcom/bnxt/bnxt_en.ko.dpkg-new": Operationen inte tillåten InstallationDate: Installed on 2018-09-29 (986 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: FUJITSU ESPR
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-bluefield/5.4.0.1013.14)
All autopkgtests for the newly accepted linux-meta-bluefield (5.4.0.1013.14) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-bluefield [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1931725] Re: initramfs-tools: use zstd as the default compression method
This bug was fixed in the package initramfs-tools - 0.140ubuntu5 --- initramfs-tools (0.140ubuntu5) impish; urgency=medium * Switch default initramfs compression to zstd, as it produces the lower overall boot time. LP: #1931725 -- Dimitri John Ledkov Fri, 11 Jun 2021 16:55:30 +0100 ** Changed in: initramfs-tools (Ubuntu) Status: Fix Committed => Fix Released -- 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/1931725 Title: initramfs-tools: use zstd as the default compression method Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: New Bug description: Turns out that loading is always the slow part in loading initramfs into memory and decompressing it since decompression is always the final 10-20% or so of the task. It therefore makes sense to use a good compressor that shrinks the initramfs as much as possible with little decompression overhead. Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in decompression, the image size is much smaller with zstd than lz4, and since ~80-90% of the boot time is loading the image it makes sense to use zstd. Attached is a libreoffice spread sheet showing typical load and decompression times for a fairly standard 3.4 GHZ intel box with data for load times for a 5400 RPM, 7200 RPM and SATA SSD drives. The conclusions from the test results (attached) show: 1. Loading time is always significantly slower than decompression time. 2. ZSTD is 5x slower than LZ4 in decompression speed but produces far better compressed images 3. Given that loading time is the major factor in loading + decompression, ZSTD is best for kernel and initramfs boot timings. (Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3 /kernel-compression-method.txt for some raw data on drive load speeds for the same UEFI box I did a couple of years ago). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1931725/+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 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931684/+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 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
Im using Ubuntu 20.04 LTS and have the same problem. I got the problem after upgrading from Kernel 5.4.0-73-generic to 5.4.0-74-generic. As I got in addition a firmware/microcode update it may be possible that the error is adjacent to that update too. If I boot to kernel 5.4.0-73-generic I have access to the serial line (e.g. /dev/ttyACM3). -- 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/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931684/+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 1931684] Re: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed
excerpt from /var/log/apt/history.log: Update from 73 to 74: Commandline: aptdaemon role='role-commit-packages' sender=':1.165' Install: linux-image-5.4.0-74-generic:amd64 (5.4.0-74.83, automatic),... Update firmware/microcode: Commandline: aptdaemon role='role-commit-packages' sender=':1.173' Upgrade: intel-microcode:amd64 (3.20210216.0ubuntu0.20.04.1, 3.20210608.0ubuntu0.20.04.1), linux-firmware:amd64 (1.187.12, 1.187.14) ** Also affects: intel-microcode (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: 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/1931684 Title: cdc_acm: acm_port_activate - usb_submit_urb(ctrl irq) failed Status in intel-microcode package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 18.04.5 LTS Recently, after kernel update 4.15.0.144 (didn't know about the case yet), i can't open serial ports on USB CDC devices (STM32 Virtual COMs in my case). using simple cat command (with or without sudo): $ sudo cat /dev/ttyACM1 cat: /dev/ttyACM1: Input/output error or some serial programs: Failed to connect to /dev/ttyACM1 : [Errno 5] could not open port /dev/ttyACM1: [Errno 5] Input/output error: '/dev/ttyACM1' dmesg: [ 3295.718270] cdc_acm 1-2:1.0: ttyACM1: USB ACM device [ 3302.508356] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed [ 3302.508940] cdc_acm 1-2:1.0: acm_port_activate - usb_submit_urb(ctrl irq) failed When i try spamming commands while plugging the device in, i am sometimes able to open the port (might be the clue). When i booted in ubuntu advanced mode to 4.15.0.143 kernel, everything started to work normally. Also tried HWE stack with 5.4.0.74 kernel, but the bug was also present there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1931684/+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 1931576] Autopkgtest regression report (linux-meta-aws/5.4.0.1050.52)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1050.52) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-aws in Ubuntu. https://bugs.launchpad.net/bugs/1931576 Title: Cloud kernels meta don't provide kernel-testing--*--modules-extra-- preferred Status in linux-meta-aws package in Ubuntu: New Status in linux-meta-aws-5.8 package in Ubuntu: New Status in linux-meta-azure package in Ubuntu: New Status in linux-meta-azure-5.8 package in Ubuntu: New Status in linux-meta-gcp package in Ubuntu: New Status in linux-meta-gcp-5.8 package in Ubuntu: New Status in linux-meta-aws source package in Focal: Fix Committed Status in linux-meta-aws-5.8 source package in Focal: Fix Committed Status in linux-meta-azure source package in Focal: Fix Committed Status in linux-meta-azure-5.8 source package in Focal: Fix Committed Status in linux-meta-gcp source package in Focal: Fix Committed Status in linux-meta-gcp-5.8 source package in Focal: Fix Committed Bug description: [Impact] ADT sets up the test environment by installing the image and modules-extra package via the virtual provides 'kernel-testing--linux---full--preferred' and 'kernel-testing--linux---modules-extra--preferred'. If those are not available, it falls back to using the real meta names as 'linux-image-' and 'linux-modules-extra-'. The 5.4 cloud kernels in Focal are not providing the virtual packages for 'kernel-testing--linux---modules-extra--preferred'. When the tests falls back to 'linux-modules-extra-', the new 5.8 cloud kernels are pulled for the tests as they are now the default sources. The oracle kernels in focal don't need fixing as they do not produce a linux-modules-extra-* package. ADT log: https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/acpi-call/20210609_092540_0a7a8@/log.gz [Fix] The meta packages need to be fixed to provide the necessary virtual packages for testing. [Where problems could occur] Adding new virtual meta packages could clash with existing names provided by other sources. However, if they existed ADT would have pulled them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-aws/+bug/1931576/+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 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1050.52)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1050.52) for focal have finished running. The following regressions have been reported in tests triggered by the package: v4l2loopback/0.12.3-1ubuntu0.4 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
I have tried 460.84 and 465.31 on a fresh hirsute install upgraded to impish with proposed enabled. Both result in a kernel oops when using DisplayPort -- 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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: 00
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Gabe, this bug results in a complete locked up computer, not just a wrong resolution. I suggest you report a new bug with your problem. -- 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/1930733 Title: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-465 package in Ubuntu: Triaged Bug description: I get a kernel oops with the 460.80 and 465.27 drivers on Hirsute Jun 03 16:26:57 willow kernel: Oops: [#1] SMP PTI Jun 03 16:26:57 willow kernel: CPU: 7 PID: 2004 Comm: Xorg Tainted: P OE 5.11.0-18-generic #19-Ubuntu Jun 03 16:26:57 willow kernel: Hardware name: System manufacturer System Product Name/PRIME H270M-PLUS, BIOS 1605 12/13/2019 Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:26:57 willow kernel: RBP: 8e318220add0 R08: 0001 R09: 8e318220acb8 Jun 03 16:26:57 willow kernel: R10: 8e3182204008 R11: 1010 R12: 0400 Jun 03 16:26:57 willow kernel: R13: 0003 R14: 8e3186ca8010 R15: 0800 Jun 03 16:26:57 willow kernel: FS: 7f5807f38a40() GS:8e3466dc() knlGS: Jun 03 16:26:57 willow kernel: CS: 0010 DS: ES: CR0: 80050033 Jun 03 16:26:57 willow kernel: CR2: 0170 CR3: 000140710005 CR4: 003706e0 Jun 03 16:26:57 willow kernel: DR0: DR1: DR2: Jun 03 16:26:57 willow kernel: DR3: DR6: fffe0ff0 DR7: 0400 Jun 03 16:26:57 willow kernel: Call Trace: Jun 03 16:26:57 willow kernel: ? _nv015556rm+0x7fd/0x1020 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv027155rm+0x22c/0x4f0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017787rm+0x303/0x5e0 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv017789rm+0xe1/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv022829rm+0xed/0x220 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv023065rm+0x30/0x60 [nvidia] Jun 03 16:26:57 willow kernel: ? _nv000704rm+0x16da/0x22b0 [nvidia] Jun 03 16:26:57 willow kernel: ? rm_init_adapter+0xc5/0xe0 [nvidia] Jun 03 16:26:57 willow kernel: ? nv_open_device+0x122/0x8e0 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_open+0x2b7/0x560 [nvidia] Jun 03 16:26:57 willow kernel: ? nvidia_frontend_open+0x58/0xa0 [nvidia] Jun 03 16:26:57 willow kernel: ? chrdev_open+0xf7/0x220 Jun 03 16:26:57 willow kernel: ? cdev_device_add+0x90/0x90 Jun 03 16:26:57 willow kernel: ? do_dentry_open+0x156/0x370 Jun 03 16:26:57 willow kernel: ? vfs_open+0x2d/0x30 Jun 03 16:26:57 willow kernel: ? do_open+0x1c3/0x340 Jun 03 16:26:57 willow kernel: ? path_openat+0x10a/0x1d0 Jun 03 16:26:57 willow kernel: ? do_filp_open+0x8c/0x130 Jun 03 16:26:57 willow kernel: ? __check_object_size+0x1c/0x20 Jun 03 16:26:57 willow kernel: ? do_sys_openat2+0x9b/0x150 Jun 03 16:26:57 willow kernel: ? __x64_sys_openat+0x56/0x90 Jun 03 16:26:57 willow kernel: ? do_syscall_64+0x38/0x90 Jun 03 16:26:57 willow kernel: ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 Jun 03 16:26:57 willow kernel: Modules linked in: snd_seq_dummy snd_hrtimer vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) binfmt_misc zfs(PO) zunicode(PO) zzstd(O) zlua(O) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) > Jun 03 16:26:57 willow kernel: sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c hid_generic usbhid hid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd c> Jun 03 16:26:57 willow kernel: CR2: 0170 Jun 03 16:26:57 willow kernel: ---[ end trace 0013b6989b267f32 ]--- Jun 03 16:26:57 willow kernel: RIP: 0010:_nv015534rm+0x1b6/0x330 [nvidia] Jun 03 16:26:57 willow kernel: Code: 8b 87 68 05 00 00 ba 01 00 00 00 be 02 00 00 00 e8 bf eb 55 c8 41 83 c5 01 41 83 fd 1f 0f 84 0b 01 00 00 48 8b 45 10 44 89 ee <48> 8b b8 70 01 00 00 48 8b 87 d8 04 00 00 e8> Jun 03 16:26:57 willow kernel: RSP: :af4201893958 EFLAGS: 00010297 Jun 03 16:26:57 willow kernel: RAX: RBX: 0400 RCX: 0003 Jun 03 16:26:57 willow kernel: RDX: 0004 RSI: 0003 RDI: Jun 03 16:2
[Kernel-packages] [Bug 1916064] Re: Touchpad not detected on Ideapad 14ARE05
Can verify this is also effecting my laptop. -- 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/1916064 Title: Touchpad not detected on Ideapad 14ARE05 Status in linux package in Ubuntu: Confirmed Bug description: Laptop: Lenovo Ideapad 5-14ARE05 Laptop - Type 81YM - AMD Ryzen 7 4700U Description: Ubuntu 20.10 Release: 20.10 Linux leptovo 5.8.0-43-generic #49-Ubuntu SMP Fri Feb 5 03:01:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Also tested with: Linux leptovo 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - and other kernels. Hello! After updating the BIOS from 1.06 to 1.10 the touchpad is not recognised anymore. It was working fine with 5.9.12 (updated the version with Ukuu), but now it does not respons with any verion tried by me: 5.8.0.43 / 5.9.16 / 5.10.17 / 5.11.0. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lebucur1295 F pulseaudio /dev/snd/controlC1: lebucur1295 F pulseaudio /dev/snd/controlC0: lebucur1295 F pulseaudio /dev/snd/controlC2: lebucur1295 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-06 (137 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81YM Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=708db822-7208-4b47-8329-20d5cc13db11 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-43-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (120 days ago) UserGroups: adm cdrom dip i2c input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2020 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN24WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrDTCN24WW(V1.10):bd12/25/2020:br1.24:efr1.24:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916064/+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 1916064] Re: Touchpad not detected on Ideapad 14ARE05
The following workaround per Bug #1881319 Comment #32 does not work on fresh installation of Ubuntu 20.04 with 5.8.55 Edit /etc/default/grub file line to below: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash initcall_blacklist=elants_i2c_driver_init" $ sudo update-grub reboot -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1916064 Title: Touchpad not detected on Ideapad 14ARE05 Status in linux package in Ubuntu: Confirmed Bug description: Laptop: Lenovo Ideapad 5-14ARE05 Laptop - Type 81YM - AMD Ryzen 7 4700U Description: Ubuntu 20.10 Release: 20.10 Linux leptovo 5.8.0-43-generic #49-Ubuntu SMP Fri Feb 5 03:01:28 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Also tested with: Linux leptovo 5.11.0-051100-generic #202102142330 SMP Sun Feb 14 23:33:21 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux - and other kernels. Hello! After updating the BIOS from 1.06 to 1.10 the touchpad is not recognised anymore. It was working fine with 5.9.12 (updated the version with Ukuu), but now it does not respons with any verion tried by me: 5.8.0.43 / 5.9.16 / 5.10.17 / 5.11.0. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: lebucur1295 F pulseaudio /dev/snd/controlC1: lebucur1295 F pulseaudio /dev/snd/controlC0: lebucur1295 F pulseaudio /dev/snd/controlC2: lebucur1295 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-06 (137 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: LENOVO 81YM Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=708db822-7208-4b47-8329-20d5cc13db11 ro quiet splash mem_sleep_default=deep vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-43-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-10-23 (120 days ago) UserGroups: adm cdrom dip i2c input lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/25/2020 dmi.bios.release: 1.24 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN24WW(V1.10) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.ec.firmware.release: 1.24 dmi.modalias: dmi:bvnLENOVO:bvrDTCN24WW(V1.10):bd12/25/2020:br1.24:efr1.24:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1916064/+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 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05
With a fresh installation of Ubuntu 20.04 with kernel 5.8.55 the above fixes do not work -- 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/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+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 1864045] Re: [SRU] Hibernation events sometimes missed on repeated attempts
** Changed in: acpid (Ubuntu Bionic) Assignee: Balint Reczey (rbalint) => (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/1864045 Title: [SRU] Hibernation events sometimes missed on repeated attempts Status in acpid package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Status in acpid source package in Bionic: Incomplete Status in linux source package in Bionic: Incomplete Status in acpid source package in Eoan: Won't Fix Status in linux source package in Eoan: Won't Fix Bug description: When testing hibernation / resume on AWS with 5.0 or 5.3 kernels on bionic (using acpid 1:2.0.28-1ubuntu1), we sometimes see failure with repeated attempts. The first attempt will always be triggered, but the next attempt may not. The result is the agent never triggers the hibernation process and the instance will be forced to shutdown after a timeout period. Two workarounds have been identified. The first is to restart acpid during the resume handler. The second is to use the latest upstream acpid (as of Feb 1, 2020). This second workaround indicates there may be a patch missing in the acpid in bionic (1:2.0.28-1ubuntu1) to work with the 5.0+ kernels. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel on a bionic image with on-demand hibernation support enabled. 2) Hibernate and resume the instance, ensuring the system is fully resumed afterward and the swap file has been removed. 3) Hibernate and resume another time. The hibernate should be triggered immediately and the instance should become unresponsive as it saves state to disk. 4) Resume the instance, it should come back with the same processes running. 5) Repeat 3) - 4) as necessary. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: acpid 1:2.0.28-1ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpid/+bug/1864045/+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 1901350] Re: [Lenovo ThinkPad T450s] Touchpad stops working after sleep
I confirmed that this is still an issue on 21.04. No improvement. -- 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/1901350 Title: [Lenovo ThinkPad T450s] Touchpad stops working after sleep Status in linux package in Ubuntu: Confirmed Bug description: On Ubuntu 20.04 and 20.10, the touchpad stops working after sleep. Restarting with rmmod psmouse and modprobe psmouse is not working anymore, the touchpad reloads but with the wrong settings. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 24 13:42:39 2020 DistUpgraded: 2020-10-24 12:59:49,175 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo HD Graphics 5500 [17aa:5036] MachineType: LENOVO 20BWS1D61J ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-25-generic root=UUID=09cc0657-0a94-4a6c-9043-2df6132cd821 ro SourcePackage: xorg UpgradeStatus: Upgraded to groovy on 2020-10-24 (0 days ago) dmi.bios.date: 02/23/2019 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: JBET72WW (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BWS1D61J dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnLENOVO:bvrJBET72WW(1.36):bd02/23/2019:br1.36:efr1.4:svnLENOVO:pn20BWS1D61J:pvrThinkPadT450s:rvnLENOVO:rn20BWS1D61J:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450s dmi.product.name: 20BWS1D61J dmi.product.sku: LENOVO_MT_20BW_BU_Think_FM_ThinkPad T450s dmi.product.version: ThinkPad T450s 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.1-1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1 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/1901350/+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 1931767] [NEW] Ubuntu 20.04 freezes when I connect external monitor through USB-C
You have been subscribed to a public bug: When I connect an external monitor through USB-C my system freezes completely and the fans start spinning full speed and I can't do anything. It was working before but now all of the sudden it has stopped working. I used to be able to connect 2 extra external monitors (through HDMI and USB-C) *P.S. When I connect the monitor and then turn on the computer then it hangs at the splash loading screen.* Here is my setup: Laptop - Lenovo Legion 5 (1 HDMI port and 1 USB-C port) Intel i5 10th gen NVIDIA GeForce GTX 1650 (with NVIDIA proprietary driver installed) What I have tried so far but did not help `apt update && apt upgrade` ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 20.04 freezes when I connect external monitor through USB-C https://bugs.launchpad.net/bugs/1931767 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 1931767] Re: Ubuntu 20.04 freezes when I connect external monitor through USB-C
Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1931767 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 ** 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/1931767 Title: Ubuntu 20.04 freezes when I connect external monitor through USB-C Status in linux package in Ubuntu: New Bug description: When I connect an external monitor through USB-C my system freezes completely and the fans start spinning full speed and I can't do anything. It was working before but now all of the sudden it has stopped working. I used to be able to connect 2 extra external monitors (through HDMI and USB-C) *P.S. When I connect the monitor and then turn on the computer then it hangs at the splash loading screen.* Here is my setup: Laptop - Lenovo Legion 5 (1 HDMI port and 1 USB-C port) Intel i5 10th gen NVIDIA GeForce GTX 1650 (with NVIDIA proprietary driver installed) What I have tried so far but did not help `apt update && apt upgrade` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931767/+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 1931779] [NEW] kdump just hung out of the box
Public bug reported: I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04 system, installed specifically to try reproducing a bug. But when I tried, after kdump-config status reported "ready to dump" on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to console and then just hung forever. After some blind guessing and twiddling both variables, I found that crashkernel=512M-:256M works. ** Affects: makedumpfile (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1931779 Title: kdump just hung out of the box Status in makedumpfile package in Ubuntu: New Bug description: I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04 system, installed specifically to try reproducing a bug. But when I tried, after kdump-config status reported "ready to dump" on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to console and then just hung forever. After some blind guessing and twiddling both variables, I found that crashkernel=512M-:256M works. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1931779/+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 1931779] Re: kdump just hung out of the box
** Description changed: I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04 system, installed specifically to try reproducing a bug. But when I tried, after kdump-config status reported "ready to dump" on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to console and then just hung forever. After some blind guessing and twiddling both variables, I found that - crashkernel=512M-:256M works. + crashkernel=512M-:256M works on this particular setup. (MS7850 + motherboard, i5-4670 CPU, 5.4.0-42-generic kernel) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1931779 Title: kdump just hung out of the box Status in makedumpfile package in Ubuntu: New Bug description: I tried installing kdump-tools (1.6.7-1ubuntu2.2) on my up to date 20.04 system, installed specifically to try reproducing a bug. But when I tried, after kdump-config status reported "ready to dump" on reboot, echo 'c' | sudo tee /proc/sysrq-trigger, it printed the panic to console and then just hung forever. After some blind guessing and twiddling both variables, I found that crashkernel=512M-:256M works on this particular setup. (MS7850 motherboard, i5-4670 CPU, 5.4.0-42-generic kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1931779/+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
