[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop-5.4/5.4.0.1017.18~18.04.18)
All autopkgtests for the newly accepted linux-meta-gkeop-5.4 (5.4.0.1017.18~18.04.18) for bionic have finished running. The following regressions have been reported in tests triggered by the package: zfs-linux/0.7.5-1ubuntu16.11 (amd64) virtualbox/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) lxc/3.0.3-0ubuntu1~18.04.1 (amd64) virtualbox-hwe/5.2.42-dfsg-0~ubuntu1.18.04.1 (amd64) 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/bionic/update_excuses.html#linux-meta-gkeop-5.4 [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 1928700] Autopkgtest regression report (linux-base/4.5ubuntu1.6)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-oem-osp1/5.0.0-1071.77 (amd64) 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/bionic/update_excuses.html#linux-base [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-base in Ubuntu. https://bugs.launchpad.net/bugs/1928700 Title: new postinst hook requires initramfs-tools Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [SRU Justification] == Impact == The new postinst hook from bug 1877088 currently requires initramfs-tools installed, or installing a kernel would fail. This happens for me on a builder chroot trying to build linux-meta of a derivative kernel. == Fix == The fix would be to skip running the script if update-initramfs is not available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools script which has exactly that check at the beginning. == Testcase == Building linux-meta in a sbuild chroot which should again work without the messages about verifying links. Reinstalling a kernel on a system with update-initramfs existing should still print the messages. == Regression Potential == Systems with update-initramfs installed and initrd files might for some reason again fail to fix missing links. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1928700/+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 1877088] Autopkgtest regression report (linux-base/4.5ubuntu1.6)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-oem-osp1/5.0.0-1071.77 (amd64) 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/bionic/update_excuses.html#linux-base [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-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to:
[Kernel-packages] [Bug 1929255] Autopkgtest regression report (linux-base/4.5ubuntu1.6)
All autopkgtests for the newly accepted linux-base (4.5ubuntu1.6) for bionic have finished running. The following regressions have been reported in tests triggered by the package: linux-oem-osp1/5.0.0-1071.77 (amd64) 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/bionic/update_excuses.html#linux-base [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-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+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 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Hi Ted, You will need to enable -proposed to get this kernel, as described in https://wiki.ubuntu.com/Testing/EnableProposed from comment #27 You can turn this option off after the test. It should be 5.8.0-56.63 from proposed on Groovy. (The 5.8 proposed kernel is not ready for Focal yet, so you can either verify this on Groovy 5.8 or wait for the 5.8 proposed kernel on Focal) Thanks! ** Tags removed: 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/1926030 Title: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in focal package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Patch: * media: rc: fix timeout handling after switch to microsecond durations * media: rc: ite-cir: fix min_timeout calculation Were applied to Groovy with our stable update process (bug 1918516) User reported that IR Remote key press will be repeated for multiple times with these patches applied. Commit 528222d853f92 ("media: rc: harmonize infrared durations to microseconds") that needs to be fixed by these two does not exist in 5.8 kernel. The patch author Matthias Reichl also state these are for 5.10 and onward. [Fix] Revert these two patches for groovy. [Test] Test kernels for G-5.8 / F-5.8 can be found here: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ User Ted L confirmed that F-5.8 test kernel can fix the problem. [Where problems could occur] The chance to cause regression can be considered as low since the original patch that need to be fix by these two patches does not exist in 5.8 at all. [Original Bug Report] I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ted1020 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (217 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enp0s31f6 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) 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=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 RfKill: Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: H110T dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3
[Kernel-packages] [Bug 1913903] Re: package linux-firmware 1.190 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmwa
[Expired for linux-firmware (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1913903 Title: package linux-firmware 1.190 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb.dpkg-new': fin de fichero o de flujo inesperado Status in linux-firmware package in Ubuntu: Expired Bug description: acabo de reinstalar ubuntu 20,10 y al cargar del dc el sistema operativo me da estos errores ,cuando la imagen del sistema operativo esta bien , no se si sera a causa de las dos memiorias ram que le puse nuevas. ProblemType: Package DistroRelease: Ubuntu 20.10 Package: linux-firmware 1.190 ProcVersionSignature: Ubuntu 5.8.0-41.46-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bus 725 F pulseaudio CasperMD5CheckResult: skip Date: Sat Jan 30 20:10:43 2021 Dependencies: ErrorMessage: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb.dpkg-new': fin de fichero o de flujo inesperado InstallationDate: Installed on 2021-01-30 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) IwConfig: lono wireless extensions. enp1s1no wireless extensions. enp1s7no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/8p, 480M MachineType: To Be Filled By O.E.M. 775i945GZ PackageArchitecture: all ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=1efc7ec4-5022-4179-9396-17a37ffeaedc ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu35.2 RfKill: SourcePackage: linux-firmware Title: package linux-firmware 1.190 failed to install/upgrade: no se pudieron copiar los datos extraídos de './lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb' a '/lib/firmware/dpaa2/mc/mc_10.10.0_lx2160a.itb.dpkg-new': fin de fichero o de flujo inesperado UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/04/2006 dmi.bios.release: 8.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: 775i945GZ dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/04/2006:br8.12:svnToBeFilledByO.E.M.:pn775i945GZ:pvrToBeFilledByO.E.M.:rvn:rn775i945GZ:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: 775i945GZ dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1913903/+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 1929803] Re: CirrusLogic: The default input volume is "0%" on Dell Warlock
verified linux-oem-5.10 version 5.10.0-1030.31 from focal-proposed. ** 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/1929803 Title: CirrusLogic: The default input volume is "0%" on Dell Warlock Status in HWE Next: New 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: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] On some platforms with Cirrus CS8409 audio codec, DMIC volume default value in kernel driver is 0, which follows no audio sound will be played during installation and OOBE until being explicitly configured again via GNOME Settings GUI or other methods. [Fix] Commit 527ff9550682 ("ALSA: hda/cirrus: Set Initial DMIC volume to -26 dB") currently landed in upstream tiwai/sound.git is required to address this issue. It's a follow-up of commit 0e853a9c3937 ("ALSA: hda/cirrus: Set Initial DMIC volume for Bullseye to -26 dB"), which is applied in bug 1923557. [Test Case] Try to remove all the user space settings caches and reboot. The detailed steps are: # reboot to another system with access, e.g. livecd livecd$ sudo mount /dev/nvme0n1p3 /mnt livecd$ sudo rm /mnt/var/lib/alsa/asound.state livecd$ sudo rm -rf /mnt/home/u/.config/pulse livecd$ sudo reboot # reboot back The original status is like: $ amixer sget 'Internal Mic',0 Simple mixer control 'Internal Mic',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 63 Front Left: Capture 0 [0%] [-51.00dB] [off] Front Right: Capture 0 [0%] [-51.00dB] [off] Expect 40% in the front left/right capture volumes. $ amixer -c 1 sget 'Internal Mic',0 Simple mixer control 'Internal Mic',0 Capabilities: cvolume cswitch Capture channels: Front Left - Front Right Limits: Capture 0 - 63 Front Left: Capture 25 [40%] [-26.00dB] [on] Front Right: Capture 25 [40%] [-26.00dB] [on] [Where problems could occur] This gives the default value of Cirrus CS8409 audio codec capture volume. It was previously found on another platform, Bullseye, and fixed in bug 1923557, while latterly convinced being a common bug that should be fixed without the quirk. [Other Info] By SRU we skipped a couple of refactoring changes in asound upstream tree, so additional changes to the original patch are required to backport. On v5.12 and on, say unstable, the fix can be cleanly cherry-picked. == original bug report == This is a similar bug to bug 1923557, which happens on Dell Bullseye. The initial default input volume right after Ubuntu installation is set to 0% while 16% is expected. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1519 F pulseaudio /dev/snd/controlC0: u 1519 F pulseaudio CasperMD5CheckResult: skip DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-proposed-release+X114 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-26 (5 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Inspiron 15 3515 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1028-oem root=UUID=dcda93ce-c1ec-4c02-9098-31756821d54d ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1028.29-oem 5.10.35 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1028-oem N/A linux-backports-modules-5.10.0-1028-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1028-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/10/2021 dmi.bios.release: 5.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.0 dmi.board.asset.tag: not specified
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/4.15.0.1093.89)
All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1093.89) for bionic have finished running. The following regressions have been reported in tests triggered by the package: nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.18.04.1 (amd64) lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64) ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64) glibc/2.27-3ubuntu1.4 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.18.04.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.18.04.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) 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/bionic/update_excuses.html#linux-meta-kvm [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 1928242] Re: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle
** Tags removed: verification-needed-groovy verification-needed-hirsute ** Tags added: verification-done-groovy verification-done-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1928242 Title: Realtek USB hubs in Dell WD19SC/DC/TB fail to work after exiting s2idle Status in HWE Next: New 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: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Committed Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Bug description: [SRU Justification] [Impact] All of 3 different WD19(TB/SC/DC) docks have 3 Type-A ports and 2 Type-C ports, and there're highspeed Hubs(0bda:5487 and its substream hub 0bda:5413) and Superspeed Hubs (0bda:0487 and its downstream hub 0bda:0413). In the bug description below, we will refer the 2 highspeed hubs as Hub A and Hub A.3, and the 2 superspeed hubs as Hub B and Hub B.3. All devices connected via either Type-A or Type-C ports will connect to either Hub A.3 or Hub B.3. If we connect a wakup enabled device (keyboard) to a Type-A port, the Hub A.3 will fail to activate after exiting s2idle and all downstream devices will not be detected. If we have a superspeed device connected to other Type-A port in addition to the keyboard, this superspeed device actually connects to Hub B.3, and the Hub B.3 will also fails to work after exiting s2idle. If the wakeup enabled device connects via Type-C port, there's no such problem. As a summary, a wakeup enabled device connect to Type-A port will cause the failure of Hub A.3 and Hub B.3. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. [Fix] Before the resume failure, the upstream hub(Hub A or B) will hit the timeout problem while doing SetPortFeature(PORT_SUSPEND) to the port of the downstream hub (Hub A.3 or Hub B.3). However, the PORT_SUSPEND bit of the wPortStatus is actually turned on for the Hub A.3, we simply need to make the kernel believe it's already suspended. Then the ClearPortFeature will be done during resume and the problem will go away. The Hub B.3 will be tricky. The PORT_SUSPEND bit is not on after the suspend timeout, but it needs the ClearPortFeature(PORT_SUSPEND) for Hub B.3 to avoid resume failure. It doesn't comply with the USB spec so it's hard to create a generic fix for it. Because it only happens when timeout happens on suspending Hub A.3 and there's a superspeed device connecting to Type-A port, we choose to leave it as-is and try to address it in the future. [Test Case] 1. Make sure that the WD19 connects to the laptop 2. Connect USB keyboard/mouse to USB Type-A ports. 3. Suspend the system 4. Press the Enter key or power button to wake up the system 5. Check if the USB keyboard/mouse are still working Repeat 4 and 5 for > 10 times w/o losing any USB devices. [Where problems could occur] A wakeup enabled device (keyboard) connect to Type-A port will cause the failure of Hub A.3 and Hub B.3 during resume. Hub B.3 only fails when a wakeup enabled device and a superspeed device both connect via Type-A port. All devices connects to Hub A.3 (and B.3 if superspeed device connect via Type-A port) will be lost after resume. [Regression Potential] Minimum. The fix is only triggered when timeout happens during USB port suspend and it follows the standard USB protocol to do either resume or reset_resume. == Original Bug Description == ● Summary Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. Plug dock into SUT and check USB keyboard and mouse work. SUT enter suspend. After 1 min resume SUT, check USB keyboard/mouse function. Sometimes USB keyboard/mouse no function. Isolation: 1. VP on UMA and Discrete 2. When issue occur, both front and back port on WD19 can't work using USB keyboard/mouse but USB Key. ● Reproduce Steps 1.Plug in USB mouse and USB keyboard to WD19/WD19DC USB ports near LAN port. 2.Plug dock into SUT and check USB keyboard and mouse work. 3. SUT enter suspend. 4.After 1 min, resume SUT and check USB keyboard/mouse function. 5.Sometimes USB keyboard/mouse no function. ● Results ○ Expected Result USB mouse or keyboard on dock can use after suspend ○ Actual Result USB mouse or keyboard on dock sometimes no function after suspend ● Additional Information ○ Test Vault ID:60943.011 ○ SKU:Broadmoor Latitude5421 ○
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
Please try this version https://github.com/intel/thermal_daemon/tree/ubuntu-bug-1930422 checkout branch ubuntu-bug-1930422. Then repeat comments at #11 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet Lake PCH SMBus Controll /0/100/1f.5 busComet Lake PCH SPI Controller /0/1system
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
I see that this system doesn't have all expected table and has one default table which has just one entry. So need some special implementation. I will implement and send a branch to test. But keep in mind that limit is set at 71C. So I know there will be complaints that there is too much throttling also. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Your message to "upstream" seems fine. No I did not "do" anything to elicit those "timed out to flush queue 2" messages with the RC4 kernel. With the 5.13.0-5 kernel as built by Kai-Heng, I did not seem to get them anymore. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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
Ubuntu should revert it to older 460 for now. It's causing issues right now. -- 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: Confirmed Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed 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:26:57 willow kernel: RBP: 8e318220add0 R08:
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
I have sent the patch to upstream: https://lore.kernel.org/linux-wireless/20210607012254.6306-1-pks...@realtek.com/T/#u I add your description of this bug in the commit message. If there is anything wrong, please let me know. About the warnings "timed out to flush queue 2", my colleague told me he cannot see the symptom. It seems like you don't need special steps to reproduce it, right? If you have, please tell me the steps. Thank you. -- 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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+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 1931044] Re: SynPS/2 Synaptics TouchPad choppy movement after suspend
** Package changed: ubuntu => linux (Ubuntu) ** Tags added: 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/1931044 Title: SynPS/2 Synaptics TouchPad choppy movement after suspend Status in linux package in Ubuntu: New Bug description: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPad id=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Buttonid=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=9[slave keyboard (3)] ↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=13 [slave keyboard (3)] >> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04.2 LTS Release: 20.04 Codename: focal >> cat /proc/bus/input/devices ... I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931044/+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 1931044] [NEW] SynPS/2 Synaptics TouchPad choppy movement after suspend
You have been subscribed to a public bug: Sometimes touchpad input becomes very laggy. It seems to be related to suspending the laptop. I think it also has to do with other mice being plugged in/out. Often, suspending and waking up immediately afterwards makes the pointer fluent again. This is not the only problem I see with this touchpad/driver: Sometimes the pointer stops moving horizontally as if it got stuck in a scrolling gesture. Sometimes the pointer (almost) stops moving completely. Suspending often but not always helps. I am not sure whether these problems are related. I am happy to debug the problem, but I don't know where to start. >> xinput list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ SynPS/2 Synaptics TouchPadid=10 [slave pointer (2)] ⎜ ↳ TPPS/2 IBM TrackPoint id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Sleep Button id=8[slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=9[slave keyboard (3)] ↳ ThinkPad Extra Buttonsid=12 [slave keyboard (3)] ↳ Integrated Camera: Integrated C id=13 [slave keyboard (3)] >> lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.2 LTS Release:20.04 Codename: focal >> cat /proc/bus/input/devices ... I: Bus=0011 Vendor=0002 Product=0007 Version=01b1 N: Name="SynPS/2 Synaptics TouchPad" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=5 B: EV=b B: KEY=e520 1 0 0 0 0 B: ABS=66080001103 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- SynPS/2 Synaptics TouchPad choppy movement after suspend https://bugs.launchpad.net/bugs/1931044 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 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
** Tags added: oem-priority -- 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/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. 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 Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 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.8 dmi.modalias:
[Kernel-packages] [Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
Using the sha1 gave the same error (ce6471a4dff253eab89bd4eb3a84eef6bdba1f44 was both old and new) I built a new kernel (5.12.0+-1) using: cd linux git bisect start v5.13-rc2 v5.12-rc8 make olddefconfig make localmodconfig make -j`nproc` deb-pkg This kernel can correctly resume from suspend. The output from git bisect log is: # bad: [d07f6ca923ea0927a1024dfccafc5b53b61cfecc] Linux 5.13-rc2 # good: [bf05bf16c76bb44ab5156223e1e58e26dfe30a88] Linux 5.12-rc8 git bisect start 'v5.13-rc2' 'v5.12-rc8' # good: [35655ceb31b56cd1cb52635a725dfcdb9662d7b7] Merge tag 'clk-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux git bisect good 35655ceb31b56cd1cb52635a725dfcdb9662d7b7 I marked it as 'good' in the bisect log since it works, but should I have marked it as 'bad' since we are doing it in reverse? -- 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 1786013] Autopkgtest regression report (linux-meta-raspi/5.8.0.1026.29)
All autopkgtests for the newly accepted linux-meta-raspi (5.8.0.1026.29) for groovy have finished running. The following regressions have been reported in tests triggered by the package: wireguard-linux-compat/unknown (arm64) systemd/246.6-1ubuntu1.3 (arm64) v4l2loopback/0.12.5-1 (arm64) rtl8821ce/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/groovy/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
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
try this. ** Attachment added: "output.txt" https://bugs.launchpad.net/bugs/1930422/+attachment/5502846/+files/output.txt ** Attachment added: "Screenshot from 2021-06-06 20-19-08.png" https://bugs.launchpad.net/bugs/1930422/+attachment/5502847/+files/Screenshot%20from%202021-06-06%2020-19-08.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
There's a new testing patch out, please try this instead of the previously mentioned. https://bugzilla.kernel.org/show_bug.cgi?id=213031#c26 It cures the ACPI enumeration to enable the kbd. Nothing more, nothing less. -- 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/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+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
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
ok will do, just for reference this is a screenshot running thermald from ubuntu-20.04.2.0-desktop-amd64 doing prime number search with cpus and gpu runing at 84c 1802rpm will send another when i install https://github.com/intel/thermal_daemon again. On 06/06/2021 19:14, Srinivas Pandruvada wrote: https://github.com/intel/thermal_daemon > Again I don't see any throttling. > With the version from > https://github.com/intel/thermal_daemon > > Can you do > #systemctl disable thermald > reboot > > from a command line > #thermald --no-daemon --loglevel=debug --adaptive > > Attach the output > > Alternatively you can just add --loglevel=debug instead of loglevel=info > in thermald service file and collects log in journal > ** Attachment added: "Screenshot from 2021-06-06 20-02-50.png" https://bugs.launchpad.net/bugs/1930422/+attachment/5502845/+files/Screenshot%20from%202021-06-06%2020-02-50.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB
[Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
Again I don't see any throttling. With the version from https://github.com/intel/thermal_daemon Can you do #systemctl disable thermald reboot from a command line #thermald --no-daemon --loglevel=debug --adaptive Attach the output Alternatively you can just add --loglevel=debug instead of loglevel=info in thermald service file and collects log in journal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS
[Kernel-packages] [Bug 1931001] Re: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
** 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/1931001 Title: kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! Status in linux package in Ubuntu: New Bug description: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931001/+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 1931001] [NEW] kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s!
You have been subscribed to a public bug: Ubuntu 20.04 LTS and Ubuntu 21.04 occasionally boots with very bad performance and very unresponsive to user input on Lenovo laptop Lenovo 300e 2nd Gen 81M9 (LENOVO_MT_81M9_BU_idea_FM_300e 2nd G). When this happens you can read this kind of messages on journal: --- root@alumne-1-58:~# journalctl | grep "BUG: soft" may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 20 21:44:35 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [swapper/3:0] may 22 09:33:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [prometheus-node:4220] may 24 16:45:14 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 23s! [swapper/0:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 22s! [swapper/1:0] jun 03 00:01:09 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0] jun 03 00:02:15 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 21s! [swapper/0:0] jun 05 08:22:58 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [swapper/2:0] jun 05 08:25:06 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [lxd:3975] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [swapper/2:0] jun 05 08:26:42 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:27:38 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [irq/138-iwlwifi:1044] jun 05 08:28:34 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] jun 05 08:29:46 alumne-1-58 kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! [irq/138-iwlwifi:1044] root@alumne-1-58:~# --- Usually if you reboot everything works fine but it's very annoying when happens. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment kernel-bug -- kernel: watchdog: BUG: soft lockup - CPU#3 stuck for 22s! https://bugs.launchpad.net/bugs/1931001 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 1926030] Re: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
This test F-hwe-5.8 / G-5.8 kernel fixes the issue: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ The latest automatically updated kernel (5.8.0-55-generic) does not fix the issue. ** Also affects: focal (Ubuntu) Importance: Undecided Status: New ** No longer affects: focal (Ubuntu Groovy) ** Changed in: focal (Ubuntu) Status: New => Confirmed ** 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/1926030 Title: IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in focal package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Groovy: Fix Committed Bug description: [Impact] Patch: * media: rc: fix timeout handling after switch to microsecond durations * media: rc: ite-cir: fix min_timeout calculation Were applied to Groovy with our stable update process (bug 1918516) User reported that IR Remote key press will be repeated for multiple times with these patches applied. Commit 528222d853f92 ("media: rc: harmonize infrared durations to microseconds") that needs to be fixed by these two does not exist in 5.8 kernel. The patch author Matthias Reichl also state these are for 5.10 and onward. [Fix] Revert these two patches for groovy. [Test] Test kernels for G-5.8 / F-5.8 can be found here: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ User Ted L confirmed that F-5.8 test kernel can fix the problem. [Where problems could occur] The chance to cause regression can be considered as low since the original patch that need to be fix by these two patches does not exist in 5.8 at all. [Original Bug Report] I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ted1020 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-09-19 (217 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: lono wireless extensions. enp3s0no wireless extensions. enp0s31f6 no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) 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=529cae8e-19cd-4732-80d5-b3dca123afc6 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 RfKill: Tags: focal Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd mythtv plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/05/2017 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3405 dmi.board.asset.tag: Default string dmi.board.name: H110T dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3
[Kernel-packages] [Bug 1931021] [NEW] Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49
Public bug reported: The bug reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926030 affects Focal (20.04). I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 uname -r: 5.8.0-55-generic This test F-hwe-5.8 / G-5.8 kernel works: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 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/1931021 Title: Focal (20.04): IR Remote Keys Repeat Many Times Starting with Kernel 5.8.0-49 Status in linux package in Ubuntu: New Bug description: The bug reported at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926030 affects Focal (20.04). I use an IR remote with the ir-keytable package. Everything was working fine until kernel 5.8.0-49 was automatically installed by Software Updater on Ubuntu 20.04.2. When any key is pressed on the remote, the key is repeated about 500 times. The kernel is now 5.8.0-50, and the problem persists. Other users on the MythTV mailing list are reporting the issue, and it appears that the problem is related to changes in the following files: drivers/media/rc/ir-mce_kbd-decoder.c drivers/media/rc/rc-main.c b/drivers/media/rc/rc-main.c drivers/media/rc/serial_ir.c It has been reported that reverting the ir-mce_kbd-decoder.c and rc- main.c files to the older versions fixes the problem. /proc/version_signature > version.log: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 lspci -vnvn: 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1043:8694] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: skl_uncore ir-keytable -V: IR keytable control version 1.18.0 lsb_release -rd: Description: Ubuntu 20.04.2 LTS Release: 20.04 uname -r: 5.8.0-55-generic This test F-hwe-5.8 / G-5.8 kernel works: https://people.canonical.com/~phlin/kernel/lp-1926030-revert-for-ir/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931021/+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
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
spoke too soon. if i run cpus and gpu hard termp goes 94-100c fan 2800-3000 makes no fifference if i fresh boot or restart thermald while under stress; please see attached. hope this helps. ** Attachment added: "journalctl.boot" https://bugs.launchpad.net/bugs/1930422/+attachment/5502784/+files/journalctl.boot ** Attachment added: "journalctl.new" https://bugs.launchpad.net/bugs/1930422/+attachment/5502785/+files/journalctl.new -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
that seems to have fixed it. temp steady at ~90c fan 2200rpm. ta. please see attached. On 03/06/2021 16:01, Srinivas Pandruvada wrote: > Both logs looks same. I don't see any throttling. > This is a backported version of thermald in Ubuntu. > Can you run with upstream version of thermald > https://github.com/intel/thermal_daemon > ** Attachment added: "journalctl.txt" https://bugs.launchpad.net/bugs/1930422/+attachment/5502756/+files/journalctl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge
[Kernel-packages] [Bug 1930733] Re: Kernel oops with the 460.80 and 465.27 drivers when using DP, but not with HDMI
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-460 (Ubuntu) Status: New => Confirmed -- 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: Confirmed Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed 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:
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
exactly what happened to me, kept reinstalling 20.04.2 then decided to update apps in batches leaving thermald to last as it seemed must likely candidate. then i discovered Timeshift (old image restorer) save a lot of time! On 06/06/2021 01:20, Junjie Jin wrote: > I encountered the similar issue since 1.9.1-1ubuntu0.4 update. On the > previous version 1.9.1-1build1, if I run a CPU stress test, the fan will > keep going up until full speed (~6000rpm) as the temp rises. On > 1.9.1-1ubuntu0.4, the fan sometimes is kept at 3600rpm or remains at > zero. Once CPU reaches over ~90C, it got throttled down to min freq > 400MHz. I didn't know the problem was thermald until I reinstalled a > fresh Ubuntu 20.04.2, which worked perfectly, and then basically did a > binary search to find which package update caused the issue. To verify > it's really thermald 1.9.1-1ubuntu0.4, I reinstalled Ubuntu 20.04.2 > again, and the fan worked fine as expected, and then updated thermald > alone, and this issue happened. Then I downgraded thermald to the stock > version come with Ubuntu 20.04.2, the issue went away. > > lshw --short: > system Latitude 7400 (08E1) > /0 bus07WDVW > /0/0 memory 64KiB BIOS > /0/20memory 32GiB System Memory > /0/20/0 memory 16GiB SODIMM DDR4 > Synchronous 2667 MHz (0.4 ns) > /0/20/1 memory 16GiB SODIMM DDR4 > Synchronous 2667 MHz (0.4 ns) > /0/29memory 256KiB L1 cache > /0/2amemory 1MiB L2 cache > /0/2bmemory 8MiB L3 cache > /0/2cprocessor Intel(R) Core(TM) > i7-8665U CPU @ 1.90GHz > /0/100 bridge Coffee Lake HOST and DRAM > Controller > /0/100/2 displayUHD Graphics 620 (Whiskey > Lake) > /0/100/4 genericXeon E3-1200 v5/E3-1500 > v5/6th Gen Core Processor Thermal Subsystem > /0/100/8 genericXeon E3-1200 v5/v6 / > E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model > /0/100/12genericCannon Point-LP Thermal > Controller > /0/100/14busCannon Point-LP USB 3.1 > xHCI Controller > /0/100/14/0 usb1busxHCI Host Controller > /0/100/14/0/6multimedia Integrated_Webcam_HD > /0/100/14/0/8generic58200 > /0/100/14/0/acommunication Bluetooth wireless > interface > /0/100/14/1 usb2busxHCI Host Controller > /0/100/14.2 memory RAM memory > /0/100/14.3 wlo1networkCannon Point-LP CNVi > [Wireless-AC] > /0/100/15busCannon Point-LP Serial IO > I2C Controller #0 > /0/100/15.1 busCannon Point-LP Serial IO > I2C Controller #1 > /0/100/15.3 busIntel Corporation > /0/100/16communication Cannon Point-LP MEI > Controller #1 > /0/100/16.3 communication Cannon Point-LP Keyboard > and Text (KT) Redirection > /0/100/19busCannon Point-LP Serial IO > I2C Host Controller > /0/100/1cbridge Cannon Point-LP PCI > Express Root Port #5 > /0/100/1c/0 bridge JHL6340 Thunderbolt 3 > Bridge (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/0bridge JHL6340 Thunderbolt 3 > Bridge (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/0/0 genericJHL6340 Thunderbolt 3 NHI > (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/1bridge JHL6340 Thunderbolt 3 > Bridge (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/2bridge JHL6340 Thunderbolt 3 > Bridge (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/2/0 busJHL6340 Thunderbolt 3 USB > 3.1 Controller (C step) [Alpine Ridge 2C 2016] > /0/100/1c/0/2/0/0usb3busxHCI Host Controller > /0/100/1c/0/2/0/1usb4busxHCI Host Controller > /0/100/1dbridge Intel Corporation > /0/100/1d/0 genericRTS525A PCI Express Card > Reader > /0/100/1d.4 bridge Cannon Point-LP PCI > Express Root Port #13 > /0/100/1d.4/0storageSK hynix > /0/100/1d.4/0/0 /dev/nvme0
Re: [Kernel-packages] [Bug 1930422] Re: thermald_1.9.1-1ubuntu0.4_amd64 breaks system
yeah ok, soz i was half asleep when i replied. On 03/06/2021 16:01, Srinivas Pandruvada wrote: > Both logs looks same. I don't see any throttling. > This is a backported version of thermald in Ubuntu. > Can you run with upstream version of thermald > https://github.com/intel/thermal_daemon > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1930422 Title: thermald_1.9.1-1ubuntu0.4_amd64 breaks system Status in thermald package in Ubuntu: New Bug description: cpu runs at 100c fan at 3000rpm when in heavy use previous version was ok re: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1913186 lshw -short is: H/W path Device Class Description == system XPS 8940 (09C5) /0 bus0KV3RP /0/0memory 64KiB BIOS /0/9memory 16GiB System Memory /0/9/0 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/1 memory 8GiB DIMM DDR4 Synchronous 32 /0/9/2 memory Project-Id-Version: lshwRepor /0/9/3 memory Project-Id-Version: lshwRepor /0/35 memory 512KiB L1 cache /0/36 memory 2MiB L2 cache /0/37 memory 16MiB L3 cache /0/38 processor Intel(R) Core(TM) i7-10700 CP /0/100 bridge Intel Corporation /0/100/1bridge Xeon E3-1200 v5/E3-1500 v5/6t /0/100/1/0 displayTU106 [GeForce RTX 2060 Rev. /0/100/1/0.1multimedia TU106 High Definition Audio C /0/100/1/0.2busTU106 USB 3.1 Host Controller /0/100/1/0.2/0 usb3 busxHCI Host Controller /0/100/1/0.2/1 usb4 busxHCI Host Controller /0/100/1/0.3busTU106 USB Type-C UCSI Control /0/100/2displayIntel Corporation /0/100/4genericXeon E3-1200 v5/E3-1500 v5/6t /0/100/8genericXeon E3-1200 v5/v6 / E3-1500 /0/100/12 genericComet Lake PCH Thermal Contro /0/100/14 busComet Lake USB 3.1 xHCI Host /0/100/14/0usb1 busxHCI Host Controller /0/100/14/0/4 enx0c5b8f279a64 communication HUAWEI_MOBILE /0/100/14/0/5 input Dell MS116 USB Optical Mouse /0/100/14/0/6 input Dell KB216 Wired Keyboard /0/100/14/0/b genericUSB2.0-CRW /0/100/14/0/c genericUB91C /0/100/14/0/e communication Bluetooth wireless interface /0/100/14/1usb2 busxHCI Host Controller /0/100/14.2 memory RAM memory /0/100/14.3wlo1 networkWi-Fi 6 AX201 /0/100/15 busComet Lake PCH Serial IO I2C /0/100/16 communication Comet Lake HECI Controller /0/100/17 storageIntel Corporation /0/100/1b bridge Comet Lake PCI Express Root P /0/100/1b/0 storageSamsung Electronics Co Ltd /0/100/1b/0/0 /dev/nvme0 storagePM991 NVMe Samsung 512GB /0/100/1b/0/0/1/dev/nvme0n1 disk 512GB NVMe namespace /0/100/1b/0/0/1/1 volume 149MiB Windows FAT volume /0/100/1b/0/0/1/2 /dev/nvme0n1p2 volume 127MiB reserved partition /0/100/1b/0/0/1/3 /dev/nvme0n1p3 volume 214GiB Windows NTFS volume /0/100/1b/0/0/1/4 /dev/nvme0n1p4 volume 989MiB Windows NTFS volume /0/100/1b/0/0/1/5 /dev/nvme0n1p5 volume 16GiB Windows NTFS volume /0/100/1b/0/0/1/6 /dev/nvme0n1p6 volume 1417MiB Windows NTFS volume /0/100/1b/0/0/1/7 /dev/nvme0n1p7 volume 243GiB EXT4 volume /0/100/1c bridge Intel Corporation /0/100/1c/0enp3s0 networkRealtek Semiconductor Co., Lt /0/100/1f bridge Intel Corporation /0/100/1f.3 multimedia Comet Lake PCH cAVS /0/100/1f.4 busComet Lake PCH SMBus
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Like Hugo Ferreira, switching to the NVIDIA Server Driver instead of the classic NVIDIA driver finally did the job. Everything I tried before didn't work. So it is finally fixed for me, although I don't know if there are any drawbacks to using the Server driver :) -- 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/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O)