[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+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 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
I can confirm that this is now fixed for me on Ubuntu 18.04.4 LTS with kernel 5.3.0-46-generic. With this kernel, my Dell Latitude E5470 with a i5-6440HQ now consumes about 4W in idle instead of 9.W as before. Thanks a lot! -- 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/1853044 Title: 5.3.0-23-generic causes fans to spin when idle Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: "drm/i915/gen8+: Add RC6 CTX corruption WA" makes it effectively impossible to enter RC6 for some Intel GPUs when a display server is running. This results in increased energy usage and temperature. Fix: Upstream has changed too much to make the fixes there applicable, but Chris Wilson has provided a patch for 5.3, here: https://gitlab.freedesktop.org/drm/intel/issues/614#note_366057 Test Case: See test results below. On an affected machine powertop will show increased RC6 usage on an idle desktop after the patch, and other symptoms of excessive power use should also subside. Regression Potential: The 5.3 patch is pretty straightforward, and only adds running of an existing delayed worker to retire GPU requests. No regressions have been reported in testing so far. --- After upgrading to 5.3.0-23-generic the fans in my machine don't stop running. They always sound like something is utilizing CPU - even with no applications running after boot. If I boot back to 5.3.0-19-generic it's fine. My microcode version is reported as 0xd4 and iucode-tool reports: iucode-tool: system has processor(s) with signature 0x000506e3 Let me know if you need anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: dean 2898 F pulseaudio /dev/snd/pcmC2D0p: dean 2898 F...m pulseaudio /dev/snd/controlC0: dean 2898 F pulseaudio /dev/snd/controlC1: dean 2898 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:03:34 2019 HibernationDevice: RESUME=UUID=55a42c82-50bf-4e75-a133-dbd3aa93611b InstallationDate: Installed on 2018-07-24 (482 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-07-19 (121 days ago) dmi.bios.date: 05/16/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629 dmi.board.name: NUC6i7KYB dmi.board.vendor: Intel Corporation dmi.board.version: H90766-406 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853044/+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 1864288] Re: No boot after an update.
I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 However they may not be able to help you, as your description reads as more hardware related (did you run memtest, do a cap-check of your motherboard or other steps etc), and thus other hardware support sites maybe more on-topic. If it doesn't get as far as loading grub (the boot loader) as indicated in your description, then the kernel hasn't been loaded & kernel upgrades aren't an issue (as they aren't loaded being loaded by grub), ie. you have support issues). -- 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/1864288 Title: No boot after an update. Status in linux package in Ubuntu: Incomplete Bug description: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. It might be of some significance to know that my Assus VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 8GB, it reports 12GB of RAM. I no longer had the patience to test if this would happen with the old 4GB module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rada 1170 F pulseaudio /dev/snd/controlC0: rada 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.302:bd03/08/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rada 1170 F pulseaudio /dev/snd/controlC0: rada 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA
[Kernel-packages] [Bug 1862669] Re: wifi and bluetooth problem hp probook 4520s, chipset rt3090
Unload btusb and see if it helps. -- 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/1862669 Title: wifi and bluetooth problem hp probook 4520s, chipset rt3090 Status in linux package in Ubuntu: Expired Bug description: with the rt3090 wifi chip there is a conflict, which makes the wifi extremely slow, the bluetooth cannot be deactivated independent of the wifi and does not detect devices. I tried many methods to fix it, but I definitely think it's the kernel --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horacio1707 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-09 (3 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Hewlett-Packard HP ProBook 4520s Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=766b6c57-4110-40d6-a8f1-2d236a3e2188 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 Tags: tricia Uname: Linux 4.15.0-76-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.61 dmi.board.name: 1413 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.37:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4520s dmi.sys.vendor: Hewlett-Packard --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: horacio1707 F pulseaudio CurrentDesktop: XFCE DistroRelease: Linux Mint 19.3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-02-09 (3 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Hewlett-Packard HP ProBook 4520s Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=766b6c57-4110-40d6-a8f1-2d236a3e2188 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 Tags: tricia Uname: Linux 4.15.0-76-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68AZZ Ver. F.61 dmi.board.name: 1413 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 57.37 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68AZZVer.F.61:bd04/25/2016:svnHewlett-Packard:pnHPProBook4520s:pvr:rvnHewlett-Packard:rn1413:rvrKBCVersion57.37:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP ProBook 4520s dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862669/+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 1868134] Re: Headphones Audio Out Not Delivering Sound
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1868134 Title: Headphones Audio Out Not Delivering Sound Status in linux package in Ubuntu: Fix Released Bug description: DELL M5510 ~ $ cat /proc/asound/cards 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0xddc28000 irq 128 4.15.0-91 Exhibits no sound via headphones 4.15.0-88 No issue with sound via headphones *** Collecting problem information The collected information can be sent to the developers to improve the application. This might take a few minutes. *** Problem in linux-image-4.15.0-88-generic The problem cannot be reported: This is not an official Linux package. Please remove any third party package and try again. Press any key to continue... ^C ~ $ cat /proc/version_signature > version.log ~ $ sudo lspci -vnvn > lspci-vnvn.log [sudo] password: ~ $ Not sure why the above commands are not creating the required info. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868134/+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 1870816] Re: received update then got stuck on blackscreen in login screen. Changed "qiuet splash" to "radeon.modeset=0" in order to boot normally.
Can you please test previous kernel versions? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870816 Title: received update then got stuck on blackscreen in login screen. Changed "qiuet splash" to "radeon.modeset=0" in order to boot normally. Status in linux package in Ubuntu: Incomplete Bug description: I received an update yesterday 3/4/2020 that had important security and kernel updates, so I launched it as I usually do with any security or kernel updates I receive. It downloaded and installed the necessary files and requested a restart. I restarted and kept receiving a black screen with only my mouse visible on the login screen and nothing I tried worked until I went to Grub and pressed "e" then changed the "qiuet splash" to "radeon.modeset=0" (since my graphics card is ATI Radeon) in order to boot normally. And it worked! But that means that there's a bug in the latest update release and I don't like to change in the system files in order to boot my laptop. So please fix and let me know when can I revert back what I did and login normally without the change I made. Thank you Version: Ubuntu 19.10 GNOME: 3.34.2 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15.4 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 Uname: Linux 5.3.0-45-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:06:55 2020 InstallationDate: Installed on 2020-03-11 (24 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-04-04 08:56:31.608736 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870816/+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 1872758] Re: System doesn't wake up after suspend on HP Pavillon 15-CS1022NL
Can you please attach `journalctl -b -1 -k` after the issue happened. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872758 Title: System doesn't wake up after suspend on HP Pavillon 15-CS1022NL Status in linux package in Ubuntu: Incomplete Bug description: 1) lsb_release -rd Description: Ubuntu 18.04.4 LTS Release: 18.04 2) I think the bug is in the Kernel 5.3.0-46: apt-cache policy linux-headers-5.3.0-46-generic linux-headers-5.3.0-46-generic: Installato: 5.3.0-46.38~18.04.1 Candidato: 5.3.0-46.38~18.04.1 Tabella versione: *** 5.3.0-46.38~18.04.1 500 500 http://it.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 3) When I wake up the laptop from suspension the laptop wakes up correctly. 4) When I wake up the laptop from suspension the laptop doesn't wake up: I can hear the fans and I can see the keyboard backlight (and Power light) on but the screen is black. Furthermore I tried different Kernels and almost each version has the same problem. The first one which doesn't have this bug is the 4.18.20-041820-generic version. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-46-generic 5.3.0-46.38~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CurrentDesktop: communitheme:ubuntu:GNOME Date: Tue Apr 14 17:30:12 2020 InstallationDate: Installed on 2020-02-24 (49 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872758/+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 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Please test this kernel: https://people.canonical.com/~khfeng/lp1872984-2/ Which disables L0s. -- 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/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error occurs when attempting to turn
[Kernel-packages] [Bug 1856392] Re: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected
Please test latest 20.04. SoF DMIC should work now. -- 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/1856392 Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Microphone not detected Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello, on a brand new HPZbook15G6, with a fresh dual boot 19.10 Ubuntu install, I have no internal mic detected. The GNOME settings sound entry list is empty. Speaker sound is working properly. When hooking a microphone enabled headphone on the jack plug, the headphones mic is then detected, but there is now no sound output on the headphone. I've been looking for a few similar issues on recent (HP or not) laptops and found a few similar issues : Bug #1523100 Bug #1837821 so I guess this is a generic alsa or snd-hda-intel issue with newer ALC2xx hardware. I already tryed quite a few of the workaroubds/fix available here and there (e.g. overriding pin with hdajackretask, adding options to snd-hda-intel module etc. none with success) I'm available to test/provide any additional needed data. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mathieu1719 F pulseaudio /dev/snd/controlC0: mathieu1719 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 13:33:14 2019 InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interne - HDA Intel PCH Symptom_Jack: Black Mic, Right Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH successful Symptom_Type: Only some of inputs are working Title: [HP ZBook 15 G6, Realtek ALC285, Black Mic, Right] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.03.04 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.asset.tag: 5CD944676Z dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.03.04:bd11/06/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6VD99AV dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-14T13:26:02.404591 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856392/+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 1852071] Re: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kai-Heng Feng (kaihengfeng) ** Changed in: linux (Ubuntu) Status: Confirmed => Triaged -- 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/1852071 Title: [HP ZBook Studio G5, Ubuntu 18.04.3 LTS] Brightness function keys works as microphone mute function keys Status in linux package in Ubuntu: Triaged Bug description: 1. Press fn+F3. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness down. 2. Press fn+F3 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness down. 1. Press fn+F4. Ubuntu shows "Internal microphone" turned off OSD pop-up. Should turn the brightness up. 2. Press fn+F4 again. Ubuntu shows "Internal microphone" turned on OSD pop-up. Should turn the brightness up. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21 Uname: Linux 5.0.0-32-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Nov 11 13:23:56 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:8428] InstallationDate: Installed on 2019-04-02 (223 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 138a:00ab Validity Sensors, Inc. Bus 001 Device 002: ID 05c8:0808 Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ZBook Studio G5 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-32-generic root=UUID=d12790df-696c-4d0c-aefa-b0e53712e2ce ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: HP dmi.bios.version: Q71 Ver. 01.08.00 dmi.board.name: 8427 dmi.board.vendor: HP dmi.board.version: KBC Version 16.3A.00 dmi.chassis.asset.tag: 5CD91018X5 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrQ71Ver.01.08.00:bd07/15/2019:svnHP:pnHPZBookStudioG5:pvr:rvnHP:rn8427:rvrKBCVersion16.3A.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook Studio dmi.product.name: HP ZBook Studio G5 dmi.product.sku: 2YN61AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852071/+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 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859979 Title: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing Status in linux package in Ubuntu: Expired Bug description: With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a "BUG: kernel NULL pointer dereference, address: 00a8" some half a minute from boot. Before that, one can log in to the system (/home is on a nilfs2 filesystem), but after the kernel BUG report, any write to a nilfs2 filesystem freezes the process trying to write, or any new login attempt freezes. This bug can be reproduced with every boot. With linux-image-5.3.0-24-lowlatency and earlier, this doesn't happen. Relevant excerpt from syslog: ... Jan 16 10:56:59 lillukka kernel: [0.00] Linux version 5.3.0-26-lowlatency (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP PREEMPT Wed Dec 18 06:21:38 UTC 2019 (Ubuntu 5.3.0-26.28-lowlatency 5.3.13) ... Jan 16 10:57:13 lillukka kernel: [ 28.727753] BUG: kernel NULL pointer dereference, address: 00a8 Jan 16 10:57:13 lillukka kernel: [ 28.727852] #PF: supervisor read access in kernel mode Jan 16 10:57:13 lillukka kernel: [ 28.727914] #PF: error_code(0x) - not-present page Jan 16 10:57:13 lillukka kernel: [ 28.727974] PGD 0 P4D 0 Jan 16 10:57:13 lillukka kernel: [ 28.728012] Oops: [#1] PREEMPT SMP PTI Jan 16 10:57:13 lillukka kernel: [ 28.728067] CPU: 3 PID: 838 Comm: segctord Not tainted 5.3.0-26-lowlatency #28-Ubuntu Jan 16 10:57:13 lillukka kernel: [ 28.728156] Hardware name: Sony Corporation SVP1321C5E/VAIO, BIOS R0280V7 07/11/2013 Jan 16 10:57:13 lillukka kernel: [ 28.728257] RIP: 0010:percpu_counter_add_batch+0x13/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.728334] Code: e0 41 5c 41 5d 41 5e 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 e5 41 55 41 54 49 89 fc 53 65 ff 05 b5 5c ed 72 <48> 8b 47 20 48 63 ca 65 44 8b 28 49 63 dd 48 01 f3 48 39 d9 7e 0a Jan 16 10:57:13 lillukka kernel: [ 28.728536] RSP: 0018:b582c02afcb0 EFLAGS: 00010082 Jan 16 10:57:13 lillukka kernel: [ 28.728598] RAX: 0002 RBX: RCX: 0001 Jan 16 10:57:13 lillukka kernel: [ 28.728679] RDX: 0018 RSI: 0001 RDI: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728760] RBP: b582c02afcc8 R08: 8f519357ab40 R09: 0018 Jan 16 10:57:13 lillukka kernel: [ 28.728841] R10: 00030140 R11: 8f5193609eea R12: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728920] R13: 8f518a3ee498 R14: 8f518a3ee608 R15: e52b07e5a200 Jan 16 10:57:13 lillukka kernel: [ 28.729001] FS: () GS:8f519798() knlGS: Jan 16 10:57:13 lillukka kernel: [ 28.729091] CS: 0010 DS: ES: CR0: 80050033 Jan 16 10:57:13 lillukka kernel: [ 28.729157] CR2: 00a8 CR3: 8d60a002 CR4: 001606e0 Jan 16 10:57:13 lillukka kernel: [ 28.729237] Call Trace: Jan 16 10:57:13 lillukka kernel: [ 28.729280] __test_set_page_writeback+0x2f1/0x310 Jan 16 10:57:13 lillukka kernel: [ 28.729362] nilfs_segctor_do_construct+0xd13/0x1260 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729432] ? __switch_to_asm+0x40/0x70 Jan 16 10:57:13 lillukka kernel: [ 28.729496] nilfs_segctor_construct+0x1ff/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729572] nilfs_segctor_thread+0x136/0x3a0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729640] kthread+0x104/0x140 Jan 16 10:57:13 lillukka kernel: [ 28.729690] ? nilfs_segctor_construct+0x2f0/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729760] ? kthread_park+0x80/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.729807] ret_from_fork+0x35/0x40 Jan 16 10:57:13 lillukka kernel: [ 28.729854] Modules linked in: ccm rfcomm aufs overlay cmac bnep nilfs2 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel pn544_mei mei_phy pn544 snd_hda_codec hci snd_hda_core snd_hwdep intel_rapl_msr mei_hdcp nfc snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp iwlmvm mac80211 snd_seq btusb btrtl libarc4 btbcm uvcvideo btintel kvm videobuf2_vmalloc iwlwifi videobuf2_memops bluetooth snd_seq_device videobuf2_v4l2 videobuf2_common irqbypass joydev input_leds intel_cstate videodev ecdh_generic snd_timer intel_rapl_perf ecc serio_raw mc mei_me cfg80211 mei snd soundcore sony_laptop mac_hid intel_smartconnect sch_fq_codel cuse
[Kernel-packages] [Bug 1861219] Re: QLogic FC paths added when issue_lip
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/ Particularly, commit 3c75ad1d87c7d277c6174051b98757fe981d592d Author: Himanshu Madhani Date: Tue Dec 17 14:06:04 2019 -0800 scsi: qla2xxx: Remove defer flag to indicate immeadiate port loss ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861219 Title: QLogic FC paths added when issue_lip Status in linux package in Ubuntu: Incomplete Bug description: My QLogic direct-connect SANboot host with Ubuntu Server 18.04 LTS is seeing paths added during testing. Specifically added when running the command below: echo 1 > /sys/class/fc_host/host15/issue_lip There should be four paths total but if I run the command above five times, I will see nine total paths. The server will hang and require a reboot eventually as multiple hung_task_timeout errors show up in logs. Information on HBAs below: root@ICTM1607S02H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2742 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k QLE2692 FW:v8.08.231 DVR:v10.00.00.02-k An example of what a volume looks like in multipath -ll after the issue_lip occurs: root@ICTM1607S02H4:~# multipath -ll 36d039ea0003ebb14009e58b1fabf dm-3 NETAPP,INF-01-00 size=160G features='3 queue_if_no_path pg_init_retries 50' hwhandler='1 alua' wp=rw |-+- policy='service-time 0' prio=50 status=active | |- 13:0:0:0 sdl 8:176 active ready running | |- 15:0:0:0 sdq 65:0 active ready running | `- 15:0:1:0 sdv 65:80 active ready running `-+- policy='service-time 0' prio=10 status=enabled |- 12:0:0:0 sdb 8:16 active ready running `- 14:0:0:0 sdc 8:32 active ready running Notice how a path is added after issue_lip. 1) version_signature.log Ubuntu 4.15.0-74.84-generic 4.15.18 2) lspci -vnvn output is in a file attached. root@ICTM1607S02H4:~# lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 root@ICTM1607S02H4:~# apt-cache policy linux-image-generic linux-image-generic: Installed: 4.15.0.74.76 Candidate: 4.15.0.74.76 Version table: *** 4.15.0.74.76 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-updates/main amd64 Packages 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic-security/main amd64 Packages 100 /var/lib/dpkg/status 4.15.0.20.23 500 500 http://repomirror-ict.eng.netapp.com/ubuntu bionic/main amd64 Packages I expected the bus reset to quickly add and remove, but it seems removal is not happening. The number of paths grow after each bus reset causing instability with the OS. I have attached logs.zip which contains four files. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861219/+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 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: network-manager (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Incomplete Status in network-manager package in Ubuntu: Invalid Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+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 1862723] Re: 18.04 can't auto load ib_uverbs (18.04.3 hwe can) for Mellanox PMD nics
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862723 Title: 18.04 can't auto load ib_uverbs (18.04.3 hwe can) for Mellanox PMD nics Status in linux package in Ubuntu: Expired Bug description: 18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD ( 18.04.3 hwe can auto load via model depends) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862723/+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 1863086] Re: unkillable process (kernel NULL pointer dereference)
Sudip Mukherjee made a more elegant fix than I did, and he posted it to the fsdevel mailing list: https://lore.kernel.org/linux- fsdevel/20200416194612.21418-1-sudipm.mukher...@gmail.com/ I got an email saying that this has now been pulled into the -mm tree. I will update when this patch reaches mainline. After that, I will backport it to the Ubuntu kernels. -- 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/1863086 Title: unkillable process (kernel NULL pointer dereference) Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: If process that listens socket on any port crashes (segmentation fault) it becomes unkillable. Kill command does not kill this process. Port that listen crashed process never be freed. journalctl shows error: Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000] Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 0020 Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0 Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G OE 5.3.0-29-generic #31-Ubuntu Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: 9d4b76995100 RCX: 1afc Feb 13 13:28:09 vbun04 kernel: RDX: RSI: b464c2c5fc68 RDI: Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: b464c2c5fbe0 Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11: R12: 9d4b7b3df540 Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14: R15: b9f15920 Feb 13 13:28:09 vbun04 kernel: FS: 7f6c91911540() GS:9d4b7db0() knlGS: Feb 13 13:28:09 vbun04 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 000606e0 Feb 13 13:28:09 vbun04 kernel: Call Trace: Feb 13 13:28:09 vbun04 kernel: ? wake_up_state+0x10/0x20 Feb 13 13:28:09 vbun04 kernel: ? __send_signal+0x1eb/0x3f0 Feb 13 13:28:09 vbun04 kernel: get_signal+0x159/0x880 Feb 13 13:28:09 vbun04 kernel: do_signal+0x34/0x280 Feb 13 13:28:09 vbun04 kernel: ? bad_area+0x47/0x50 Feb 13 13:28:09 vbun04 kernel: exit_to_usermode_loop+0xbf/0x160 Feb 13 13:28:09 vbun04 kernel: prepare_exit_to_usermode+0x77/0xa0 Feb 13 13:28:09 vbun04 kernel: retint_user+0x8/0x8 Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: RCX: 7f6c918424eb Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 0003 Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08: R09: 7f6c919331f0 Feb 13 13:28:09 vbun04 kernel: R10: R11: 0217 R12: 55ec3a6bf150 Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14: R15: Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a Feb 13 13:28:09 vbun04 kernel: CR2: 0020 Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]--- Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b
[Kernel-packages] [Bug 1864288] Re: No boot after an update.
If it can't even reach GRUB, is it a bug to Linux kernel? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864288 Title: No boot after an update. Status in linux package in Ubuntu: Incomplete Bug description: After an update, my computer will no longer boot. I only see a black screen. No grub menu. After a couple of forced restarts, the file system gets corrupt. This happens both on XUbuntu 18.04.4 and 19.10. I am not sure if it had something to do with RAM upgrade or was it just a coincidence that I replaced a 4GB RAM module for an 8GB module and the next day my computer would not boot after an update. With clean install to any version everything works fine. It might be of some significance to know that my Assus VivoBook with Ryzen3 CPU has 4GB somewhere embedded and a separate 4GB module in the SODIMM slot, so it reports 8GB of RAM. After upgrading the RAM module to 8GB, it reports 12GB of RAM. I no longer had the patience to test if this would happen with the old 4GB module. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 [origin: unknown] ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: XFCE Date: Sat Feb 22 10:57:29 2020 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-update UpgradeStatus: No upgrade log present (fresh install) as update crashes. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rada 1170 F pulseaudio /dev/snd/controlC0: rada 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X512DA.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X512DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX512DA.302:bd03/08/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX512DA_X512DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX512DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X512DA_X512DA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: rada 1170 F pulseaudio /dev/snd/controlC0: rada 1170 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-22 (0 days ago) InstallationMedia: Xubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X512DA_X512DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic root=UUID=8beff811-d0c3-4481-97d4-7ca7073f066b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 RelatedPackageVersions: linux-restricted-modules-5.3.0-28-generic N/A linux-backports-modules-5.3.0-28-generic N/A linux-firmware1.173.14 Tags: bionic Uname: Linux 5.3.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/08/2019 dmi.bios.vendor: American Megatrends Inc.
[Kernel-packages] [Bug 1872375] Re: AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/ Particularly, to test the commit: commit 487eca11a321ef33bcf4ca5adb3c0c4954db1b58 Author: Prike Liang Date: Tue Apr 7 20:21:26 2020 +0800 drm/amdgpu: fix gfx hang during suspend with video playback (v2) ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872375 Title: AMDGPU driver crashes when resuming from sleep if a ffmpeg-vaapi encoding backend is being used Status in linux package in Ubuntu: Incomplete Bug description: Good morning, I'm writing this because is pretty much easily reproduceable in this hardware I discovered this when I set up an automatic permanent replay- recording in OBS, using FFMPEG VAAPI backend I usually put the system to sleep, and pretty much 100% of the times so far when OBS is recording something AND is using the ffmpeg-vaapi backend, putting the system to sleep and then waking it back, causes the amdgpu driver to crash no matter what Any other sleep/standby test made without recording using ffmpeg-vaapi (even using default ffmpeg software x264 backend) has not made the driver crash so far My setup: CPU: AMD Ryzen 5 1600 GPU: AMD Sapphire RX 580 8GB RAM: 12GB DDR4 (3x4GB) System: Ubuntu 20.04 Focal Fossa Desktop: GNOME 3.36.1 Kernel: 5.4.0-21-generic #25-Ubuntu Display server: X.org Here is the system crashing logs dmesg (Don't mind the hostname, it's a desktop PC not a thinkpad) Apr 13 01:49:02 haru-ThinkPad-T440s kernel: [ 64.100393] PM: suspend entry (deep) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108441] Filesystems sync: 0.008 seconds Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.108716] Freezing user space processes ... (elapsed 0.002 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111290] OOM killer disabled. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.111291] Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.112125] printk: Suspending console(s) (use no_console_suspend to debug) Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113085] serial 00:04: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.113317] parport_pc 00:03: disabled Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151545] sd 0:0:0:0: [sda] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151713] sd 1:0:0:0: [sdc] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151720] sd 10:0:0:0: [sdd] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151724] sd 11:0:0:0: [sdb] Synchronizing SCSI cache Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.151807] sd 0:0:0:0: [sda] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.152043] sd 1:0:0:0: [sdc] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.157544] sd 10:0:0:0: [sdd] Stopping disk Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.612461] ACPI: Preparing to enter system sleep state S3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925094] PM: Saving platform NVS memory Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.925117] Disabling non-boot CPUs ... Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.927049] smpboot: CPU 1 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.931788] smpboot: CPU 2 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.934941] IRQ 37: no longer affine to CPU3 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.935968] smpboot: CPU 3 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.940098] smpboot: CPU 4 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943503] IRQ 27: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.943510] IRQ 28: no longer affine to CPU5 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.944533] smpboot: CPU 5 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.947662] IRQ 44: no longer affine to CPU6 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.948697] smpboot: CPU 6 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.952180] IRQ 30: no longer affine to CPU7 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.953216] smpboot: CPU 7 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.957820] smpboot: CPU 8 is now offline Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961177] IRQ 39: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.961187] IRQ 63: no longer affine to CPU9 Apr 13 01:49:08 haru-ThinkPad-T440s kernel: [ 64.962201] smpboot: CPU 9 is now offline Apr 13 01:49:08
[Kernel-packages] [Bug 1870265] Re: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0000000000000040
Can you please test 5.4.0-24? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870265 Title: Intel GPU causes BUG: kernel NULL pointer dereference, address: 0040 Status in linux package in Ubuntu: Incomplete Bug description: After playing Gurumin: A Monstrous Adventure for some time, the system crashed in an unrecoverable way. REISUB was required to get some logs. This crash happened with default Ubuntu's kernel, default Mesa and default Xorg session. I never observed a crash this serious using the intel Xorg driver. However, using the default (modesetting), the following unrecoverable crash happened after two hours: The syslog contains the following: Apr 2 00:39:02 Lenovo-ideapad-310-14ISK systemd[1]: Starting Clean php session files... Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: phpsessionclean.service: Succeeded. Apr 2 00:39:03 Lenovo-ideapad-310-14ISK systemd[1]: Finished Clean php session files. Apr 2 00:56:59 Lenovo-ideapad-310-14ISK wpa_supplicant[1083]: wlp2s0: WPA: Group rekeying completed with 18:d6:c7:ee:b0:90 [GTK=CCMP] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284307] BUG: kernel NULL pointer dereference, address: 0040 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284314] #PF: supervisor read access in kernel mode Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284316] #PF: error_code(0x) - not-present page Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284321] PGD 0 P4D 0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284325] Oops: [#1] SMP PTI Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284330] CPU: 1 PID: 200385 Comm: xfwm4 Tainted: P O 5.4.0-21-generic #25-Ubuntu Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284331] Hardware name: LENOVO 80UG/Toronto 4A2, BIOS 0XCN45WW 08/09/2018 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284399] RIP: 0010:i915_active_acquire+0xe/0x80 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284403] Code: 00 48 c7 c6 a5 4e 6f c0 e8 af 07 93 e5 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 66 90 0f 1f 44 00 00 55 48 89 e5 41 55 41 54 53 <8b> 47 38 48 89 fb 85 c0 74 17 8d 50 01 f0 0f b1 53 38 75 f2 45 31 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284405] RSP: 0018:bd8446f979c8 EFLAGS: 00010286 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284408] RAX: RBX: 9c477afaca80 RCX: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284409] RDX: 9c4633bfc500 RSI: 9c477afaca80 RDI: 0008 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284411] RBP: bd8446f979e0 R08: 9c47d6f4dc28 R09: 9c47d6f4dc20 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284413] R10: 00014000 R11: 9c47d1918b00 R12: 9c4633bfc500 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284414] R13: 0008 R14: 9c4633bfc500 R15: 9c47d6f4db00 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284417] FS: 7f99a3564a80() GS:9c47de28() knlGS: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284419] CS: 0010 DS: ES: CR0: 80050033 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284420] CR2: 0040 CR3: 000556ca0001 CR4: 003606e0 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284421] DR0: DR1: DR2: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284422] DR3: DR6: fffe0ff0 DR7: 0400 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284423] Call Trace: Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284477] i915_active_ref+0x24/0x200 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284521] i915_vma_move_to_active+0x74/0xf0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284564] eb_submit+0xff/0x440 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284608] i915_gem_do_execbuffer+0x88e/0xc20 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284615] ? sock_def_readable+0x40/0x70 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284618] ? __kmalloc_node+0x205/0x320 Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284668] i915_gem_execbuffer2_ioctl+0x2c3/0x3d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284717] ? i915_gem_execbuffer_ioctl+0x2d0/0x2d0 [i915] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel: [16231.284742] drm_ioctl_kernel+0xae/0xf0 [drm] Apr 2 00:58:56 Lenovo-ideapad-310-14ISK kernel:
[Kernel-packages] [Bug 1872817] Re: Workqueue: events dp_altmode_work [typec_displayport]
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/ -- 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/1872817 Title: Workqueue: events dp_altmode_work [typec_displayport] Status in linux package in Ubuntu: Confirmed Bug description: After rebooting the following was present in dmesg: [ 242.931199] INFO: task kworker/6:2:174 blocked for more than 120 seconds. [ 242.931210] Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 242.931214] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.931218] kworker/6:2 D0 174 2 0x80004000 [ 242.931239] Workqueue: events dp_altmode_work [typec_displayport] [ 242.931243] Call Trace: [ 242.931260] __schedule+0x2e3/0x740 [ 242.931270] schedule+0x42/0xb0 [ 242.931278] schedule_preempt_disabled+0xe/0x10 [ 242.931282] __mutex_lock.isra.0+0x182/0x4f0 [ 242.931288] ? __switch_to_asm+0x34/0x70 [ 242.931291] ? __switch_to_asm+0x34/0x70 [ 242.931295] ? __switch_to_asm+0x40/0x70 [ 242.931299] ? __switch_to_asm+0x40/0x70 [ 242.931302] __mutex_lock_slowpath+0x13/0x20 [ 242.931305] mutex_lock+0x2e/0x40 [ 242.931315] ucsi_send_command+0x2a/0x60 [typec_ucsi] [ 242.931323] ucsi_displayport_enter+0x90/0x180 [typec_ucsi] [ 242.931334] typec_altmode_enter+0x4f/0x60 [typec] [ 242.931339] dp_altmode_work+0xde/0xf0 [typec_displayport] [ 242.931346] process_one_work+0x1eb/0x3b0 [ 242.931352] worker_thread+0x4d/0x400 [ 242.931357] kthread+0x104/0x140 [ 242.931362] ? process_one_work+0x3b0/0x3b0 [ 242.931365] ? kthread_park+0x90/0x90 [ 242.931370] ret_from_fork+0x35/0x40 [ 242.931384] INFO: task kworker/4:2:328 blocked for more than 120 seconds. [ 242.931389] Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 242.931391] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 242.931394] kworker/4:2 D0 328 2 0x80004000 [ 242.931405] Workqueue: events_long ucsi_init [typec_ucsi] [ 242.931407] Call Trace: [ 242.931422] __schedule+0x2e3/0x740 [ 242.931436] schedule+0x42/0xb0 [ 242.931441] schedule_timeout+0x203/0x2f0 [ 242.931449] ? ttwu_do_activate+0x5b/0x70 [ 242.931455] wait_for_completion+0xb1/0x120 [ 242.931461] ? wake_up_q+0x70/0x70 [ 242.931467] __flush_work+0x123/0x1d0 [ 242.931473] ? worker_detach_from_pool+0xb0/0xb0 [ 242.931481] __cancel_work_timer+0x10e/0x190 [ 242.931489] ? kernfs_put+0xf1/0x180 [ 242.931499] cancel_work_sync+0x10/0x20 [ 242.931507] dp_altmode_remove+0x23/0x30 [typec_displayport] [ 242.931520] typec_remove+0x4b/0x8d [typec] [ 242.931531] device_release_driver_internal+0xf0/0x1d0 [ 242.931540] device_release_driver+0x12/0x20 [ 242.931546] bus_remove_device+0xe1/0x150 [ 242.931552] device_del+0x165/0x370 [ 242.931559] ? kfree+0x22b/0x240 [ 242.931565] device_unregister+0x1b/0x60 [ 242.931576] typec_unregister_altmode+0x30/0x40 [typec] [ 242.931582] ucsi_unregister_altmodes+0x42/0xa0 [typec_ucsi] [ 242.931588] ucsi_unregister_partner.part.0+0x17/0x30 [typec_ucsi] [ 242.931594] ucsi_init+0x179/0x1c0 [typec_ucsi] [ 242.931600] process_one_work+0x1eb/0x3b0 [ 242.931605] worker_thread+0x4d/0x400 [ 242.931609] kthread+0x104/0x140 [ 242.931614] ? process_one_work+0x3b0/0x3b0 [ 242.931617] ? kthread_park+0x90/0x90 [ 242.931622] ret_from_fork+0x35/0x40 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nikolaj2154 F pulseaudio /dev/snd/controlC0: nikolaj2154 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 22:16:08 2020 InstallationDate: Installed on 2019-11-15 (151 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash mem_sleep_default=deep vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (10 days ago) dmi.bios.date: 12/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.12.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1871182 ** Tags added: iso-testing -- 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/1871182 Title: [RTL810xE] No ethernet connection Status in linux package in Ubuntu: Confirmed Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871182/+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 1873360] Re: Ethernet driver not loaded at boot
*** This bug is a duplicate of bug 1871182 *** https://bugs.launchpad.net/bugs/1871182 ** This bug has been marked a duplicate of bug 1871182 [RTL810xE] No ethernet connection -- 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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 1873316] Re: bluetooth
Okay, Thank you. Jim On Thu, Apr 16, 2020 at 9:35 PM Daniel van Vugt < daniel.van.v...@canonical.com> wrote: > Your kernel shows some recurring problems with Bluetooth: > > [205443.289468] Bluetooth: hci0: command 0x1001 tx timeout > ... > [205451.385131] Bluetooth: hci0: CSR: Local version failed (-110) > > "CSR" sounds like Cambridge Silicon Radio, which is a brand of Bluetooth > chip that many people find to be unreliable. So it might be a good idea > to try a different brand. > > ** Summary changed: > > - bluetooth > + I can't get bluetooth to work > > ** Package changed: xorg (Ubuntu) => linux (Ubuntu) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1873316 > > Title: > I can't get bluetooth to work > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > I can't get bluetooth to work > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 > Uname: Linux 4.15.0-96-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.14 > Architecture: amd64 > CompizPlugins: No value set for > `/apps/compiz-1/general/screen0/options/active_plugins' > CompositorRunning: None > Date: Thu Apr 16 12:04:07 2020 > DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, > re-reading > DistroCodename: bionic > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes, if not too technical > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] > [1002:9901] (prog-if 00 [VGA controller]) > Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] > [1458:d000] > InstallationDate: Installed on 2018-11-09 (523 days ago) > InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 > (20170801) > MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. > ProcEnviron: >PATH=(custom, no user) >LANG=en_US.UTF-8 >SHELL=/bin/bash > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic > root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) > dmi.bios.date: 12/24/2015 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: F2 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: F2A88XM-D3HP > dmi.board.vendor: Gigabyte Technology Co., Ltd. > dmi.board.version: x.x > dmi.chassis.asset.tag: To Be Filled By O.E.M. > dmi.chassis.type: 3 > dmi.chassis.vendor: Gigabyte Technology Co., Ltd. > dmi.chassis.version: To Be Filled By O.E.M. > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: > dmi.product.family: To be filled by O.E.M. > dmi.product.name: To be filled by O.E.M. > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: Gigabyte Technology Co., Ltd. > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Wed Jul 24 17:33:18 2019 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 > xserver.video_driver: radeon > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873316/+subscriptions > -- 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/1873316 Title: I can't get bluetooth to work Status in linux package in Ubuntu: Confirmed Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename:
[Kernel-packages] [Bug 1849947] Re: Dell XPS 13 (7390) Display Flickering - 19.10
I am in kernel 5.4.0-24-generic from ubuntu 20, and I am still seeing this issue, btw I am will dell xps 15 9570 is a 4k display model, this issue is with me since ubuntu 18 / 19 and now 20. -- 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/1849947 Title: Dell XPS 13 (7390) Display Flickering - 19.10 Status in linux package in Ubuntu: Fix Released Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: Hi there, I recently purchased a Dell XPS 13 7390 (Developer Edition). I decided to replace 18.4 LTS with 19.10 and so far it has been pretty smooth. However, there is one issue which occurs frequently whereby the display flickers and becomes unusable. The best way to describe the appearance is that the image becomes heavily distorted. Sometimes it only happens for a split second, other times it is permanently distorted. When this happens, simply closing the laptop lip and re-opening seems to put the display back into it's correct state. I didn't experience this issue on 18.04 LTS which is why I believe it's a Software Bug within 19.10. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 26 11:11:43 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Device [8086:9b41] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0962] InstallationDate: Installed on 2019-10-25 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 13 7390 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.3 dmi.board.name: 0G2D0W dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd08/23/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0G2D0W:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 dmi.product.sku: 0962 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849947/+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 1873316] Re: I can't get bluetooth to work
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/ -- 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/1873316 Title: I can't get bluetooth to work Status in linux package in Ubuntu: Confirmed Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873316/+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 1861359] Re: swap storms kills interactive use
Andrea, I've been running the v1 kernel for a day or so now: [0.00] Linux version 5.4.0-24-generic (arighi@sita) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1)) #28+lp1861359v1 SMP Wed Apr 15 14:49:33 UTC 2020 (Ubuntu 5.4.0-24.28+lp1861359v1-generic 5.4.30) $ uptime 02:21:45 up 1 day, 9 min, 14 users, load average: 0.42, 0.25, 0.23 and have not seen any hangs or stalls of any sort in the ~ten hours that I've been using it. Normally these problems start to appear about a day into use, so it's perhaps still early to declare success, but this is looking promising. Even loading https://platform.leolabs.space/visualization in firefox just causes momentary glitches in mouse movement, like 50ms kind of range. (I know this range is pretty poor for humans to tell, but it sure feels like less than half a second by a lot.) Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: [Impact] High watermark boosting can cause large swap activity under certain memory intensive workloads, making the system very unresponsive (screen does not refresh, keyboard not responding, etc.). This large swap activity seems to be prevented disabling high watermark boosting. [Test case] Opening this web page in chrome seems to be a good reproducer of the problem: https://platform.leolabs.space/visualizations/conjunction?type=conjunction=2004981040 When this page is opened we can clearly see from 'top' (for example) that the used swap is going up very quickly. With the fix applied swap is not used at all and the system is always responsive. [Fix] Set vm.watermark_boost_factor to 0, disabling watermark boosting by default. [Regression potential] Regression potential is minimal, setting vm.watermark_boost_factor to 0 by default restores the old kernel behavior before watermark boosting was introduced. In case of unexpected regressions we can always fix this in user-space via sysctl. [Original report] Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic
[Kernel-packages] [Bug 1873316] Re: bluetooth
Your kernel shows some recurring problems with Bluetooth: [205443.289468] Bluetooth: hci0: command 0x1001 tx timeout ... [205451.385131] Bluetooth: hci0: CSR: Local version failed (-110) "CSR" sounds like Cambridge Silicon Radio, which is a brand of Bluetooth chip that many people find to be unreliable. So it might be a good idea to try a different brand. ** Summary changed: - bluetooth + I can't get bluetooth to work ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873316 Title: I can't get bluetooth to work Status in linux package in Ubuntu: Confirmed Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873316/+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 1873316] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873316 Title: I can't get bluetooth to work Status in linux package in Ubuntu: Confirmed Bug description: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873316/+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 1873316] [NEW] I can't get bluetooth to work
You have been subscribed to a public bug: I can't get bluetooth to work ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Apr 16 12:04:07 2020 DistUpgraded: 2019-08-03 17:51:10,821 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660D] [1002:9901] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Trinity [Radeon HD 7660D] [1458:d000] InstallationDate: Installed on 2018-11-09 (523 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=974dc935-0484-40f5-82d9-c10d0243872c ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-08-03 (256 days ago) dmi.bios.date: 12/24/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88XM-D3HP dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XM-D3HP:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Wed Jul 24 17:33:18 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- I can't get bluetooth to work https://bugs.launchpad.net/bugs/1873316 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 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872198/+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 1814983] Re: zfs poor sustained read performance from ssd pool
Writing 8589934592 (eight gigs) into the zfs_arc_dnode_limit seemed to
make an improvement: the arc_prune threads would periodically spike
above 20% CPU use, but would return to 2-5% CPU use quickly; it worked
well for a long time, perhaps even hours, before all the arc_prune
threads returned to ~50% CPU use.
I tried one gigabyte for a bit but the arc_prune threads returned
quickly. Tuning this may take a bit.
Thanks for the tip.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814983
Title:
zfs poor sustained read performance from ssd pool
Status in Native ZFS for Linux:
Unknown
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
Hello,
I'm seeing substantially slower read performance from an ssd pool than
I expected.
I have two pools on this computer; one ('fst') is four sata ssds, the
other ('srv') is nine spinning metal drives.
With a long-running ripgrep process on the fst pool, performance
started out really good and grew to astonishingly good (iirc ~30kiops,
as measured by zpool iostat -v 1). However after a few hours the
performance has dropped to 30-40 iops. top reports an arc_reclaim and
many arc_prune processes to be consuming most of the CPU time.
I've included a screenshot of top, some output from zpool iostat -v 1,
and arc_summary, with "===" to indicate the start of the next
command's output:
===
top (memory in gigabytes):
top - 16:27:53 up 70 days, 16:03, 3 users, load average: 35.67, 35.81, 35.58
Tasks: 809 total, 19 running, 612 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 58.1 sy, 0.0 ni, 39.2 id, 2.6 wa, 0.0 hi, 0.0 si, 0.0
st
GiB Mem : 125.805 total,0.620 free, 96.942 used, 28.243 buff/cache
GiB Swap:5.694 total,5.688 free,0.006 used. 27.840 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1523 root 20 00.0m 0.0m 0.0m R 100.0 0.0 290:52.26
arc_reclaim
4484 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:18.79 arc_prune
6225 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:11.92 arc_prune
7601 root 20 00.0m 0.0m 0.0m S 56.2 0.0 2:50.25 arc_prune
30891 root 20 00.0m 0.0m 0.0m S 56.2 0.0 1:33.08 arc_prune
3057 root 20 00.0m 0.0m 0.0m S 55.9 0.0 9:00.95 arc_prune
3259 root 20 00.0m 0.0m 0.0m R 55.9 0.0 3:16.84 arc_prune
24008 root 20 00.0m 0.0m 0.0m S 55.9 0.0 1:55.71 arc_prune
1285 root 20 00.0m 0.0m 0.0m R 55.6 0.0 3:20.52 arc_prune
5345 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:15.99 arc_prune
30121 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:35.50 arc_prune
31192 root 20 00.0m 0.0m 0.0m S 55.6 0.0 6:17.16 arc_prune
32287 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:28.02 arc_prune
32625 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:27.34 arc_prune
22572 root 20 00.0m 0.0m 0.0m S 55.3 0.0 10:02.92 arc_prune
31989 root 20 00.0m 0.0m 0.0m R 55.3 0.0 1:28.03 arc_prune
3353 root 20 00.0m 0.0m 0.0m R 54.9 0.0 8:58.81 arc_prune
10252 root 20 00.0m 0.0m 0.0m R 54.9 0.0 2:36.37 arc_prune
1522 root 20 00.0m 0.0m 0.0m S 53.9 0.0 158:42.45 arc_prune
3694 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:20.79 arc_prune
13394 root 20 00.0m 0.0m 0.0m R 53.9 0.0 10:35.78 arc_prune
24592 root 20 00.0m 0.0m 0.0m R 53.9 0.0 1:54.19 arc_prune
25859 root 20 00.0m 0.0m 0.0m S 53.9 0.0 1:51.71 arc_prune
8194 root 20 00.0m 0.0m 0.0m S 53.6 0.0 0:54.51 arc_prune
18472 root 20 00.0m 0.0m 0.0m R 53.6 0.0 2:08.73
[Kernel-packages] [Bug 1873164] Re: [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation
It sounds like the main problem then is actually during boot then. Would you like this bug to focus on that or some other problem after booting? ** Also affects: plymouth (Ubuntu) Importance: Undecided Status: New ** Changed in: plymouth (Ubuntu) Importance: Undecided => Low ** Changed in: plymouth (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873164 Title: [Lenovo Ideapad D330] [bmc150] Problem with g sensor and screen orientation Status in iio-sensor-proxy package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Status in plymouth package in Ubuntu: Incomplete Bug description: I am using Lenovo Ideapad D330 2 in 1 Laptop. It has Intel UHD Graphics 600. and its a touchscreen laptop. The Problem is i'm facing with g sensor and screen orientation ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 11:08:58 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 605 [17aa:39ff] InstallationDate: Installed on 2020-04-16 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: LENOVO 81H3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=c7483622-a4a6-415a-9767-7aa10bb670db ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 8NCN37WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55724 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad D330-10IGM dmi.modalias: dmi:bvnLENOVO:bvr8NCN37WW:bd10/30/2019:svnLENOVO:pn81H3:pvrLenovoideapadD330-10IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55724WIN:cvnLENOVO:ct32:cvrLenovoideapadD330-10IGM: dmi.product.family: ideapad D330-10IGM dmi.product.name: 81H3 dmi.product.sku: LENOVO_MT_81H3_BU_idea_FM_ideapad D330-10IGM dmi.product.version: Lenovo ideapad D330-10IGM dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1873164/+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 1873360] Re: Ethernet driver not loaded at boot
Sorry for last comment---long day .. but attached is the apport file ** Attachment added: "apport.linux-image-5.4.0-24-generic.94ipruqt.apport" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+attachment/5355836/+files/apport.linux-image-5.4.0-24-generic.94ipruqt.apport -- 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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 1808957] Re: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle
Same problem and same solution as OP in a Dell XPS 9360 on Ubuntu 20.04. It is a regression coming from 19.10. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1808957 Title: Dell XPS 13 (9370) defaults to s2idle sleep/suspend instead of deep, NVMe drains lots of power under s2idle Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in linux-oem source package in Cosmic: Invalid Status in linux-oem-osp1 source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-oem source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: It seems that the Dell 9370 is set to go into s2idle mode rather than deep sleep, forgoing significant power savings. I have confirmed this by suspending and then checking: sudo journalctl | grep "PM: suspend" | tail -2. If the output is PM: suspend entry (s2idle) PM: suspend exit cat /sys/power/mem_sleep showed [s2idle] deep As a temporary fix, I typed echo deep > /sys/power/mem_sleep as a root user (sudo -i). Then the output of cat /sys/power/mem_sleep was s2idle [deep] After suspending now, sudo journalctl | grep "PM: suspend" | tail -2 returns PM: suspend entry (deep) PM: suspend exit I have made this permanent by editing /etc/default/grub and replacing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" with GRUB_CMDLINE_LINUX_DEFAULT="quiet splash mem_sleep_default=deep" then regenerating my grub configuration (sudo grub-mkconfig -o /boot/grub/grub.cfg). This appears to be working with no ill effects. Credit to https://askubuntu.com/a/1036122/470077 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aaron-work 3672 F pulseaudio /dev/snd/pcmC0D0p: aaron-work 3672 F...m pulseaudio Date: Tue Dec 18 09:52:44 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/ubuntu-vg/swap_1 InstallationDate: Installed on 2018-09-04 (104 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-11-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash mem_sleep_default=deep vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.175.1 SourcePackage: linux UpgradeStatus: Upgraded to cosmic on 2018-10-26 (52 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.1:bd08/09/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1808957/+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 1873360] Re: Ethernet driver not loaded at boot
unable to run the command "apport-collect 1873360" as no internet connection available. I can manually attach log files -- which logs would be appropriate? -- 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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 446657] Re: Bluetooth's on/off status doesn't update from the SetProperty D-Bus method that bluetoothd sends
Launchpad has imported 58 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=570073. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2010-03-03T08:12:26+00:00 sassmann wrote: Description of problem: On my lenovo t500 bluetooth is always enabled after reboot, regardless if it was turned off before the reboot or not. Not sure why this happens but someway during initrd run I see the bluetooth LED turning on. Version-Release number of selected component (if applicable): gnome-bluetooth-2.28.6-2.fc12.x86_64 How reproducible: always Steps to Reproduce: 1. turn off bluetooth in gnome-bluetooth applet 2. reboot 3. Actual results: bluetooth is always turned on Expected results: bluetooth setting is the same as before the reboot Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446657/comments/27 On 2010-06-30T08:16:46+00:00 jpazdziora wrote: The same problem on Fedora 13 with gnome-bluetooth-2.30.0-1.fc13.i686 on T61. Bastien, please, let us know if some other package might be causing this and you'd need more detailed version info, or if it is configurable somewhere. I am pretty sure that on Fedora 11 my bluetooth was off after reboot (and I had the option to turn it on with the applet on my panel). That's why I'd consider this a regression. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446657/comments/44 On 2010-06-30T08:41:22+00:00 jpazdziora wrote: Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true to false, and reboot, the applet will show that white x in red on its icon, to say that bluetooth is off. However, the bluetooth LED is still on, so in that case the applet shows incorrect information. So maybe this is a bug in bluez (which owns that /etc/bluetooth/main.conf), that it does not honor the setting (and provides bad info to the applet as well)? But I don't see a component bluez in bugzilla to report it ... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446657/comments/45 On 2010-06-30T08:43:40+00:00 jpazdziora wrote: (In reply to comment #2) > Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true > to > false, and reboot, the applet will show that white x in red on its icon, to > say > that bluetooth is off. However, the bluetooth LED is still on, so in that case > the applet shows incorrect information. Another finding: even if the icon of the applet shows that bluetooth is off, when I click it, the status is shown as On, and I have the option to "Turn Off Bluetooth". When I turn if off, the LED goes off as well. When I then turn in on again, the LED goes on, but the icon on the panel still shows that red/white "off" sign. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/446657/comments/46 On 2010-08-03T14:47:21+00:00 bnocera wrote: (In reply to comment #1) > The same problem on Fedora 13 with gnome-bluetooth-2.30.0-1.fc13.i686 on T61. > Bastien, please, let us know if some other package might be causing this and > you'd need more detailed version info, or if it is configurable somewhere. > > I am pretty sure that on Fedora 11 my bluetooth was off after reboot (and I > had > the option to turn it on with the applet on my panel). That's why I'd consider > this a regression. Definitely not a regression, if anything, it's a kernel one. The ibm- laptop (or whatever the kernel module is called for Thinkpads) module changed behaviour. (In reply to comment #2) > Funny thing: if I change in /etc/bluetooth/main.conf InitiallyPowered = true > to > false, and reboot, the applet will show that white x in red on its icon, to > say > that bluetooth is off. However, the bluetooth LED is still on, so in that case > the applet shows incorrect information. Nope. Check the output of "hciconfig hci0", you'll see that the device is enabled, just not powered. The hardware has no ways to know that... > So maybe this is a bug in bluez (which owns that /etc/bluetooth/main.conf), > that it does not honor the setting (and provides bad info to the applet as > well)? But I don't see a component bluez in bugzilla to report it ... This is a BIOS bug. gnome-bluetooth doesn't hold *any* information as to the state of Bluetooth, and bluetoothd (somewhat) remembers the state of the device. The problem is that when it's hard-blocked, eg. disabled in hardware, bluetoothd has no Bluetooth devices to remember the
Re: [Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
On Thu, 2020-04-16 at 20:54 +, Anton Keks wrote: > No, normally it's below 60C. > > I can get it to 80C (and shutdown) when the AC is plugged in and > charging the battery and I load my CPU a lot at the same time. > > Usually it means a video conference with several people and charging > at > the same time. A little bit of sun also helps. > > So I guess the cooling mechanism here is not adequate, if thermald > tries > to do anything about it at all. I am attaching thermald debug log, if > it > helps. > > Also, I usually can avoid the shutdown if I manually reduce CPU > target > temperature to 70C using this tool: > https://github.com/erpalma/throttled > This results in very heavy CPU throttling well below 1GHz. Not sure if you ran dptfxtract tool on this system. May be thermald is not doing anything because there is no target device. Thanks, Srinivas > > > ** Attachment added: "thermald debug log" > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+attachment/5355770/+files/thermald.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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1866972] Re: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests
Was observed on the linux-gcp 5.3 kernel: 04/14 09:54:08 DEBUG| utils:0153| [stdout] # [45] Register/unregister many kprobe events [FAIL] 5.3.0-1018.19~18.04.1 linux-gcp-5.3 ** Tags added: gcp -- 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/1866972 Title: ftrace test failed with Register/unregister many kprobe events in ubuntu_kernel_selftests Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Triaged Status in linux source package in Eoan: New Bug description: Issue found on c4.large with 5.0.0-1027.30-aws Test failed with: [42] Register/unregister many kprobe events [FAIL] selftests: ftrace: ftracetest === Ftrace unit tests === [1] Basic trace file check [PASS] [2] Basic test for tracers [PASS] [3] Basic trace clock test [PASS] [4] Basic event tracing check[PASS] [5] Change the ringbuffer size [PASS] [6] Snapshot and tracing setting [PASS] [7] trace_pipe and trace_marker [PASS] [8] Generic dynamic event - add/remove kprobe events [PASS] [9] Generic dynamic event - add/remove synthetic events [PASS] [10] Generic dynamic event - selective clear (compatibility) [PASS] [11] Generic dynamic event - generic clear event [PASS] [12] event tracing - enable/disable with event level files [PASS] [13] event tracing - restricts events based on pid [PASS] [14] event tracing - enable/disable with subsystem level files [PASS] [15] event tracing - enable/disable with top level files [PASS] [16] Test trace_printk from module [UNRESOLVED] [17] ftrace - function graph filters with stack tracer [PASS] [18] ftrace - function graph filters [PASS] [19] ftrace - function pid filters [PASS] [20] ftrace - stacktrace filter command [PASS] [21] ftrace - function trace with cpumask[PASS] [22] ftrace - test for function event triggers [PASS] [23] ftrace - function trace on module [UNRESOLVED] [24] ftrace - function profiling [PASS] [25] ftrace - function profiler with function tracing[PASS] [26] ftrace - test reading of set_ftrace_filter [PASS] [27] ftrace - test for function traceon/off triggers [PASS] [28] Test creation and deletion of trace instances while setting an event [PASS] [29] Test creation and deletion of trace instances [PASS] [30] Kprobe dynamic event - adding and removing [PASS] [31] Kprobe dynamic event - busy event check [PASS] [32] Kprobe dynamic event with arguments [PASS] [33] Kprobe event with comm arguments[PASS] [34] Kprobe event string type argument [PASS] [35] Kprobe event symbol argument[PASS] [36] Kprobe event argument syntax[PASS] [37] Kprobes event arguments with types [PASS] [38] Kprobe event auto/manual naming [PASS] [39] Kprobe dynamic event with function tracer [PASS] [40] Kretprobe dynamic event with arguments [PASS] [41] Kretprobe dynamic event with maxactive [PASS] [42] Register/unregister many kprobe events [FAIL] [43] Kprobe dynamic event - adding and removing [PASS] [44] test for the preemptirqsoff tracer [UNSUPPORTED] [45] Test wakeup tracer [PASS] [46] Test wakeup RT tracer [PASS] [47] event trigger - test extended error support [PASS] [48] event trigger - test field variable support [PASS] [49] event trigger - test multiple actions on hist trigger [PASS] [50] event trigger - test inter-event histogram trigger onmatch action [PASS] [51] event trigger - test inter-event histogram trigger onmatch-onmax action [PASS] [52] event trigger - test inter-event histogram trigger onmax action [PASS] [53] event trigger - test synthetic_events syntax parser [PASS] [54] event trigger - test event enable/disable trigger [PASS] [55] event trigger - test trigger filter [PASS] [56] event trigger - test histogram modifiers[PASS] [57] event trigger - test multiple histogram triggers[PASS] [58] event trigger - test snapshot-trigger [PASS] [59] event trigger - test stacktrace-trigger [PASS] [60] trace_marker trigger - test snapshot trigger[PASS] [61] trace_marker trigger - test histogram with synthetic event against kernel event [PASS] [62] trace_marker trigger - test histogram with synthetic event [PASS] [63] event trigger - test traceon/off trigger[PASS] [64] (instance) Basic test for tracers [PASS] [65] (instance) Basic trace clock test [PASS] [66] (instance) Change the ringbuffer size [PASS] [67] (instance) Snapshot and tracing setting [PASS] [68] (instance) trace_pipe and trace_marker [PASS] [69] (instance) event tracing - enable/disable with event level
[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
"sudo echo "disabled" > /sys/class/thermal/thermal_zone0/mode" is not correct. Try echo "disabled" | sudo tee /sys/class/thermal/thermal_zone0/mode -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1873179] Re: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46
There are four patches added to i915 from Ubuntu-5.3.0-45.37 to Ubuntu-5.3.0-46.38, like in https://people.canonical.com/~alexhung/LP1873179/patches/ I built four kernels, each with one patch removed: https://people.canonical.com/~alexhung/LP1873179/ For example, p-1 = Ubuntu-5.3.0-46.38 with Revert "drm/i915: Schedue request retirement in execlists_user_end()" p-2 = p-1 with Revert "drm/i915/userptr: fix size calculation" p-3 = p-2 ... p-all = p3 ... Let us know which one caused your problem and we can discuss further. If a patch is identified, I am also interested in knowing whether focal kernel (based on 5.4) is able to solve your problem. If so, we can investigate where we can backport anything from 5.4 to 5.3. -- 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/1873179 Title: i915 bug: ZOOM messenger is very slow w/ kernel 5.3.0-46 Status in linux package in Ubuntu: Confirmed Bug description: Hi. I'm running Xubuntu 5.3.0-45.37-generic 5.3.18 on ThinkPad P1 Gen2 (ThinkPad Carbon X1 without Nvidia graphics). This bug happens on Eoan kernel 5.3.0-46 only. Kernels -45 and earlier don't have it, so I had to revert to 5.3.0-45. Steps to reproduce: 1. Install ZOOM .deb from https://zoom.us/download?os=linux 2. Start it. 3. Try to start ZOOM meeting. 4. GUI becomes very-very slow, but not completely frozen. No crashes. 5. As soon as ZOOM meeting window is closed, lines "Resetting rcs0 for hang on rcs0" stop coming and GUI is OK. In syslog I see following lines: --- [ 111.956936] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 111.957947] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 119.951013] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 127.949941] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 135.950174] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 143.950558] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 151.950819] i915 :00:02.0: Resetting rcs0 for hang on rcs0 --- --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vburdo 1450 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-15 (31 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QUS11E00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-45-generic N/A linux-backports-modules-5.3.0-45-generic N/A linux-firmware1.183.5 Tags: eoan Uname: Linux 5.3.0-45-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lp lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/20/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET42W (1.29 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QUS11E00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET42W(1.29):bd01/20/2020:svnLENOVO:pn20QUS11E00:pvrThinkPadP1Gen2:rvnLENOVO:rn20QUS11E00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad P1 Gen 2 dmi.product.name: 20QUS11E00 dmi.product.sku: LENOVO_MT_20QU_BU_Think_FM_ThinkPad P1 Gen 2 dmi.product.version: ThinkPad P1 Gen 2 dmi.sys.vendor: LENOVO modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-03-16T16:40:07.038972 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vburdo 1450 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2020-03-15 (31 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QUS11E00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic root=UUID=6059e627-eadb-4530-bba0-ac77ea95ba2d ro quiet splash resume=UUID=2ba66786-beee-495b-bcff-db0f19c70ccb vt.handoff=7 ProcVersionSignature:
[Kernel-packages] [Bug 1814983] Re: zfs poor sustained read performance from ssd pool
Thanks Colin,
I believe that bountysource.com url is a scrape of
https://github.com/openzfs/zfs/issues/6223
I hadn't seen much of this information before.
Sadly my machine doesn't have enough memory to just keep turning up the
knobs -- the working set far exceeds the memory of my computer.
A recent archive-wide search I performed, I tried the following:
echo 126491074560 >> /sys/module/zfs/parameters/zfs_arc_max # eight gigs less
than RAM
echo 117901139968 >> /sys/module/zfs/parameters/zfs_arc_dnode_limit # eight
gigs less than ^^
I picked these numbers entirely at a guess. The zfs arc had previously
been 0 -- for half of ram, 64 gigabytes.
This workload seemed to run fine for longer than usual (arc_prune cpu
numbers were low, good read iops reported in zpool status output -- not
ideal indicator of actual progress, but a reasonable proxy) but
eventually the arc_prune tasks started consuming most of the CPUs, and
read iops fell to the dozens.
I haven't tried a run with silly low numbers for the arc dnode limit,
but I'm curious...
Thanks
** Bug watch added: github.com/openzfs/zfs/issues #6223
https://github.com/openzfs/zfs/issues/6223
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1814983
Title:
zfs poor sustained read performance from ssd pool
Status in Native ZFS for Linux:
Unknown
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
Hello,
I'm seeing substantially slower read performance from an ssd pool than
I expected.
I have two pools on this computer; one ('fst') is four sata ssds, the
other ('srv') is nine spinning metal drives.
With a long-running ripgrep process on the fst pool, performance
started out really good and grew to astonishingly good (iirc ~30kiops,
as measured by zpool iostat -v 1). However after a few hours the
performance has dropped to 30-40 iops. top reports an arc_reclaim and
many arc_prune processes to be consuming most of the CPU time.
I've included a screenshot of top, some output from zpool iostat -v 1,
and arc_summary, with "===" to indicate the start of the next
command's output:
===
top (memory in gigabytes):
top - 16:27:53 up 70 days, 16:03, 3 users, load average: 35.67, 35.81, 35.58
Tasks: 809 total, 19 running, 612 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.0 us, 58.1 sy, 0.0 ni, 39.2 id, 2.6 wa, 0.0 hi, 0.0 si, 0.0
st
GiB Mem : 125.805 total,0.620 free, 96.942 used, 28.243 buff/cache
GiB Swap:5.694 total,5.688 free,0.006 used. 27.840 avail Mem
PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND
1523 root 20 00.0m 0.0m 0.0m R 100.0 0.0 290:52.26
arc_reclaim
4484 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:18.79 arc_prune
6225 root 20 00.0m 0.0m 0.0m R 56.2 0.0 1:11.92 arc_prune
7601 root 20 00.0m 0.0m 0.0m S 56.2 0.0 2:50.25 arc_prune
30891 root 20 00.0m 0.0m 0.0m S 56.2 0.0 1:33.08 arc_prune
3057 root 20 00.0m 0.0m 0.0m S 55.9 0.0 9:00.95 arc_prune
3259 root 20 00.0m 0.0m 0.0m R 55.9 0.0 3:16.84 arc_prune
24008 root 20 00.0m 0.0m 0.0m S 55.9 0.0 1:55.71 arc_prune
1285 root 20 00.0m 0.0m 0.0m R 55.6 0.0 3:20.52 arc_prune
5345 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:15.99 arc_prune
30121 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:35.50 arc_prune
31192 root 20 00.0m 0.0m 0.0m S 55.6 0.0 6:17.16 arc_prune
32287 root 20 00.0m 0.0m 0.0m S 55.6 0.0 1:28.02 arc_prune
32625 root 20 00.0m 0.0m 0.0m R 55.6 0.0 1:27.34 arc_prune
22572 root 20 00.0m 0.0m 0.0m S 55.3 0.0 10:02.92 arc_prune
31989 root 20 00.0m 0.0m 0.0m R 55.3 0.0 1:28.03 arc_prune
3353 root 20 00.0m 0.0m 0.0m R 54.9 0.0 8:58.81 arc_prune
10252 root 20 00.0m 0.0m 0.0m R 54.9 0.0 2:36.37 arc_prune
1522 root 20 00.0m 0.0m 0.0m S 53.9 0.0
[Kernel-packages] [Bug 1872526] Re: dbgsym package for linux-image-4.15.0-1065-aws missing
I have checked the status of the pkg, it's still in the queue just wanted to update the bug, hopefully we should see it in updates by Sat EOD. ** Changed in: linux-aws (Ubuntu) Importance: High => Medium ** Changed in: linux-aws (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1872526 Title: dbgsym package for linux-image-4.15.0-1065-aws missing Status in linux-aws package in Ubuntu: In Progress Bug description: On April 6th, a new linux-aws was released, targeting linux- image-4.15.0-1065-aws. However it's been over a week and the linux- image-4.15.0-1065-aws-dbgsym is still not available on http://ddebs.ubuntu.com/ubuntu "bionic-updates". It does seem to be there on "bionic-proposed", but I think it should be there on "bionic- updates" as well given that "linux-image-4.15.0-1065-aws" is there on bionic-updates. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1065-aws (not installed) ProcVersionSignature: User Name 4.15.0-1051.53-aws 4.15.18 Uname: Linux 4.15.0-1051-aws x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Mon Apr 13 19:00:32 2020 Ec2AMI: ami-096bb69690a48bcc9 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: t2.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1872526/+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 1873360] Re: Ethernet driver not loaded at boot
** Package changed: network-manager (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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 1873360] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1873360 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** 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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 1873360] Re: Ethernet driver not loaded at boot
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1873360 ** Tags added: iso-testing -- 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/1873360 Title: Ethernet driver not loaded at boot Status in linux package in Ubuntu: Incomplete Bug description: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873360/+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 1873360] [NEW] Ethernet driver not loaded at boot
You have been subscribed to a public bug: Running a test on Focal Daily build 16.04.2020 the ethernet driver was not loaded at boot - attached is the dmesg.log - the machine was a Dell [Inspiron] 3521, (i3-3217U, 4GB, Intel HD Graphics 4000, Intel HM76 chipset 10/100 Mbps ethernet controller integrated on system board, WiFi 802.11 b/g/N, ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Ethernet driver not loaded at boot https://bugs.launchpad.net/bugs/1873360 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 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
Here is the problem. Fanatic test-local-docker, creates a local docker container and imports local DNS via systemd-resolv.conf , it tries to install "Ping" and can't do that because of our firewall, well... the firewall in the lab. It's blocking access to ports.ubuntu.com.. 2 ways we can fix this.. Need to install docker manually, prior to running the teest and preseed docker templates to add Acquire::http::Proxy "http://:3128"; so that it imports to /etc/apt/apt.conf OR we update the firewall rules to allow access to ports.ubuntu.com from all machines in this lab. Giving we don't own that network it may require some haggling. updating our test may be the least invasive, but it's a pain in the rear. -- 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/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+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 1872198] Re: [HP Pavilion 17] Lost the use of the numeric keypad
By any chance is "Mouse Keys" enabled? To check, go to the "Settings" application and look under the "Universal Access" tab. In that tab there is a "Mouse Keys" option under "Pointing & Clicking". If this is enabled, please disable it and see if that restores use of your numeric keypad. -- 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/1872198 Title: [HP Pavilion 17] Lost the use of the numeric keypad Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Hello I lost the use of the numeric keypad while it works in windows. Thank you ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 11 16:17:54 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.3.0-46-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.3.0-47-generic, x86_64: installed ndiswrapper, 1.60, 5.3.0-47-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Atom Processor Z36xxx/Z37xxx Series Graphics & Display [103c:227c] InstallationDate: Installed on 2020-03-23 (18 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Hewlett-Packard HP Pavilion 17 Notebook PC MonitorsUser.xml: ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=e42364f6-7faf-4750-be1d-6e44dd2b71f7 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/09/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.57 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 227C dmi.board.vendor: Hewlett-Packard dmi.board.version: 76.35 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.57:bd11/09/2018:svnHewlett-Packard:pnHPPavilion17NotebookPC:pvr097510405F1620180:rvnHewlett-Packard:rn227C:rvr76.35:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null dmi.product.name: HP Pavilion 17 Notebook PC dmi.product.sku: J2U02EA#ABF dmi.product.version: 097510405F1620180 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872198/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
No, normally it's below 60C. I can get it to 80C (and shutdown) when the AC is plugged in and charging the battery and I load my CPU a lot at the same time. Usually it means a video conference with several people and charging at the same time. A little bit of sun also helps. So I guess the cooling mechanism here is not adequate, if thermald tries to do anything about it at all. I am attaching thermald debug log, if it helps. Also, I usually can avoid the shutdown if I manually reduce CPU target temperature to 70C using this tool: https://github.com/erpalma/throttled This results in very heavy CPU throttling well below 1GHz. ** Attachment added: "thermald debug log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+attachment/5355770/+files/thermald.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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
On Thu, 2020-04-16 at 20:18 +, Anton Keks wrote: > I have traced it to int3403_thermal module. > If I do rmmod int3403_thermal - the thermal_zone3 goes away an no > thermal shutdown is happening. > I can use it as a workaround - but is it dangerous for the HW? > > https://github.com/torvalds/linux/blob/master/drivers/thermal/intel/int340x_thermal/int3403_thermal.c > > > From what I see in the source, it is probably related to battery or > charger or both. > > So I guess thermald should take this sensor into acccount when > throttling? > > When I quickly modprobe int3403_thermal back, the full output is here > (it is seen that temp is 79C, which is really close to the critical > 80C): Correct. So this will shutdown the system. Is that sensor temperature always in that range? If it is then sensor may be faulty. Thanks, Srinivas > > thermal_zone3$ grep . * > available_policies:power_allocator user_space step_wise bang_bang > fair_share > grep: emul_temp: Permission denied > integral_cutoff:0 > k_d:0 > k_i:0 > k_po:0 > k_pu:0 > offset:0 > policy:user_space > grep: power: Is a directory > slope:0 > grep: subsystem: Is a directory > sustainable_power:0 > temp:79000 > trip_point_0_hyst:2000 > trip_point_0_temp:0 > trip_point_0_type:passive > trip_point_1_hyst:2000 > trip_point_1_temp:0 > trip_point_1_type:passive > trip_point_2_hyst:2000 > trip_point_2_temp:8 > trip_point_2_type:critical > trip_point_3_hyst:2000 > trip_point_3_temp:75000 > trip_point_3_type:hot > trip_point_4_hyst:2000 > trip_point_4_temp:65000 > trip_point_4_type:passive > trip_point_5_hyst:2000 > trip_point_5_temp:6 > trip_point_5_type:active > trip_point_6_hyst:2000 > trip_point_6_temp:5 > trip_point_6_type:active > trip_point_7_hyst:2000 > trip_point_7_temp:4 > trip_point_7_type:active > type:SEN4 > -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1873352] UdevLog.txt
apport information ** Attachment added: "UdevLog.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355748/+files/UdevLog.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355749/+files/WifiSyslog.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355747/+files/UdevDb.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355744/+files/ProcEnviron.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic
[Kernel-packages] [Bug 1873352] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355745/+files/ProcInterrupts.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355743/+files/ProcCpuinfoMinimal.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355742/+files/ProcCpuinfo.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic
[Kernel-packages] [Bug 1873352] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355746/+files/ProcModules.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic
[Kernel-packages] [Bug 1873352] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware
[Kernel-packages] [Bug 1873352] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355739/+files/Lspci.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] NonfreeKernelModules.txt
apport information ** Attachment added: "NonfreeKernelModules.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355741/+files/NonfreeKernelModules.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] BootDmesg.txt
apport information ** Attachment added: "BootDmesg.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355736/+files/BootDmesg.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355740/+files/Lsusb.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1873352] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355738/+files/CurrentDmesg.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic
[Kernel-packages] [Bug 1873352] [NEW] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2
Public bug reported: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.127.24 RfKill: Error: [Errno 2] No such file or directory Tags: trusty uec-images Uname: Linux 4.15.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 10/02/2018 dmi.bios.vendor: HPE dmi.bios.version: A40 dmi.board.name: ProLiant DL385 Gen10 dmi.board.vendor: HPE dmi.chassis.type: 23 dmi.chassis.vendor: HPE dmi.modalias: dmi:bvnHPE:bvrA40:bd10/02/2018:svnHPE:pnProLiantDL385Gen10:pvr:rvnHPE:rnProLiantDL385Gen10:rvr:cvnHPE:ct23:cvr:
[Kernel-packages] [Bug 1873352] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1873352/+attachment/5355737/+files/CRDA.txt -- 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/1873352 Title: unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 Status in linux package in Ubuntu: Confirmed Bug description: Hello, We recently encountered an issue when trying to stop nova instances. | Apr 16 09:35:10 ginzel kernel: [6925958.071665] unregister_netdevice: waiting for tape3e33cb9-d6 to become free. Usage count = 2 When I try to stop manually the qemu process, it errors """ ballot@ginzel:~$ sudo virsh destroy instance-000718af setlocale: No such file or directory error: Failed to destroy domain instance-000718af error: Failed to terminate process 20953 with SIGKILL: Device or resource busy """ The qemu process is in D state because of this """ libvirt+ 20953 12.9 0.5 9001400 2925908 ? DApr15 84:25 /usr/bin/qemu-system-x86_64 -name instance-000718af -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu EPYC-IBPB-2.0,+perfctr_nb,+perfctr_core,+t opoext,+tce,+wdt,+skinit,+extapic,+cmp_legacy,+osxsave,+ht -m 4096 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid 020ecf87-4c96-47af-8d3f-d86d51b445f4 -smbios type=1,manufacturer=OpenStack Foundati on,product=OpenStack Nova,version=2014.1.5,serial=993710e9-0a44-428e-88ec-9210c6dfed55,uuid=020ecf87-4c96-47af-8d3f-d86d51b445f4 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/q emu/instance-000718af.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device pii x3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/disk,if=none,id=drive-virtio-disk0,format=qcow2,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0 ,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -netdev tap,fd=24,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:eb:99:5e,bus=pci.0,addr=0x3 -chardev f ile,id=charserial0,path=/srv/nova/instances/020ecf87-4c96-47af-8d3f-d86d51b445f4/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,i d=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x5 ballot@ginzel:~$ sudo cat /proc/20953/sta stack statstatm status """ and we can see the stack of the process """ ballot@ginzel:~$ sudo cat /proc/20953/stack [<0>] msleep+0x2d/0x40 [<0>] netdev_run_todo+0x11c/0x320 [<0>] rtnl_unlock+0xe/0x10 [<0>] tun_chr_close+0x28/0x30 [<0>] __fput+0xea/0x220 [<0>] fput+0xe/0x10 [<0>] task_work_run+0x9d/0xc0 [<0>] exit_to_usermode_loop+0xc0/0xd0 [<0>] do_syscall_64+0x115/0x130 [<0>] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [<0>] 0x """ Will attach the relevant files --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 27 05:43 seq crw-rw 1 root audio 116, 33 Jan 27 05:43 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.14.1-0ubuntu3.29 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 14.04 IwConfig: Error: [Errno 2] No such file or directory MachineType: HPE ProLiant DL385 Gen10 Package: linux (not installed) PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=06e712a9-0adb-4078-8976-0c41ce346aa5 ro console=tty0 console=ttyS0,115200 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A
[Kernel-packages] [Bug 1767611] Re: ath10k_pci crash leading to unstable wifi on 18.04
I believe I am seeing the same issue on 20.04: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611 -- 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/1767611 Title: ath10k_pci crash leading to unstable wifi on 18.04 Status in linux package in Ubuntu: Invalid Bug description: Ubuntu 18.04. mitch@mitch-YOGA:~$ uname -a Linux mitch-YOGA 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Same laptop, device, working fine on 17.10. No crashes, stable wifi. Apr 28 12:11:09 mitch-YOGA kernel: [12303.503506] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready Apr 28 12:12:04 mitch-YOGA kernel: [12359.164491] ath10k_pci :01:00.0: failed to set 5g txpower 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164498] ath10k_pci :01:00.0: failed to setup tx power 20: -11 Apr 28 12:12:04 mitch-YOGA kernel: [12359.164503] ath10k_pci :01:00.0: failed to recalc tx power: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236455] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236460] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:08 mitch-YOGA kernel: [12362.236488] wlp1s0: deauthenticating from 54:a0:50:d8:ca:00 by local choice (Reason: 3=DEAUTH_LEAVING) Apr 28 12:12:11 mitch-YOGA kernel: [12365.308434] ath10k_pci :01:00.0: failed to set inactivity time for vdev 0: -11 Apr 28 12:12:11 mitch-YOGA kernel: [12365.308441] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380355] ath10k_pci :01:00.0: failed to set PS Mode 0 for vdev 0: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380360] ath10k_pci :01:00.0: failed to setup powersave: -11 Apr 28 12:12:14 mitch-YOGA kernel: [12368.380366] ath10k_pci :01:00.0: failed to setup ps on vdev 0: -11 Apr 28 12:12:19 mitch-YOGA kernel: [12373.500277] ath10k_pci :01:00.0: failed to flush transmit queue (skip 0 ar-state 1): 0 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572243] ath10k_pci :01:00.0: failed to install key for vdev 0 peer 54:a0:50:d8:ca:00: -11 Apr 28 12:12:22 mitch-YOGA kernel: [12376.572251] wlp1s0: failed to remove key (0, 54:a0:50:d8:ca:00) from hardware (-11) Apr 28 12:12:25 mitch-YOGA kernel: [12379.644315] ath10k_pci :01:00.0: failed to delete peer 54:a0:50:d8:ca:00 for vdev 0: -11 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644328] ath10k_pci :01:00.0: found sta peer 54:a0:50:d8:ca:00 (ptr id 133) entry on vdev 0 after it was supposedly removed Apr 28 12:12:25 mitch-YOGA kernel: [12379.644457] WARNING: CPU: 0 PID: 757 at /build/linux-5s7Xkn/linux-4.15.0/net/mac80211/sta_info.c:1001 __sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA kernel: [12379.644460] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) rfcomm ccm arc4 bnep snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic btusb btrtl hid_sensor_accel_3d btbcm btintel bluetooth uvcvideo hid_sensor_als hid_sensor_trigger videobuf2_vmalloc industrialio_triggered_buffer kfifo_buf videobuf2_memops hid_sensor_iio_common videobuf2_v4l2 ecdh_generic industrialio videobuf2_core hid_sensor_custom videodev joydev media nls_iso8859_1 hid_sensor_hub hid_multitouch snd_soc_skl snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep ath10k_pci intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_pcm ath10k_core kvm_intel Apr 28 12:12:25 mitch-YOGA kernel: [12379.644566] ath kvm mac80211 irqbypass snd_seq_midi crct10dif_pclmul snd_seq_midi_event crc32_pclmul cfg80211 ghash_clmulni_intel snd_rawmidi pcbc snd_seq aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_cstate intel_rapl_perf input_leds snd_seq_device snd_timer wmi_bmof serio_raw intel_wmi_thunderbolt snd idma64 virt_dma soundcore mei_me mei processor_thermal_device shpchp int340x_thermal_zone intel_lpss_pci intel_pch_thermal intel_lpss intel_soc_dts_iosf ideapad_laptop sparse_keymap mac_hid int3400_thermal acpi_thermal_rel acpi_pad tpm_crb sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core i2c_hid wmi hid video Apr 28 12:12:25 mitch-YOGA kernel: [12379.644694] CPU: 0 PID: 757 Comm: NetworkManager Tainted: GW OE4.15.0-20-generic #21-Ubuntu Apr 28 12:12:25 mitch-YOGA kernel: [12379.644697] Hardware name: LENOVO 80VF/LNVNB161216, BIOS 2JCN39WW 05/31/2017 Apr 28 12:12:25 mitch-YOGA kernel: [12379.644741] RIP: 0010:__sta_info_destroy_part2+0x169/0x170 [mac80211] Apr 28 12:12:25 mitch-YOGA
[Kernel-packages] [Bug 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2
I am using OpenWRT on my WRT120AC AP. It is a shame there are no fixes for this issue. How can I contribute for finding a solution for this? Any ideas? -- 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/1872351 Title: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2 Status in linux package in Ubuntu: Confirmed Bug description: I have multiple issues with wifi on my Dell XPS 9380. This error was triggered when I tried to disable my wifi. [ 3634.322471] [ cut here ] [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 __sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device ucsi_acpi typec_ucsi mei_me intel_rapl_common [ 3634.322564] intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 12/11/2019 [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282 [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: [ 3634.322640] RDX: 90061ba3c740 RSI: RDI: 900613a62f48 [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 0004 [ 3634.322642] R10: R11: R12: 900613f28000 [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 900613a60d68 [ 3634.322644] FS: 7f596b396240() GS:90061e4c() knlGS: [ 3634.322645] CS: 0010 DS: ES: CR0: 80050033 [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 003606e0 [ 3634.322647] Call Trace: [ 3634.322670] __sta_info_flush+0x128/0x180 [mac80211] [ 3634.322696] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] [ 3634.322719] ieee80211_mgd_deauth+0x104/0x490 [mac80211] [ 3634.322743] ieee80211_deauth+0x18/0x20 [mac80211] [ 3634.322782] cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211] [ 3634.322804] cfg80211_mlme_down+0x66/0x80 [cfg80211] [ 3634.322823] cfg80211_disconnect+0x127/0x1e0 [cfg80211] [ 3634.322827] ? _raw_spin_unlock_bh+0x1e/0x20 [ 3634.322845] __cfg80211_leave+0x133/0x1b0 [cfg80211] [ 3634.322862] cfg80211_leave+0x2c/0x40 [cfg80211] [ 3634.322879] cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211] [ 3634.322902] ? ath10k_warn.cold+0x1a/0x1f [ath10k_core] [ 3634.322911] ? ath10k_config_ps+0x52/0x70 [ath10k_core] [ 3634.322913] ? rtnl_is_locked+0x15/0x20 [ 3634.322917] ? inetdev_event+0x47/0x560 [ 3634.322919] ? skb_dequeue+0x5a/0x70 [ 3634.322923] notifier_call_chain+0x55/0x80 [ 3634.322925] raw_notifier_call_chain+0x16/0x20 [ 3634.322927] call_netdevice_notifiers_info+0x2e/0x60 [ 3634.322929] __dev_close_many+0x63/0x120 [ 3634.322931] dev_close_many+0x91/0x150 [ 3634.322933] dev_close.part.0+0x4a/0x70 [ 3634.322936] dev_close+0x18/0x20 [ 3634.322955]
[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
I have traced it to int3403_thermal module. If I do rmmod int3403_thermal - the thermal_zone3 goes away an no thermal shutdown is happening. I can use it as a workaround - but is it dangerous for the HW? https://github.com/torvalds/linux/blob/master/drivers/thermal/intel/int340x_thermal/int3403_thermal.c >From what I see in the source, it is probably related to battery or charger or both. So I guess thermald should take this sensor into acccount when throttling? When I quickly modprobe int3403_thermal back, the full output is here (it is seen that temp is 79C, which is really close to the critical 80C): thermal_zone3$ grep . * available_policies:power_allocator user_space step_wise bang_bang fair_share grep: emul_temp: Permission denied integral_cutoff:0 k_d:0 k_i:0 k_po:0 k_pu:0 offset:0 policy:user_space grep: power: Is a directory slope:0 grep: subsystem: Is a directory sustainable_power:0 temp:79000 trip_point_0_hyst:2000 trip_point_0_temp:0 trip_point_0_type:passive trip_point_1_hyst:2000 trip_point_1_temp:0 trip_point_1_type:passive trip_point_2_hyst:2000 trip_point_2_temp:8 trip_point_2_type:critical trip_point_3_hyst:2000 trip_point_3_temp:75000 trip_point_3_type:hot trip_point_4_hyst:2000 trip_point_4_temp:65000 trip_point_4_type:passive trip_point_5_hyst:2000 trip_point_5_temp:6 trip_point_5_type:active trip_point_6_hyst:2000 trip_point_6_temp:5 trip_point_6_type:active trip_point_7_hyst:2000 trip_point_7_temp:4 trip_point_7_type:active type:SEN4 -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1872351] Re: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2
I believe this is the same issue: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767611 -- 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/1872351 Title: Qualcomm Atheros QCA6174 Killer 1435 Wireless-AC: Disabling wifi causes kernel warning in __sta_info_destroy_part2 Status in linux package in Ubuntu: Confirmed Bug description: I have multiple issues with wifi on my Dell XPS 9380. This error was triggered when I tried to disable my wifi. [ 3634.322471] [ cut here ] [ 3634.322524] WARNING: CPU: 3 PID: 1188 at net/mac80211/sta_info.c:1057 __sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322525] Modules linked in: rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm typec_displayport cmac algif_hash algif_skcipher af_alg bnep binfmt_misc nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_hdmi dell_laptop snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_nhlt snd_hda_codec snd_hda_core snd_usb_audio ath10k_pci x86_pkg_temp_thermal snd_usbmidi_lib snd_seq_midi snd_hwdep snd_seq_midi_event ath10k_core intel_powerclamp coretemp cdc_ether snd_rawmidi usbnet btusb kvm_intel r8152 ath btrtl mii btbcm kvm snd_seq uvcvideo videobuf2_vmalloc btintel videobuf2_memops intel_cstate videobuf2_v4l2 joydev snd_seq_device snd_pcm dell_wmi intel_rapl_perf videobuf2_common bluetooth mac80211 dell_smbios videodev snd_timer dcdbas mc input_leds ecdh_generic ecc wmi_bmof snd dell_wmi_descriptor serio_raw intel_wmi_thunderbolt cfg80211 soundcore rtsx_pci_ms libarc4 memstick hid_multitouch processor_thermal_device ucsi_acpi typec_ucsi mei_me intel_rapl_common [ 3634.322564] intel_xhci_usb_role_switch mei typec intel_soc_dts_iosf intel_pch_thermal roles int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad intel_hid acpi_thermal_rel sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mmc_block dm_crypt usbhid hid_generic crct10dif_pclmul crc32_pclmul rtsx_pci_sdmmc i915 ghash_clmulni_intel aesni_intel crypto_simd cryptd i2c_algo_bit glue_helper drm_kms_helper psmouse syscopyarea sysfillrect nvme sysimgblt i2c_i801 fb_sys_fops nvme_core drm intel_lpss_pci rtsx_pci intel_lpss idma64 i2c_hid virt_dma wmi hid pinctrl_sunrisepoint video pinctrl_intel [ 3634.322599] CPU: 3 PID: 1188 Comm: NetworkManager Tainted: G OE 5.4.0-21-generic #25-Ubuntu [ 3634.322600] Hardware name: Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.12.1 12/11/2019 [ 3634.322633] RIP: 0010:__sta_info_destroy_part2+0x14e/0x160 [mac80211] [ 3634.322635] Code: 24 0c 01 00 00 00 0f 84 52 ff ff ff 45 31 c0 b9 01 00 00 00 4c 89 e2 48 89 de 4c 89 ef e8 0a a6 ff ff 85 c0 0f 84 34 ff ff ff <0f> 0b e9 2d ff ff ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 [ 3634.322636] RSP: 0018:a70c009c3918 EFLAGS: 00010282 [ 3634.322638] RAX: ff94 RBX: 9006104cc8c0 RCX: [ 3634.322640] RDX: 90061ba3c740 RSI: RDI: 900613a62f48 [ 3634.322641] RBP: a70c009c3938 R08: 90061e4d78c8 R09: 0004 [ 3634.322642] R10: R11: R12: 900613f28000 [ 3634.322643] R13: 900613a607a0 R14: 9006104cc8c0 R15: 900613a60d68 [ 3634.322644] FS: 7f596b396240() GS:90061e4c() knlGS: [ 3634.322645] CS: 0010 DS: ES: CR0: 80050033 [ 3634.322646] CR2: 0db00945f000 CR3: 000494824005 CR4: 003606e0 [ 3634.322647] Call Trace: [ 3634.322670] __sta_info_flush+0x128/0x180 [mac80211] [ 3634.322696] ieee80211_set_disassoc+0xc0/0x5f0 [mac80211] [ 3634.322719] ieee80211_mgd_deauth+0x104/0x490 [mac80211] [ 3634.322743] ieee80211_deauth+0x18/0x20 [mac80211] [ 3634.322782] cfg80211_mlme_deauth+0xb6/0x1e0 [cfg80211] [ 3634.322804] cfg80211_mlme_down+0x66/0x80 [cfg80211] [ 3634.322823] cfg80211_disconnect+0x127/0x1e0 [cfg80211] [ 3634.322827] ? _raw_spin_unlock_bh+0x1e/0x20 [ 3634.322845] __cfg80211_leave+0x133/0x1b0 [cfg80211] [ 3634.322862] cfg80211_leave+0x2c/0x40 [cfg80211] [ 3634.322879] cfg80211_netdev_notifier_call+0x1b2/0x590 [cfg80211] [ 3634.322902] ? ath10k_warn.cold+0x1a/0x1f [ath10k_core] [ 3634.322911] ? ath10k_config_ps+0x52/0x70 [ath10k_core] [ 3634.322913] ? rtnl_is_locked+0x15/0x20 [ 3634.322917] ? inetdev_event+0x47/0x560 [ 3634.322919] ? skb_dequeue+0x5a/0x70 [ 3634.322923] notifier_call_chain+0x55/0x80 [ 3634.322925] raw_notifier_call_chain+0x16/0x20 [ 3634.322927] call_netdevice_notifiers_info+0x2e/0x60 [ 3634.322929] __dev_close_many+0x63/0x120 [ 3634.322931] dev_close_many+0x91/0x150 [ 3634.322933] dev_close.part.0+0x4a/0x70 [ 3634.322936] dev_close+0x18/0x20 [ 3634.322955] cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211] [ 3634.322971]
[Kernel-packages] [Bug 1872984] Blacklisting rtw_pci and rtwpci
After adding rtw_pci to /etc/modprobe.d/blacklist.conf , running "sudo depmod -a" and "sudo update-initramfs -u -k '5.6.0-8-generic'" and rebooting, rtw_pci was loaded by the other driver "rtwpci". Adding "rtwpci" to the blacklist and rebooting, "lspci -vvnn" gives a proper output for the network device. However, with disabling these two drivers there is zero internet functionality since the device does not have a driver associated with it and the kernel does not have one available to load, of course. Attached is both the dmesg and lspci outputs from when both of these modules were blacklisted. I was expecting the kernel to load the old realtek network driver 'rtlwifi' instead, but I guess it is no longer installed. ** Attachment added: "dmesg-5.6.0-8-blacklist-rtw_pci.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355733/+files/dmesg-5.6.0-8-blacklist-rtw_pci.log ** Attachment added: "lspci-vvnn-blacklist-rtw_pci.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355734/+files/lspci-vvnn-blacklist-rtw_pci.log -- 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/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774]
[Kernel-packages] [Bug 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
By the way, these are the types I get: /sys/class/thermal/thermal_zone0/type:acpitz /sys/class/thermal/thermal_zone1/type:SEN2 /sys/class/thermal/thermal_zone2/type:SEN3 /sys/class/thermal/thermal_zone3/type:SEN4 /sys/class/thermal/thermal_zone4/type:B0D4 /sys/class/thermal/thermal_zone5/type:iwlwifi_1 /sys/class/thermal/thermal_zone6/type:x86_pkg_temp thermal_zone3, which causes most shutdowns, is actually not a CPU core - it's value doesn't match any of the values shown by the sensors command. What could be the mysterious SEN4? How can I trace it further? Moreover, the thermal shutdown is more easily reproduced when laptop is charging (battery below 100%) on AC power. -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
Marking the linux package invalid as this is clearly a busted test ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+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 1864140] Re: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC
After looking @ lp#1840904 This looks like its nameresolv issue in the lab in which the power machine resides. I'll have to deploy one in order to fix this and find out whats causing it. ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Sean Feole (sfeole) ** Changed in: ubuntu-kernel-tests Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1864140 Title: ubuntu_fan_smoke_test failed with unable to fetch file from http://ports.ubuntu.com on PowerPC Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Bug description: Issue found on PowerPC nodes across different kernels. (It works on other arches in different MAAS server, so it looks like some network config issue) Running in the Canonical CI environment Testing Fan Networking (pre-0.13.0 API) docker pull ppc64le/ubuntu: PASSED enable disable fan test: PASSED fanctl show test: PASSED fanctl check bridge config test: PASSED fanatic docker test: FAILED: (docker run returned 100) stderr: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic/InRelease Could not connect to ports.ubuntu.com:80 (91.189.88.150), connection timed out W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-updates/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-backports/InRelease Unable to connect to ports.ubuntu.com:http: W: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/bionic-security/InRelease Unable to connect to ports.ubuntu.com:http: W: Some index files failed to download. They have been ignored, or old ones used instead. E: Unable to locate package iputils-ping ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-174-generic 4.4.0-174.204 ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211 Uname: Linux 4.4.0-174-generic ppc64le AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Feb 21 03:32 seq crw-rw 1 root audio 116, 33 Feb 21 03:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.21 Architecture: ppc64el ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: Date: Fri Feb 21 03:47:15 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: root=UUID=faf7d4a6-6836-4496-bc64-15f33ec9e43d ro console=hvc0 ProcLoadAvg: 1.28 1.27 0.97 1/1305 17149 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -1 ProcVersion: Linux version 4.4.0-174-generic (buildd@bos02-ppc64el-008) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.12) ) #204-Ubuntu SMP Wed Jan 29 06:41:38 UTC 2020 RelatedPackageVersions: linux-restricted-modules-4.4.0-174-generic N/A linux-backports-modules-4.4.0-174-generic N/A linux-firmware 1.157.22 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 120) max: 3.694 GHz (cpu 37) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1864140/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
By the way, I have only one thermal_zone with mode file in it - thermal_zone0 (other don't have mode) If I do: sudo echo "disabled" > /sys/class/thermal/thermal_zone0/mode I get: Permission denied The thermal zones that usually cause the shutdown is thermal_zone3 and thermal_zone4 (rarely) -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1873083] Re: Lenovo Yoga C940 frequently does thermal shutdown
If I start thermald service, I still can reproduce thermal shutdown relatively easily. What is cryptic is that while I monitor the sensors, CPU core temps are around 85deg, but when shutdown happens it says that critical value was 80C. Where does this difference come from? Laptop runs above 80C for quite some time before it shuts down... -- 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/1873083 Title: Lenovo Yoga C940 frequently does thermal shutdown Status in linux package in Ubuntu: Incomplete Status in thermald package in Ubuntu: New Bug description: On a bit higher load and especially if Laptop is charging, very often Kernel does an emergency thermal shutdown. thermal thermal_zone3: critical temperature reached (80 C), shutting down It says 80 C, but sensors command shows that temperatures hovering close to 100C before the shutdown happens. dmesg is often also full of these (for each core): mce: CPU2: Core temperature above threshold, cpu clock throttled (total events = 246766) When I boot to Windows, it seems that CPU is throttled more aggressively on load and thermal shutdown doesn't happen with a similar load, but CPU frequencies drop to 1600 range, while in Ubuntu they are 2800 range. I would rather have more throttling that computer shutting down randomly without the ability to save work. Is there a workaround? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: anton 1874 F pulseaudio /dev/snd/pcmC0D0p: anton 1874 F...m pulseaudio /dev/snd/pcmC0D6c: anton 1874 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 23:54:21 2020 InstallationDate: Installed on 2019-11-29 (137 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q9 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=24af2874-e109-44f9-a5b9-8a9ce34b3f0f ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-04 (11 days ago) dmi.bios.date: 01/09/2020 dmi.bios.vendor: LENOVO dmi.bios.version: AUCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga C940-14IIL dmi.modalias: dmi:bvnLENOVO:bvrAUCN54WW:bd01/09/2020:svnLENOVO:pn81Q9:pvrLenovoYogaC940-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaC940-14IIL: dmi.product.family: Yoga C940-14IIL dmi.product.name: 81Q9 dmi.product.sku: LENOVO_MT_81Q9_BU_idea_FM_Yoga C940-14IIL dmi.product.version: Lenovo Yoga C940-14IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873083/+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 1850654] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355694/+files/UdevDb.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355691/+files/ProcModules.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355693/+files/RfKill.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355692/+files/PulseList.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355682/+files/CRDA.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355683/+files/CurrentDmesg.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355690/+files/ProcInterrupts.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355689/+files/ProcEnviron.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355685/+files/Lspci.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355695/+files/WifiSyslog.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355684/+files/IwConfig.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Today, I manage to execute "apport-collect 1850654". avdzm@dell5575:~$ apport-collect 1850654 The authorization page: (https://launchpad.net/+authorize-token?oauth_token=79jd1C38BFnNwrtzWtM3_permission=DESKTOP_INTEGRATION) should be opening in your browser. Use your browser to authorize this program to access Launchpad on your behalf. Waiting to hear from Launchpad about your decision... Gtk-Message: 20:31:03.699: GtkDialog mapped without a transient parent. This is discouraged. dpkg-query: no packages found matching linux dpkg-query: no packages found matching linux I hope it was successful and that it helps. -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355687/+files/ProcCpuinfo.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355686/+files/Lsusb.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355688/+files/ProcCpuinfoMinimal.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1850654/+attachment/5355681/+files/AlsaInfo.txt -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1850654] Re: update-initramfs complains of missing amdgpu firmware files
ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: avdzm 2061 F pulseaudio /dev/snd/pcmC1D0p: avdzm 2061 F...m pulseaudio /dev/snd/controlC0: avdzm 2061 F pulseaudio /dev/snd/timer: avdzm 2061 f pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-10 (6 days ago) InstallationMedia: Kubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Dell Inc. Inspiron 5575 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-47-generic root=UUID=a3475952-40a9-47d1-9770-c3e923939eaf ro quiet splash iommu=soft amd_iommu=soft nouveau.modeset=0 radeon.si_support=0 radeon.cik_support=0 amdgpu.si_support=1 amdgpu.cik_support=1 amdgpu.dc=1 amdgpu.dpm=1 amdgpu.modeset=1 noapic vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-47.39~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-47-generic N/A linux-backports-modules-5.3.0-47-generic N/A linux-firmware1.173.17 Tags: bionic Uname: Linux 5.3.0-47-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/31/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.asset.tag: not specified dmi.board.name: 05Y1V6 dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.3.3 dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd10/31/2019:svnDellInc.:pnInspiron5575:pvr1.3.3:rvnDellInc.:rn05Y1V6:rvrX01:cvnDellInc.:ct10:cvr1.3.3: dmi.product.family: Inspiron dmi.product.name: Inspiron 5575 dmi.product.sku: 0812 dmi.product.version: 1.3.3 dmi.sys.vendor: Dell Inc. ** Tags added: apport-collected bionic -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Ok. Can you please blacklist rtw_pci and attach `sudo lspci -vv` again? -- 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/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error occurs when attempting to turn on/off wifi in settings:
[Kernel-packages] [Bug 1873325] Re: update-initramfs complains of missing amdgpu firmware files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-firmware (Ubuntu) Status: New => Confirmed -- 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/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux-firmware package in Ubuntu: Confirmed Bug description: Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+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 1873325] [NEW] update-initramfs complains of missing amdgpu firmware files
Public bug reported: Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux-firmware package in Ubuntu: New Bug description: Ubuntu 20.04 during initramfs update reports missing firmware files: W: Possible missing firmware /lib/firmware/amdgpu/navi12_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_vcn.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi12_smc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/arcturus_smc.bin for module amdgpu Kernel: 5.4.0-24-generic linux-firmware: 1.187 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1873325/+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 1872984] Testing on 5.6.0-8-generic #8~lp1872984
The crash also occurs in the kernel version 5.6.0-8-generic #8~lp1872984 linked above; however, two distinct behaviors are present depending on whether or not wifi was ON/OFF in NetworkManager. If it was enabled previously, and then the machine is powered off and back on, the driver appears to send an auth to the default network before crashing (explained below, c.f. attached dmesg logs). Regardless, it will crash and fail to power on if it is turned off and back on in NetworkManager.Case 1 (on): Boot 1: (Was connected to network on kernel 5.4.0-18, powered off device, then powered on and changed kernel to 5.6.0lp in grub) - The network driver successfully authed with the default network and I was even able to ping google.com. After turning wifi off and then back on again, the network driver is unable to scan for networks and shows a crash in dmesg (dmesg-auth1.log) Boot 2: (Powered off and restarted after previous attempt, no settings changed) The network driver appeared to auth in dmesg with the specified network then immediately crash. Attempts to turn OFF/ON again in networkmanager result in "fail to power on mac" error in dmesg (dmesg-auth2.log)Case 2 (off): Boot 3: (Turned off wifi in NetworkManager after boot 2, then powered off and restarted machine) Network driver crashes after enabled on boot and fails to power on when turning off/on in networkmanager (c.f. [5.611939] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0) (dmesg-lp-crash.log) ** Attachment added: "dmesg-auth1.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355668/+files/dmesg-auth1.log ** Attachment added: "dmesg-auth2.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355669/+files/dmesg-auth2.log ** Attachment added: "dmesg-lp-crash.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355670/+files/dmesg-lp-crash.log ** Attachment added: "lspci-vvnn-5.6.0-8-lp1872984.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355671/+files/lspci-vvnn-5.6.0-8-lp1872984.log ** Attachment added: "uname-a-5.6.0-8.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355672/+files/uname-a-5.6.0-8.log ** Attachment added: "version-5.6.0-8.log" https://bugs.launchpad.net/bugs/1872984/+attachment/5355673/+files/version-5.6.0-8.log -- 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/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Incomplete Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699]
[Kernel-packages] [Bug 1873315] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873315 Title: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. Status in linux package in Ubuntu: Confirmed Bug description: I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315/+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 1873315] [NEW] 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.
Public bug reported: I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873315 Title: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. Status in linux package in Ubuntu: New Bug description: I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell
[Kernel-packages] [Bug 1873313] [NEW] linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo
Public bug reported: The most recent kernel updates resulted in... ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-image-generic5.4.0.24.29 amd64Generic Linux kernel image where the 5.4.0.24.29 build of linux-image-5.4.0-24-generic didn't get moved into the repository. Likewise we have... ii linux-headers-5.4.0-24 5.4.0-24.28 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-libc-dev:amd64 5.4.0-24.28 amd64Linux Kernel Headers for development ii linux-modules-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1873313 Title: linux-image-5.4.0-24-generic 5.4.0.24.29 missing from repo Status in linux-signed package in Ubuntu: New Bug description: The most recent kernel updates resulted in... ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-image-generic5.4.0.24.29 amd64Generic Linux kernel image where the 5.4.0.24.29 build of linux-image-5.4.0-24-generic didn't get moved into the repository. Likewise we have... ii linux-headers-5.4.0-24 5.4.0-24.28 all Header files related to Linux kernel version 5.4.0 ii linux-headers-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel headers for version 5.4.0 on 64 bit x86 SMP ii linux-image-5.4.0-24-generic 5.4.0-24.28 amd64Signed kernel image generic ii linux-libc-dev:amd64 5.4.0-24.28 amd64Linux Kernel Headers for development ii linux-modules-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP ii linux-modules-extra-5.4.0-24-generic 5.4.0-24.28 amd64Linux kernel extra modules for version 5.4.0 on 64 bit x86 SMP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1873313/+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 1873292] [NEW] Focal update: v5.4.32 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.32 upstream stable release
from git://git.kernel.org/
net: phy: realtek: fix handling of RTL8105e-integrated PHY
cxgb4: fix MPS index overwrite when setting MAC address
ipv6: don't auto-add link-local address to lag ports
net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
net: dsa: bcm_sf2: Ensure correct sub-node is parsed
net: dsa: mt7530: fix null pointer dereferencing in port5 setup
net: phy: micrel: kszphy_resume(): add delay after genphy_resume() before
accessing PHY registers
net_sched: add a temporary refcnt for struct tcindex_data
net_sched: fix a missing refcnt in tcindex_init()
net: stmmac: dwmac1000: fix out-of-bounds mac address reg setting
tun: Don't put_page() for all negative return values from XDP program
mlxsw: spectrum_flower: Do not stop at FLOW_ACTION_VLAN_MANGLE
r8169: change back SG and TSO to be disabled by default
s390: prevent leaking kernel address in BEAR
random: always use batched entropy for get_random_u{32,64}
usb: dwc3: gadget: Wrap around when skip TRBs
uapi: rename ext2_swab() to swab() and share globally in swab.h
slub: improve bit diffusion for freelist ptr obfuscation
tools/accounting/getdelays.c: fix netlink attribute length
hwrng: imx-rngc - fix an error path
ACPI: PM: Add acpi_[un]register_wakeup_handler()
platform/x86: intel_int0002_vgpio: Use acpi_register_wakeup_handler()
ASoC: jz4740-i2s: Fix divider written at incorrect offset in register
IB/hfi1: Call kobject_put() when kobject_init_and_add() fails
IB/hfi1: Fix memory leaks in sysfs registration and unregistration
IB/mlx5: Replace tunnel mpls capability bits for tunnel_offloads
ARM: imx: Enable ARM_ERRATA_814220 for i.MX6UL and i.MX7D
ARM: imx: only select ARM_ERRATA_814220 for ARMv7-A
ceph: remove the extra slashes in the server path
ceph: canonicalize server path in place
include/uapi/linux/swab.h: fix userspace breakage, use __BITS_PER_LONG for swap
RDMA/ucma: Put a lock around every call to the rdma_cm layer
RDMA/cma: Teach lockdep about the order of rtnl and lock
RDMA/siw: Fix passive connection establishment
Bluetooth: RFCOMM: fix ODEBUG bug in rfcomm_dev_ioctl
RDMA/cm: Update num_paths in cma_resolve_iboe_route error flow
blk-mq: Keep set->nr_hw_queues and set->map[].nr_queues in sync
fbcon: fix null-ptr-deref in fbcon_switch
iommu/vt-d: Allow devices with RMRRs to use identity domain
Linux 5.4.32
UBUNTU: upstream stable to v5.4.32
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Tags: kernel-stable-tracking-bug
** Changed in: linux (Ubuntu)
Status: New => Confirmed
** Tags added: kernel-stable-tracking-bug
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Description changed:
+ SRU Justification
- SRU Justification
+ Impact:
+ The upstream process for stable tree updates is quite similar
+ in scope to the Ubuntu SRU process, e.g., each patch has to
+ demonstrably fix a bug, and each patch is vetted by upstream
+ by originating either directly from a mainline/stable Linux tree or
+ a minimally backported form of that patch. The following upstream
+ stable patches should be included in the Ubuntu kernel:
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ v5.4.32 upstream stable release
+ from git://git.kernel.org/
-v5.4.32 upstream stable release
-from git://git.kernel.org/
+ net: phy: realtek: fix handling of RTL8105e-integrated PHY
+ cxgb4: fix MPS index overwrite when setting MAC address
+ ipv6: don't auto-add link-local address to lag ports
+ net: dsa: bcm_sf2: Do not register slave MDIO bus with OF
+ net: dsa: bcm_sf2: Ensure correct sub-node is parsed
+ net: dsa: mt7530: fix null pointer dereferencing
