[Kernel-packages] [Bug 1880266] Re: console-setup defaults prevent using automatic highdpi fonts
** Package changed: linux (Ubuntu) => console-setup (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/1880266 Title: console-setup defaults prevent using automatic highdpi fonts Status in console-setup package in Ubuntu: Incomplete Bug description: console-setup defaults prevent using automatic highdpi fonts Kernel has built-in Terminus fonts, at multiple sizes, and it picks font based on screen resolution, including selecting high-dpi version of the font. The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15 results in tiny font getting set on high-dpi laptops. Dropping this setting, makes fonts to be of correct size on highdpi screens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1880266/+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 1880266] 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 1880266 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880266 Title: console-setup defaults prevent using automatic highdpi fonts Status in linux package in Ubuntu: Incomplete Bug description: console-setup defaults prevent using automatic highdpi fonts Kernel has built-in Terminus fonts, at multiple sizes, and it picks font based on screen resolution, including selecting high-dpi version of the font. The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15 results in tiny font getting set on high-dpi laptops. Dropping this setting, makes fonts to be of correct size on highdpi screens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880266/+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 1860501] Re: Middle-click button suddenly appears right in the middle of my touchpad
[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/1860501 Title: Middle-click button suddenly appears right in the middle of my touchpad Status in linux package in Ubuntu: Expired Bug description: Since one of the last updates, about three days or so, I have got middle-click button right in the middle of my touchpad without any ability to disable it. I use taps for clicks, so it often mix up with regular left-clicks, and it is very annoying. Xubuntu 18.04 LTS amd64 on Acer Aspire V3 551G ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: kernel-common (not installed) ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Jan 22 10:15:28 2020 InstallationDate: Installed on 2019-06-28 (207 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: kernel-package UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mrrabbit 1411 F pulseaudio /dev/snd/controlC0: mrrabbit 1411 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-06-28 (269 days ago) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Acer Aspire V3-551G Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=3c394265-461d-4c60-a689-c850925b8fd5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-42-generic N/A linux-backports-modules-5.3.0-42-generic N/A linux-firmware1.183.4 Tags: eoan Uname: Linux 5.3.0-42-generic x86_64 UpgradeStatus: Upgraded to eoan on 2020-02-10 (42 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/24/2012 dmi.bios.vendor: Acer dmi.bios.version: V2.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: VA50_CM dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAcer:bvrV2.02:bd08/24/2012:svnAcer:pnAspireV3-551G:pvrV2.02:rvnAcer:rnVA50_CM:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Aspire dmi.product.name: Aspire V3-551G dmi.product.sku: Q5WV8_0696_V2.02 dmi.product.version: V2.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860501/+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 1868590] Re: VFS cannot open root device "sdc"
[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/1868590 Title: VFS cannot open root device "sdc" Status in linux package in Ubuntu: Expired Bug description: vfs: cannot open root device "sdc" or unknown-block(0,0): error -6 kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) this happened after upgrading the linux kernel 5.3.0-40 to 5.3.0-42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1868590/+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 1880266] [NEW] console-setup defaults prevent using automatic highdpi fonts
Public bug reported: console-setup defaults prevent using automatic highdpi fonts Kernel has built-in Terminus fonts, at multiple sizes, and it picks font based on screen resolution, including selecting high-dpi version of the font. The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15 results in tiny font getting set on high-dpi laptops. Dropping this setting, makes fonts to be of correct size on highdpi screens. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880266 Title: console-setup defaults prevent using automatic highdpi fonts Status in linux package in Ubuntu: New Bug description: console-setup defaults prevent using automatic highdpi fonts Kernel has built-in Terminus fonts, at multiple sizes, and it picks font based on screen resolution, including selecting high-dpi version of the font. The autogenerated default of FONTFACE=VGA and FONTSIZE=16 for Lat15 results in tiny font getting set on high-dpi laptops. Dropping this setting, makes fonts to be of correct size on highdpi screens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880266/+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 1879760] Re: PCI/internal sound card not detected
** This bug is no longer a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879760 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: after updating ubuntu kernel pc cant detect sound its show dummy output but when i select from boot previous kernel the sound working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 21:20:11 2020 InstallationDate: Installed on 2020-05-10 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/03/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879760/+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 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug is no longer a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- 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/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+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 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
Odd Behavior of this Bug: 1. The audio device is not detected (not by gnome and not by lshw -C multimedia) and won't play sounds unless it's the "bell" from the terminal. 2. If headphones are plugged in, there won't be an detected audio device but lightly distorted sound is played thru headphones. 2. /proc/asound/card1/codec#0 is present and readable Codec: Realtek ALC892 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0892 [...] -- 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/1879939 Title: Audio stopped working after 5.4.0-31 kernel update Status in linux package in Ubuntu: Confirmed Bug description: After rebooting following a system update where kernel 5.4.0-31 got installed, the main audio output stopped working. HDMI audio and USB headphones still work. Rebooting using the previous kernel (5.4.0-29) restores audio. Description:Ubuntu 20.04 LTS Release:20.04 log of the update that broke audio: Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31:amd64 (5.4.0-31.35) Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64 (5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeyelth1921 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 21 13:05:44 2020 HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c InstallationDate: Installed on 2017-10-29 (934 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (12 days ago) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd04/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/+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 1874465] Re: dummy output ubuntu 20.04 LTS dell inspiron 3420
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug is no longer a duplicate of bug 1875252 Ubuntu 20.04 LTS update causing no sound coming from built-in speakers ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- 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/1874465 Title: dummy output ubuntu 20.04 LTS dell inspiron 3420 Status in linux package in Ubuntu: Confirmed Bug description: in sound settings there is only dummy output, everything worked until April, 21 2020 when updated 18.04 LTS to 20.04 LTS via terminal. Description: Ubuntu 20.04 LTS Release: 20.04 alsa-base: Installed: 1.0.25+dfsg-0ubuntu5 Candidate: 1.0.25+dfsg-0ubuntu5 Version table: *** 1.0.25+dfsg-0ubuntu5 500 500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages 500 http://br.archive.ubuntu.com/ubuntu focal/main i386 Packages 100 /var/lib/dpkg/status pavucontrol: Installed: 4.0-1build1 Candidate: 4.0-1build1 Version table: *** 4.0-1build1 500 500 http://br.archive.ubuntu.com/ubuntu focal/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ploosh 1949 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 23 11:35:40 2020 InstallationDate: Installed on 2019-10-06 (199 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec870298-2798-4d1b-a6d2-6118c2078d5e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-22 (1 days ago) dmi.bios.date: 11/04/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A11 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA11:bd11/04/2013:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA11:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874465/+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 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
*** This bug is a duplicate of bug 1876065 *** https://bugs.launchpad.net/bugs/1876065 ** This bug has been marked a duplicate of bug 1876065 After unplug headphones and plug them again no sound can be heard -- 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/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+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 1879760] Re: PCI/internal sound card not detected
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 ** This bug has been marked a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879760 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Confirmed Bug description: after updating ubuntu kernel pc cant detect sound its show dummy output but when i select from boot previous kernel the sound working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 20 21:20:11 2020 InstallationDate: Installed on 2020-05-10 (10 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/03/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: RAMPAGE V EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1302:bd03/03/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnRAMPAGEVEXTREME:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879760/+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 1879939] Re: Audio stopped working after 5.4.0-31 kernel update
Hi Hui Wang, 5.4.0-33 is installed on my machines and nothing was fixed. Please keep an eye on this bug. -- 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/1879939 Title: Audio stopped working after 5.4.0-31 kernel update Status in linux package in Ubuntu: Confirmed Bug description: After rebooting following a system update where kernel 5.4.0-31 got installed, the main audio output stopped working. HDMI audio and USB headphones still work. Rebooting using the previous kernel (5.4.0-29) restores audio. Description:Ubuntu 20.04 LTS Release:20.04 log of the update that broke audio: Install: linux-image-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-extra-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-modules-5.4.0-31-generic:amd64 (5.4.0-31.35), linux-headers-5.4.0-31:amd64 (5.4.0-31.35) Upgrade: bind9-dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-headers-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), linux-libc-dev:amd64 (5.4.0-29.33, 5.4.0-31.35), linux-image-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-host:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), dnsutils:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1), linux-generic:amd64 (5.4.0.29.34, 5.4.0.31.36), bind9-libs:amd64 (1:9.16.1-0ubuntu2, 1:9.16.1-0ubuntu2.1) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zeyelth1921 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Thu May 21 13:05:44 2020 HibernationDevice: RESUME=UUID=8ede6c97-084e-4c19-b235-2ba8b2c5565c InstallationDate: Installed on 2017-10-29 (934 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/kubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-08 (12 days ago) dmi.bios.date: 04/16/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1003 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1003:bd04/16/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/+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 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879939/comments/3 Mentions, that Kernel 5.4.0-32 is going to fix the problem, which is not right. 5.4.0-33 still has the problem. ** This bug has been marked a duplicate of bug 1879939 Audio stopped working after 5.4.0-31 kernel update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+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 1879989] Re: "Failed to play sound: No such driver" ubuntu 20.04
*** This bug is a duplicate of bug 1879939 *** https://bugs.launchpad.net/bugs/1879939 Judging on the described behaviour this Bug also is present in Ubuntu 14.04 https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1879869 -- 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/1879989 Title: "Failed to play sound: No such driver" ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: my speakers- built in audio produces terrible sound I tested the speakers via settings/sound and there was no sound I checked gnome logs and found "Failed to play sound: No such driver" I checked online and it seams to be a problem that affects many users ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: regern70802 F pulseaudio /dev/snd/pcmC0D0c: regern70802 F...m pulseaudio /dev/snd/pcmC0D0p: regern70802 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 19:13:55 2020 InstallationDate: Installed on 2020-05-16 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Dell Inc. Inspiron 15-3552 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=55652357-023b-4633-8d3a-46ce1a22d378 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 4.4.0 dmi.board.name: 079W3P dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvr4.4.0:bd03/06/2018:svnDellInc.:pnInspiron15-3552:pvr4.4.0:rvnDellInc.:rn079W3P:rvrA00:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3552 dmi.product.sku: 06AC dmi.product.version: 4.4.0 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879989/+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 1879017] Re: dd caused systemd-udevd call trace
1) No, it is not appropriate to test a non LTS kernel on a LTS distribution. 2) I did you a favor and tested on the previous LTS kernel (linux- image-5.4.0-28-generic) and the latest LTS kernel (linux- image-5.4.0-31-generic) and could not reproduce on either after running dd 3-5 times on each. However, the kernel I reported on (linux-image-5.4.0-29-generic) produced the stack trace after the 2nd attempt. Maybe I didn't collect enough samples, but the point here is the previous kernel was not broken, nor is the latest. Something may be different in linux- image-5.4.0-29-generic. May 22 20:12:39 quad kernel: [ 1088.902612] INFO: task systemd-udevd:451 blocked for more than 120 seconds. May 22 20:12:39 quad kernel: [ 1088.902618] Tainted: P IOE 5.4.0-29-generic #33-Ubuntu May 22 20:12:39 quad kernel: [ 1088.902620] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 22 20:12:39 quad kernel: [ 1088.902623] systemd-udevd D0 451 1 0x4124 May 22 20:12:39 quad kernel: [ 1088.902626] Call Trace: May 22 20:12:39 quad kernel: [ 1088.902636] __schedule+0x2e3/0x740 May 22 20:12:39 quad kernel: [ 1088.902639] schedule+0x42/0xb0 May 22 20:12:39 quad kernel: [ 1088.902641] schedule_preempt_disabled+0xe/0x10 May 22 20:12:39 quad kernel: [ 1088.902644] __mutex_lock.isra.0+0x182/0x4f0 May 22 20:12:39 quad kernel: [ 1088.902649] ? exact_lock+0x11/0x20 May 22 20:12:39 quad kernel: [ 1088.902652] __mutex_lock_slowpath+0x13/0x20 May 22 20:12:39 quad kernel: [ 1088.902654] mutex_lock+0x2e/0x40 May 22 20:12:39 quad kernel: [ 1088.902658] __blkdev_get+0x78/0x550 May 22 20:12:39 quad kernel: [ 1088.902661] blkdev_get+0x3d/0x140 May 22 20:12:39 quad kernel: [ 1088.902663] ? blkdev_get_by_dev+0x50/0x50 May 22 20:12:39 quad kernel: [ 1088.902665] blkdev_open+0x8f/0xa0 May 22 20:12:39 quad kernel: [ 1088.902670] do_dentry_open+0x143/0x3a0 May 22 20:12:39 quad kernel: [ 1088.902672] vfs_open+0x2d/0x30 May 22 20:12:39 quad kernel: [ 1088.902676] do_last+0x194/0x900 May 22 20:12:39 quad kernel: [ 1088.902679] path_openat+0x8d/0x290 May 22 20:12:39 quad kernel: [ 1088.902682] do_filp_open+0x91/0x100 May 22 20:12:39 quad kernel: [ 1088.902686] ? __alloc_fd+0x46/0x150 May 22 20:12:39 quad kernel: [ 1088.902689] do_sys_open+0x17e/0x290 May 22 20:12:39 quad kernel: [ 1088.902691] __x64_sys_openat+0x20/0x30 May 22 20:12:39 quad kernel: [ 1088.902695] do_syscall_64+0x57/0x190 May 22 20:12:39 quad kernel: [ 1088.902699] entry_SYSCALL_64_after_hwframe+0x44/0xa9 May 22 20:12:39 quad kernel: [ 1088.902702] RIP: 0033:0x7f31ed7bdd1b May 22 20:12:39 quad kernel: [ 1088.902709] Code: Bad RIP value. May 22 20:12:39 quad kernel: [ 1088.902710] RSP: 002b:7ffdc7cf3f50 EFLAGS: 0246 ORIG_RAX: 0101 May 22 20:12:39 quad kernel: [ 1088.902712] RAX: ffda RBX: 7ffdc7cf4060 RCX: 7f31ed7bdd1b May 22 20:12:39 quad kernel: [ 1088.902714] RDX: 000a0800 RSI: 55f3f78a27d0 RDI: ff9c May 22 20:12:39 quad kernel: [ 1088.902715] RBP: 55f3f78a27d0 R08: 55f3f66940c0 R09: May 22 20:12:39 quad kernel: [ 1088.902716] R10: R11: 0246 R12: 000a0800 May 22 20:12:39 quad kernel: [ 1088.902717] R13: 55f3f78759d0 R14: 7ffdc7cf4028 R15: 0001 -- 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/1879017 Title: dd caused systemd-udevd call trace Status in linux package in Ubuntu: Incomplete Bug description: Using dd to copy an image onto sdcard seems to cause a kernel stack trace. dd seems to hang. [ 3747.220647] INFO: task systemd-udevd:2451 blocked for more than 483 seconds. [ 3747.220652] Tainted: P IOE 5.4.0-29-generic #33-Ubuntu [ 3747.220654] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 3747.220656] systemd-udevd D0 2451 1 0x4124 [ 3747.220660] Call Trace: [ 3747.220670] __schedule+0x2e3/0x740 [ 3747.220673] schedule+0x42/0xb0 [ 3747.220675] schedule_preempt_disabled+0xe/0x10 [ 3747.220678] __mutex_lock.isra.0+0x182/0x4f0 [ 3747.220683] ? exact_lock+0x11/0x20 [ 3747.220685] __mutex_lock_slowpath+0x13/0x20 [ 3747.220687] mutex_lock+0x2e/0x40 [ 3747.220692] __blkdev_get+0x78/0x550 [ 3747.220694] blkdev_get+0x3d/0x140 [ 3747.220697] ? blkdev_get_by_dev+0x50/0x50 [ 3747.220699] blkdev_open+0x8f/0xa0 [ 3747.220704] do_dentry_open+0x143/0x3a0 [ 3747.220706] vfs_open+0x2d/0x30 [ 3747.220710] do_last+0x194/0x900 [ 3747.220713] path_openat+0x8d/0x290 [ 3747.220716] do_filp_open+0x91/0x100 [ 3747.220720] ? __alloc_fd+0x46/0x150 [ 3747.220722] do_sys_open+0x17e/0x290 [ 3747.220724] __x64_sys_openat+0x20/0x30 [
[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
New images do not appear to be available quite yet, still getting the May 18 image. $ vagrant box update ==> default: Checking for updates to 'ubuntu/focal64' default: Latest installed version: 20200518.0.0 default: Version constraints: default: Provider: virtualbox ==> default: Box 'ubuntu/focal64' (v20200518.0.0) is running the latest version. -- 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/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders Status in cloud-images: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: When our kernel packaging was updated to build the virtualbox guest packages by downloading the dkms package, the modules were accidentally moved to linux-modules-extra instead of linux-modules. This has caused the modules to go missing in our Vagrant images. Fix: Move the modules back to linux-modules. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Therefore the risk of regression is extremely low. --- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the Vagrant error message: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: : No such device To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+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 1870189] Re: initramfs does not get loaded
** Tags added: rls-gg-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1870189
Title:
initramfs does not get loaded
Status in grub2 package in Ubuntu:
Won't Fix
Status in linux-azure package in Ubuntu:
Confirmed
Status in livecd-rootfs package in Ubuntu:
Triaged
Bug description:
A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu
20.04 by “do-release-upgrade –d”.
Then the latest Ubuntu v5.6 kernel was installed from
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a
reboot was performed, a panic with the v5.6 kernel occured because the
rootfs can not be found.
It turns out by default, initramfs does not get loaded:
/boot/grub/grub.cfg:
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os
$menuentry_id_option 'gnulinux-simple-3d2737e8-
b95a-42bf-bac1-bb6fb4cda87f' {
…
if [ "${initrdfail}" = 1 ]; then
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic
initrd/boot/initrd.img-5.6.0-050600-generic
else
linux /boot/vmlinuz-5.6.0-050600-generic
root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1
console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled
unknown_nmi_panic panic=-1
#Dexuan: here the initrd line is missing!
fi
initrdfail
}
As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally,
initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit
the “fail to mount rootfs” panic and the kernel will automatically reboot….
Also, the “initrdfail” here marks initrdfail=1, so when the kernel
boots for the 2nd time, the kernel should successfully boot up. Next,
when the kernel boots for the 3rd time, it panics again since the
userspace program resets initrdfail to 0, and next time when the
kernel boots, it can boot up successfully -- this
“panic/success/panic/success” pattern repeats forever…
The linux-azure kernels are not affected since they have the vmbus driver and
storage drivers built-in (i.e. “=y”):
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y
/boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m
/boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m
The v5.6 kernel uses =m rather than =y, so is affected here.
It looks the setting may be intentional, but we should not assume a customer
kernel must have the necessary vmbus/storage drivers built-in.
This issue only happens to the Ubuntu Marketplace image (19.10 and maybe
19.04 as well?) on Azure.
We installed a Ubuntu 20.04 VM from the .iso file from
http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub
issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+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 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1860659 Title: 4.15.0-1053 contains fatal nilfs2 kernel bug Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: Confirmed Bug description: The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug: https://marc.info/?t=15741385112 and it specifically concerns this nilfs2 commit for 5.3 which was apparently backported: https://marc.info/?l=linux-nilfs=157423529924889=2 My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel -1053 oopses consistently and reproducibly, with exactly the same "nilfs_segctor_do_construct" pattern as in the above bug report. Reverting to -1052 results in a working, bootable system again. The -1053 changelog mentions: "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)" which I suspect is the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+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 1860659] Re: 4.15.0-1053 contains fatal nilfs2 kernel bug
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1860659 Title: 4.15.0-1053 contains fatal nilfs2 kernel bug Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: Confirmed Bug description: The Bionic 4.15.0-1053 kernel package contains this nilfs2 bug: https://marc.info/?t=15741385112 and it specifically concerns this nilfs2 commit for 5.3 which was apparently backported: https://marc.info/?l=linux-nilfs=157423529924889=2 My RPi 2B boots fine from nilfs2 on kernel 4.15.0-1052, but kernel -1053 oopses consistently and reproducibly, with exactly the same "nilfs_segctor_do_construct" pattern as in the above bug report. Reverting to -1052 results in a working, bootable system again. The -1053 changelog mentions: "Bionic update: upstream stable patchset 2019-11-21 (LP: #1853519)" which I suspect is the cause. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1860659/+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 1880012] Re: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS
Attaching ubuntu-style information for the case that works fine where the laptop was booted from the Live-USB. ** Attachment added: "ubuntu-bug style info when fan works fine booting with Live-USB" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880012/+attachment/5375737/+files/fan_working_with_LiveUSB.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/1880012 Title: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: After installing Ubuntu 20.04 LTS, my laptop's temperature goes fairly high without intensive CPU activity. The fan(s) remain **off** under heavy CPU load and the temperature goes very high. I don't suspect a material failure since I didn't notice such overheating issues anymore with my previous Ubuntu (19.04) (after using sudo prime-select intel). **Config** - ASUS UX533FN - BIOS version 304 (up-to-date) - Kernel: 5.4.0-31-generic (same issue with 5.4.0-29) - NVIDIA GeForce MX150 (with latest NVIDIA driver) Low CPU load Without running anything special, I get the following figures with `sensors` command: ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+49.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +50.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+49.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+50.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+49.0°C (crit = +103.0°C) These figures are a too high in my opinion for low CPU load with a room temperature of 20°C. But here come's worse: Heavy CPU load == When the CPU is under load, for instance when running `sysbench cpu run` in loop, the temperature increases to 90°C, and no fan is triggered! To get a repeatable CPU load test, I run while true; do echo "One more time..." && sysbench cpu run; done Here are the figures I get in this case (from `sensors` command): ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+65.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +88.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+88.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+70.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+72.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+72.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+86.0°C (crit = +103.0°C) Note 1: The temperature in the room for this test is 20°C. Note 2: I got almost the same issue one year ago with Ubuntu 19.04 and used the sudo prime-select intel workaround. What I already tried - installing the latest NVIDIA driver, including selecting `intel` with `prime-select` ameliorated the situation but didn't tackle the issue - running `sensors-detect` (YES to all questions) resulted in `coretemp` to be added to `/etc/modules` - running `pwmconfig` didn't work: /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sylvain1710 F pulseaudio /dev/snd/pcmC0D0p: sylvain1710 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 20:58:45 2020 InstallationDate: Installed on 2020-05-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX533FN_UX533FN ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=1fba935a-ac77-4cdb-bc3a-d3ce26e567d9 ro quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 1880012] Re: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS
The fan is working when booting with the Live-USB I used to install Ubuntu 20.04 The Linux kernel from the Live-USB is Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux in case it makes any difference. -- 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/1880012 Title: ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: After installing Ubuntu 20.04 LTS, my laptop's temperature goes fairly high without intensive CPU activity. The fan(s) remain **off** under heavy CPU load and the temperature goes very high. I don't suspect a material failure since I didn't notice such overheating issues anymore with my previous Ubuntu (19.04) (after using sudo prime-select intel). **Config** - ASUS UX533FN - BIOS version 304 (up-to-date) - Kernel: 5.4.0-31-generic (same issue with 5.4.0-29) - NVIDIA GeForce MX150 (with latest NVIDIA driver) Low CPU load Without running anything special, I get the following figures with `sensors` command: ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+49.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +50.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+49.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+48.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+50.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+49.0°C (crit = +103.0°C) These figures are a too high in my opinion for low CPU load with a room temperature of 20°C. But here come's worse: Heavy CPU load == When the CPU is under load, for instance when running `sysbench cpu run` in loop, the temperature increases to 90°C, and no fan is triggered! To get a repeatable CPU load test, I run while true; do echo "One more time..." && sysbench cpu run; done Here are the figures I get in this case (from `sensors` command): ... pch_cannonlake-virtual-0 Adapter: Virtual device temp1:+65.0°C BAT0-acpi-0 Adapter: ACPI interface in0: 15.60 V asus-isa- Adapter: ISA adapter cpu_fan:0 RPM coretemp-isa- Adapter: ISA adapter Package id 0: +88.0°C (high = +100.0°C, crit = +100.0°C) Core 0:+88.0°C (high = +100.0°C, crit = +100.0°C) Core 1:+70.0°C (high = +100.0°C, crit = +100.0°C) Core 2:+72.0°C (high = +100.0°C, crit = +100.0°C) Core 3:+72.0°C (high = +100.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1:+86.0°C (crit = +103.0°C) Note 1: The temperature in the room for this test is 20°C. Note 2: I got almost the same issue one year ago with Ubuntu 19.04 and used the sudo prime-select intel workaround. What I already tried - installing the latest NVIDIA driver, including selecting `intel` with `prime-select` ameliorated the situation but didn't tackle the issue - running `sensors-detect` (YES to all questions) resulted in `coretemp` to be added to `/etc/modules` - running `pwmconfig` didn't work: /usr/sbin/pwmconfig: There are no pwm-capable sensor modules installed ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sylvain1710 F pulseaudio /dev/snd/pcmC0D0p: sylvain1710 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 20:58:45 2020 InstallationDate: Installed on 2020-05-08 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 13d3:56cb IMC Networks USB2.0 HD IR UVC WebCam Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. ZenBook UX533FN_UX533FN ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=1fba935a-ac77-4cdb-bc3a-d3ce26e567d9 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A
[Kernel-packages] [Bug 1880253] Re: More info for bug #1880012
*** This bug is a duplicate of bug 1880012 *** https://bugs.launchpad.net/bugs/1880012 I'm sorry filing this bug automatically (from Ubuntu 20.04 LTS Live-USB) has failed since no technical information was joined. So I'd like to remove this bug. ** Changed in: linux (Ubuntu) Status: New => Invalid ** Converted to question: https://answers.launchpad.net/ubuntu/+source/linux/+question/690900 -- 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/1880253 Title: More info for bug #1880012 Status in linux package in Ubuntu: Invalid Bug description: The attached logs correspond to booting the same ASUS UX533FN laptop, but this time using the Ubuntu 20.04 live-USB that was used to install Ubuntu 20.04 in the first place. Here, booting with the Live-USB, I can hear the fan is working! The kernel is Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux in case it makes any difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880253/+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 1880253] Re: More info for bug #1880012
*** This bug is a duplicate of bug 1880012 *** https://bugs.launchpad.net/bugs/1880012 I'm going to immediately link the present bug report to bug #1880012 and mark the current one as duplicate. The only purpose of the current bug report is to provide more information for bug #1880012. Sorry for any inconvenience my not finding a better way to bring more information. ** This bug has been marked a duplicate of bug 1880012 ASUS UX533F overheating and fan off with Ubuntu 20.04 LTS -- 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/1880253 Title: More info for bug #1880012 Status in linux package in Ubuntu: Invalid Bug description: The attached logs correspond to booting the same ASUS UX533FN laptop, but this time using the Ubuntu 20.04 live-USB that was used to install Ubuntu 20.04 in the first place. Here, booting with the Live-USB, I can hear the fan is working! The kernel is Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux in case it makes any difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880253/+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 1880253] [NEW] More info for bug #1880012
*** This bug is a duplicate of bug 1880012 *** https://bugs.launchpad.net/bugs/1880012 Public bug reported: The attached logs correspond to booting the same ASUS UX533FN laptop, but this time using the Ubuntu 20.04 live-USB that was used to install Ubuntu 20.04 in the first place. Here, booting with the Live-USB, I can hear the fan is working! The kernel is Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux in case it makes any difference. ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1880253 Title: More info for bug #1880012 Status in linux package in Ubuntu: Invalid Bug description: The attached logs correspond to booting the same ASUS UX533FN laptop, but this time using the Ubuntu 20.04 live-USB that was used to install Ubuntu 20.04 in the first place. Here, booting with the Live-USB, I can hear the fan is working! The kernel is Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux in case it makes any difference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880253/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
It was not fixed, in the 5.3.0-53 kernel !!! In the 5.7.0-994 kernel it is functional, but in the previous one it is not ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Confirmed Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
** Changed in: thermald (Ubuntu) Status: Fix Committed => Fix Released -- 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/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == As reported here: https://www.phoronix.com/forums/forum/linux- graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice- lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
systemd debdiff with a fix to skip creating /dev/disk/by-uuid for bcache backing, caching devices. ** Patch added: "lp1861941-skip-bcache-links.debdiff" https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+attachment/5375730/+files/lp1861941-skip-bcache-links.debdiff -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
debdiff of the changes ** Attachment added: "bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375722/+files/bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1 -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Updated test to be a bit more resilient. ** Attachment added: "test-bcache-byuuid-links-fixed.sh" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375723/+files/test-bcache-byuuid-links-fixed.sh -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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
Agreed -- 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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
Tarball of a source package with a fix for this issue: bcache-tools_1.0.8.orig.tar.gz bcache-tools_1.0.8-4ubuntu1_amd64.build bcache-tools_1.0.8-4ubuntu1_amd64.buildinfo bcache-tools_1.0.8-4ubuntu1_amd64.changes bcache-tools_1.0.8-4ubuntu1_amd64.deb bcache-tools_1.0.8-4ubuntu1.debian.tar.xz bcache-tools_1.0.8-4ubuntu1.dsc bcache-tools_1.0.8-4ubuntu1_source.build bcache-tools_1.0.8-4ubuntu1_source.buildinfo bcache-tools_1.0.8-4ubuntu1_source.changes bcache-tools-dbgsym_1.0.8-4ubuntu1_amd64.ddeb bcache-tools-debdiff-1.0.8-4_to_1.0.8-4ubuntu1 ** Attachment added: "bcache-tools-fix-lp1861941.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1861941/+attachment/5375721/+files/bcache-tools-fix-lp1861941.tar.gz -- 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/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: New Status in systemd package in Ubuntu: Invalid Status in bcache-tools source package in Focal: New Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: New Status in systemd source package in Focal: Invalid Status in bcache-tools source package in Groovy: Fix Released Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: New Status in systemd source package in Groovy: Invalid Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory 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 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
*** This bug is a duplicate of bug 1573095 *** https://bugs.launchpad.net/bugs/1573095 Eric, I'll close this LP as dup of #1879987 - seems it's the same issue. I'll try also the Debian release top see what's different there...we can comment in the other bug about Debian status and what are the differences. Thanks, Guilherme -- 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/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
*** This bug is a duplicate of bug 1573095 *** https://bugs.launchpad.net/bugs/1573095 Sorry, dup of LP #1573095. ** This bug has been marked a duplicate of bug 1573095 Cloud images fail to boot when a serial port is not available -- 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/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
It's still very slow. When I don't attach a serial device like you gave an example for to the virtualbox, it still has that 90s pause between mentioned 'printk' lines during booting and booting is slow in general. When I do attach the serial device, it still panics the first time, but the whole thing is so fast that vagrant doesn't notice or times out. So that setup is now workable. Still doesn't explain why it behaves so strange without a serial device. -- 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1853044] Re: 5.3.0-23-generic causes fans to spin when idle
Unfortunately this bug is back with linux-5.3.0-53.47. It got reintroduced somewhere between linux-5.3.0-53.47 and 5.3.0-51.44. System is Dell XPS 9550 with Skylake HD Graphics 530. -- 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 1856375] Re: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK
Additional conversations for the bug are happening in bug 1874544 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856375 Title: [linux-azure] Request to autoload mlx4/mlx5 modules for DPDK Status in linux-azure package in Ubuntu: New Bug description: Ubuntu 18.04 images in the marketplace do not automatically load the required mlx drivers. (mlx4_ib|mlx5_ib and mlx4_en|mlx5_en) Someone trying DPDK on Ubuntu 18.04 has raised an issue on Azure DPDK document(https://github.com/MicrosoftDocs/azure-docs/issues/44303). To reproduce, bring up an ubuntu 18.04 VM on Azure. There you can see only mlx4_en but not the other one(mlx4_ib): # lsmod | grep mlx4 mlx4_en 118784 0 mlx4_core 294912 1 mlx4_en We would expect there to be 4 kernel modules loaded such as: mlx[4|5]_ib, rdma_cm, rdma_ucm, and ib_ipoib To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1856375/+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 1880237] [NEW] Disco update: upstream stable patchset 2020-05-22
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: upstream stable patchset 2020-05-22 Ported from the following upstream stable releases: v4.19.123, v.5.4.41 from git://git.kernel.org/ USB: serial: qcserial: Add DW5816e support tracing/kprobes: Fix a double initialization typo vt: fix unicode console freeing with a common interface dp83640: reverse arguments to list_add_tail fq_codel: fix TCA_FQ_CODEL_DROP_BATCH_SIZE sanity checks net: macsec: preserve ingress frame ordering net/mlx4_core: Fix use of ENOSPC around mlx4_counter_alloc() net_sched: sch_skbprio: add message validation to skbprio_change() net: usb: qmi_wwan: add support for DW5816e sch_choke: avoid potential panic in choke_reset() sch_sfq: validate silly quantum values tipc: fix partial topology connection closure bnxt_en: Fix VLAN acceleration handling in bnxt_fix_features(). net/mlx5: Fix forced completion access non initialized command entry net/mlx5: Fix command entry leak in Internal Error State bnxt_en: Improve AER slot reset. bnxt_en: Fix VF anti-spoof filter setup. net: stricter validation of untrusted gso packets HID: wacom: Read HID_DG_CONTACTMAX directly for non-generic devices sctp: Fix bundling of SHUTDOWN with COOKIE-ACK HID: usbhid: Fix race between usbhid_close() and usbhid_stop() USB: uas: add quirk for LaCie 2Big Quadra USB: serial: garmin_gps: add sanity checking for data length tracing: Add a vmalloc_sync_mappings() for safe measure KVM: arm: vgic: Fix limit condition when writing to GICD_I[CS]ACTIVER KVM: arm64: Fix 32bit PC wrap-around arm64: hugetlb: avoid potential NULL dereference mm/page_alloc: fix watchdog soft lockups during set_zone_contiguous() staging: gasket: Check the return value of gasket_get_bar_index() coredump: fix crash when umh is disabled batman-adv: fix batadv_nc_random_weight_tq batman-adv: Fix refcnt leak in batadv_show_throughput_override batman-adv: Fix refcnt leak in batadv_store_throughput_override batman-adv: Fix refcnt leak in batadv_v_ogm_process x86/entry/64: Fix unwind hints in register clearing code x86/entry/64: Fix unwind hints in kernel exit path x86/entry/64: Fix unwind hints in rewind_stack_do_exit() x86/unwind/orc: Don't skip the first frame for inactive tasks x86/unwind/orc: Prevent unwinding before ORC initialization x86/unwind/orc: Fix error path for bad ORC entry type x86/unwind/orc: Fix premature unwind stoppage due to IRET frames netfilter: nat: never update the UDP checksum when it's 0 netfilter: nf_osf: avoid passing pointer to local var objtool: Fix stack offset tracking for indirect CFAs scripts/decodecode: fix trapping instruction formatting ipc/mqueue.c: change __do_notify() to bypass check_kill_permission() drm/amdgpu: move kfd suspend after ip_suspend_phase1 drm/amdgpu: drop redundant cg/pg ungate on runpm enter tty: xilinx_uartps: Fix missing id assignment to the console devlink: fix return value after hitting end in region read neigh: send protocol value in neighbor create notification net: tc35815: Fix phydev supported/advertising mask net/tls: Fix sk_psock refcnt leak in bpf_exec_tx_verdict() net/tls: Fix sk_psock refcnt leak when in tls_data_ready() nfp: abm: fix a memory leak bug tunnel: Propagate ECT(1) when decapsulating as recommended by RFC6040 bnxt_en: Reduce BNXT_MSIX_VEC_MAX value to supported CQs per PF. bnxt_en: Return error when allocating zero size context memory. HID: wacom: Report 2nd-gen Intuos Pro S center button status over BT crypto: arch/nhpoly1305 - process in explicit 4k chunks mm: limit boost_watermark on small zones KVM: x86: Fixes posted interrupt check for IRQs delivery modes mm, memcg: fix error return value of mem_cgroup_css_alloc() UBUNTU: upstream stable to v4.19.123, v5.4.41 ** Affects: linux (Ubuntu) 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 ** 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: -
[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once
Vagrant boxes with updated kernels have been pushed. My current tests are showing boot times in the 30s range. Could folks commenting on slow boot speeds in Focal and Eoan please run a `vagrant box update` on their current setups? https://app.vagrantup.com/ubuntu/boxes/eoan64/versions/20200522.0.0 and https://app.vagrantup.com/ubuntu/boxes/focal64/versions/20200518.0.0 Have the latest kernels. Any produced after those dates should also load faster. -- 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/1874453 Title: ubuntu/focal64 very slow to boot and reboots once Status in cloud-images: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Using `ubuntu/focal64` version `20200423.0.0`, the boot process is extremely slow and the box always reboots once before completing a successful boot. With default settings, this causes a timeout in Vagrant waiting for SSH to be available. Setting a long enough timeout it does eventually boot successfully. For comparison, `ubuntu/bionic64` boots successfully in roughly 10 seconds on my machine. This appears to be the big hang-up: Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] enabled Apr 23 14:00:12 ubuntu-focal kernel: [ 76.448371] printk: console [ttyS0] enabled I have a hard time telling where exactly it reboots because my /var/log/syslog only ends up with the second boot. I can watch it in Virtualbox though and it suddenly reboots, then the second boot process runs to completion. The long delay shown above happens both times making the total time to a successful boot very long. Here is the head of my /var/log/syslog: Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel File Systems. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File System... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent Storage... Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables... Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users... Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File System. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent Storage. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed. Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group systemd-coredump with gid 999. Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user systemd-coredump (systemd Core Dumper) with uid 999 and gid 999. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete Device Initialization... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes in /dev... Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes in /dev. Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device Manager... Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager. Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 ( Ubuntu 5.4.0-26.30-generic 5.4.30) Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro console=tty1 console=ttyS0 Subsequent boots are also slow but don't seem to have the extra reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 7 16:02 seq crw-rw 1 root audio 116, 33 May 7 16:02 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No
[Kernel-packages] [Bug 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
Focal and Eoan boxes with the above kernels have been pushed to Vagrant and verified. Please run a `vagrant box update` to get the latest versions. ** Changed in: cloud-images Status: Confirmed => 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/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders Status in cloud-images: Fix Released Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: When our kernel packaging was updated to build the virtualbox guest packages by downloading the dkms package, the modules were accidentally moved to linux-modules-extra instead of linux-modules. This has caused the modules to go missing in our Vagrant images. Fix: Move the modules back to linux-modules. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Therefore the risk of regression is extremely low. --- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the Vagrant error message: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: : No such device To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+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 1879575] Re: rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3
Hi You-Sheng Yang, I appreciate that you took the effort to fix this bug. Unfortunately, I don't have Ubuntu 20.04 installed in my system as I needed wifi urgently which made me switch to Ubuntu 18.04 LTS. For the time being, unless someone faces the same problem, I request that you can close the bug. Thanks 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/1879575 Title: rtl8822be not initialized: rtw_pci: Refused to change power state, currently in D3 Status in linux package in Ubuntu: Incomplete Bug description: Wifi adapter can't find avaiable connections in new kernel. Upgraded from 19.04 to 19.10 and then to 20.04 on Lenovo Legion y530 which comes with realtek wifi adapter. lspci shows the pci adapter but not found in lshw -C network. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: manish 1950 F pulseaudio /dev/snd/controlC0: manish 1950 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-06 (318 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-31-generic root=UUID=a67f2402-8ada-4a31-8500-4ce7031521e2 ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-31-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-18 (1 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879575/+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 1879393] Re: Delayed failure in Genesys USB3 SD card reader
I'm several steps down the bisect at this point and have overcome several compilation issues along the way (old kernels won't compile with gcc-9, so installed gcc-8, patched around an issue building with newer headers, https://gitlab.freedesktop.org/drm/msm/commit/dfbd199a7cfe3e3cd8531e1353cdbd7175bfbc5e, and dealt with some stale build artefacts, mainly vmlinux-gdb.py), but now I seem to have hit a build issue that I can't google around! Specifically, I was at commit 2b7bee1a6df3e666e2ebf3e523ca9c1a98f931dd and got the following error during the build: CC /home/dave/projects/linux/tools/objtool/str_error_r.o ../lib/str_error_r.c: In function ‘str_error_r’: ../lib/str_error_r.c:25:3: error: passing argument 1 to restrict-qualified parameter aliases with argumen t 5 [-Werror=restrict] snprintf(buf, buflen, "INTERNAL ERROR: strerror_r(%d, %p, %zd)=%d", errnum, buf, buflen, err); ^~~~ cc1: all warnings being treated as errors mv: cannot stat '/home/dave/projects/linux/tools/objtool/.str_error_r.o.tmp': No such file or directory I couldn't manage to successfully patch my way around that one, so I skipped that commit and instantly ran into exactly the same issue on the next try. Any ideas for working around this? -- 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/1879393 Title: Delayed failure in Genesys USB3 SD card reader Status in linux package in Ubuntu: Confirmed Bug description: I have a "UGreen USB3 Hub/SD card reader" which worked reliably under Ubuntu Xenial for many months. Recently, I re-installed the machine it was attached to with a fresh install of Ubuntu Focal. When initially booted, the device works perfectly (at least, the USB3 ports and SD card reader do; those are the only ports I use on it). However, after some period of time I inevitably find the device has stopped working, and dmesg is flooded with repeats of the following block of messages (I include several copies below so the typical time-delay between repeats can be observed): [39695.777289] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39695.777293] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39695.861328] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39728.545725] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39728.545728] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39728.633771] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39761.313967] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39761.313969] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39761.397933] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39794.082286] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39794.082289] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39794.166248] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39826.850674] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39826.850677] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39826.938742] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd [39859.618976] xhci_hcd :05:00.0: WARN Cannot submit Set TR Deq Ptr [39859.618979] xhci_hcd :05:00.0: A Set TR Deq Ptr command is pending. [39859.706965] usb 6-2.3: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd The delay before failure (and these messages appearing) is highly variable. Sometimes it's within a couple of minutes of booting the machine; sometimes the device works happily for a couple of hours before failure. I've found that simply replugging the device (temporarily) solves the issue, but obviously I'd prefer the device to be as reliable as it was under the Xenial kernel. This may be related to LP: #1798979 which features extremely similar log messages on failure, but the symptoms are ever so slightly different (no CPU spike, no blinking LED), as is the model of card reader, hence why I've filed a separate bug. I'll add an apport report after filing this, but I should add there are multiple card-readers on this machine (my work involves raspberry pis, so I often find myself re-writing cards in bulk :). The specific one with the issue is listed as follows in the lsusb output: Bus 006 Device 005: ID 05e3:0743 Genesys Logic, Inc. SDXC and microSDXC CardReader The other card reader listed in that output (realtek) is a separate device with no issues. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate:
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
Thanks, this eliminated the problem. The only unexplained thing is what was the urge to break the "old" package which perfectly worked before. If Ubuntu planned to reorder/restructure package names, the reasonable way would be to turn 'bcmwl-kernel-source' into a dummy/transitional package which would pull new broadcom-sta-* packages as its dependencies. But probably Ubuntu plans were more mysterial than that. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: Confirmed Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0
OK.
I've reviewed the kernel code, and there are no unexpected changes w.r.t
the CACHED_UUID change event. So I don't think we will need any kernel
changes which is good.
With the small change to the 60-persistent-storage.rules to not attempt
to create a /dev/disk/by-uuid symlink for the backing device; instead we
want to only create a /dev/bcache/by-uuid symlink to the bcacheN device
(that is associated with the backing device).
# by-label/by-uuid links (filesystem metadata), skip bcache backing,caching
devices, handled in 69-bcache.rules
ENV{ID_FS_TYPE}=="bcache", GOTO="skip_fs_uuid_enc"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_UUID_ENC}=="?*",
SYMLINK+="disk/by-uuid/$env{ID_FS_UUID_ENC}"
ENV{ID_FS_USAGE}=="filesystem|other|crypto", ENV{ID_FS_LABEL_ENC}=="?*",
SYMLINK+="disk/by-label/$env{ID_FS_LABEL_ENC}"
LABEL="skip_fs_uuid_enc"
And then with my previously proposed changed to 69-bcache.rules in place
https://github.com/g2p/bcache-tools/pull/29/files
The test-case works just fine.
--
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/1861941
Title:
bcache by-uuid links disappear after mounting bcache0
Status in bcache-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Incomplete
Status in linux-signed package in Ubuntu:
New
Status in systemd package in Ubuntu:
Invalid
Status in bcache-tools source package in Focal:
New
Status in linux source package in Focal:
Invalid
Status in linux-signed source package in Focal:
New
Status in systemd source package in Focal:
Invalid
Status in bcache-tools source package in Groovy:
Fix Released
Status in linux source package in Groovy:
Incomplete
Status in linux-signed source package in Groovy:
New
Status in systemd source package in Groovy:
Invalid
Bug description:
1.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
2.
root@ubuntu:~# lsb_release -rd
Description: Ubuntu Focal Fossa (development branch)
Release: 20.04
root@ubuntu:~# apt-cache policy linux-image-virtual
linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
*** 5.4.0.12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
*** 5.4.0-12.15 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status
3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
+ ls -al /dev/bcache/by-uuid/
total 0
drwxr-xr-x 2 root root 60 Feb 4 23:31 .
drwxr-xr-x 3 root root 60 Feb 4 23:31 ..
lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a
-> ../../bcache0
4.
root@ubuntu:~# ls -al /dev/bcache/by-uuid
ls: cannot access '/dev/bcache/by-uuid': No such file or directory
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
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
Date: Tue Feb 4 23:31:52 2020
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
SourcePackage: linux-signed-5.4
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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] Re: update-initramfs complains of missing amdgpu firmware files
I see this when running sudo apt dist-upgrade. $ uname -a Linux andradeii 5.4.0-7629-generic #33~1589834512~20.04~ff6e79e-Ubuntu SMP Mon May 18 23:29:32 UTC x86_64 x86_64 x86_64 GNU/Linux $ sudo apt dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: system76-power 1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 435 kB of archives. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://ppa.launchpad.net/system76/pop/ubuntu focal/main amd64 system76-power amd64 1.1.4~1590091483~20.04~15264d3 [435 kB] Fetched 435 kB in 1s (441 kB/s) (Reading database ... 257591 files and directories currently installed.) Preparing to unpack .../system76-power_1.1.4~1590091483~20.04~15264d3_amd64.deb ... Unpacking system76-power (1.1.4~1590091483~20.04~15264d3) over (1.1.4~1589409407~20.04~fbef7a2) ... Setting up system76-power (1.1.4~1590091483~20.04~15264d3) ... Processing triggers for dbus (1.12.16-2ubuntu2) ... Processing triggers for initramfs-tools (0.136ubuntu6) ... update-initramfs: Generating /boot/initrd.img-5.4.0-7629-generic cryptsetup: WARNING: Resume target cryptswap uses a key file 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 kernelstub.Config: INFO Looking for configuration... kernelstub : INFO System information: OS:..Pop!_OS 20.04 Root partition:../dev/sda7 Root FS UUID:37941144-436e-4d7c-800a-ecae219596c7 ESP Path:/boot/efi ESP Partition:.../dev/sda5 ESP Partition #:.5 NVRAM entry #:...-1 Boot Variable #:. Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash Kernel Image Path:.../boot/vmlinuz-5.4.0-7629-generic Initrd Image Path:.../boot/initrd.img-5.4.0-7629-generic Force-overwrite:.False kernelstub.Installer : INFO Copying Kernel into ESP kernelstub.Installer : INFO Copying initrd.img into ESP kernelstub.Installer : INFO Setting up loader.conf configuration kernelstub.Installer : INFO Making entry file for Pop!_OS kernelstub.Installer : INFO Backing up old kernel kernelstub.Installer : INFO Making entry file for Pop!_OS But the modules seem to be loaded anyways: $ lsmod | rg amd edac_mce_amd 32768 0 kvm_amd98304 0 kvm 663552 1 kvm_amd ccp86016 7 kvm_amd amdgpu 4575232 42 amd_iommu_v2 20480 1 amdgpu gpu_sched 32768 1 amdgpu i2c_algo_bit 16384 1 amdgpu ttm 106496 1 amdgpu drm_kms_helper184320 1 amdgpu drm 491520 21 gpu_sched,drm_kms_helper,amdgpu,ttm gpio_amdpt 20480 0 gpio_generic 20480 1 gpio_amdpt -- 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/1873325 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Triaged Bug description: SRU Justification Impact: amdgpu references firmware files in modinfo which have not been supplied to linux-firmware. This causes update-initramfs to generate "Possible missing firmware" warnings. Fix: Since the firmware is not available, all we can do is remove the files from modinfo. Test Case: Confirm that update-initramfs no longer produces the warnings. Regression Potential: Low. If someone had managed to obtain these files they will no longer be added to the initramfs, potentially causing regressions for these users. This would be an atypical situation. --- 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/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
My bad. Looks like 5.4.0-32 never made it out of -proposed. -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1880213] 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 1880213 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 ** Changed in: linux (Ubuntu Xenial) 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/1880213 Title: ext2 build failure on 4.4.0-180.210 Status in linux package in Ubuntu: Incomplete Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: Incomplete Status in linux-snapdragon source package in Xenial: New Bug description: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880213/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
It's the same upstream patchlevel as the previous kernel: $ cat /proc/version_signature Ubuntu 5.4.0-31.35-generic 5.4.34 -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
@Hui, Thank you for looking deeper into the problem, and for your explanation. I tried disconnecting and reconnecting the speaker to the audio output jack as you suggested, however it did not change the behavior. The 'Dummy Output' remains, and no sound is heard. @Kai, I added the PPA you linked to, applied the updates, and rebooted my system. Unfortunately, this did not change the behavior. The 'Dummy Output' remains, and no sound is heard. Please let me know if I can provide any addition information or fresh logs files from my system, as I am happy to do so. Thank you both again for your help! -- 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/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1880213] [NEW] ext2 build failure on 4.4.0-180.210
Public bug reported: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-snapdragon (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1880213 Title: ext2 build failure on 4.4.0-180.210 Status in linux package in Ubuntu: New Status in linux-snapdragon package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-snapdragon source package in Xenial: New Bug description: [Impact] Build failure when building ext2 fs/ext2/xattr.c:828:18: error: 'ext2_xattr_cache' undeclared (first use in this function) atomic_read(_xattr_cache->c_entry_count)); [Fix] The fix is upstream commit 32302085a8d90859c40cf1a5e8313f575d06ec75 "ext2: fix debug reference to ext2_xattr_cache" [Test case] Enable CONFIG_EXT2_FS and build kernel [Regression potential] Low, fix is changing the contents of a print to a string literal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880213/+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 1873506] Re: ubuntu/focal64 fails to mount Vagrant shared folders
** Changed in: cloud-images Assignee: (unassigned) => John Chittum (jchittum) -- 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/1873506 Title: ubuntu/focal64 fails to mount Vagrant shared folders Status in cloud-images: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU Justification Impact: When our kernel packaging was updated to build the virtualbox guest packages by downloading the dkms package, the modules were accidentally moved to linux-modules-extra instead of linux-modules. This has caused the modules to go missing in our Vagrant images. Fix: Move the modules back to linux-modules. Test Case: Build the kernel packages and confirm that the vboxguest and vboxsf drivers are now in linux-modules rather than linux-modules- extra. Regression Potential: Since linux-modules is required, anyone who is using the vbox drivers will continue to have them after this change. Therefore the risk of regression is extremely low. --- Attempting to `vagrant up` using the `ubuntu/focal64` box fails to mount the `/vagrant` shared folder. `ubuntu/bionic64` works as expected. Here is the Vagrant error message: Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: : No such device To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1873506/+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 1871917] Re: Unable to boot 20.04 installer on Dell XPS 15 9560
Same issue on XPS 9560, 8GB USB stick. Created in Rufus from ubuntu-20.04-desktop-amd64.iso, both ISO and DD mode behave the same. Can't install 20.04 as a result. No way to collect the logs, because the laptop shuts down after disks checks and there is no interaction other than Ctrl+C to cancel disk checks and speed this up. -- 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/1871917 Title: Unable to boot 20.04 installer on Dell XPS 15 9560 Status in linux package in Ubuntu: Confirmed Bug description: I tried to boot the 20.04 nightly image (focal-desktop-amd64.iso 2020-04-05 11:06 ) as well as an older one (a week ago) on my Dell XPS 15 9560, and I got the same error message each time. The live system performs a filesystem check while showing a progress bar on a screen with dell and ubuntu logo, then the linux console shows with following error: sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 3816176 async page read This happens with two different 16GB usb sticks on the Dell XPS 15. They both worked fine on an old samsung netbook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871917/+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 1867686] Re: FC hosts become unresponsive during array upgrade
I don't believe so as I am able to discover SCSI devices on my Emulex fabric-attached, Emulex direct-connect, and Qlogic fabric-attached hosts before starting this test. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+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 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I believe it's a bug with the inbox Qlogic driver -- 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/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+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 1879658] Re: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels
Test kernel has been tested successfully so far by original reporter and has fixed the Docker breakage and so on. -- 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/1879658 Title: Cannot create ipvlans with > 1500 MTU on recent Bionic kernels Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: [IMPACT] Setting an MTU larger than the default 1500 results in an error on the recent (4.15.0-92+) Bionic/Xenial -hwe kernels when attempting to create ipvlan interfaces: # ip link add test0 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument This breaks Docker and other applications which use a Jumbo MTU (9000) when using ipvlans. The bug is caused by the following recent commit to Bionic & Xenial-hwe; which is pulled in via the stable patchset below, which enforces a strict min/max MTU when MTUs are being set up via rtnetlink for ipvlans: Breaking commit: --- Ubuntu-hwe-4.15.0-92.93~16.04.1 * Bionic update: upstream stable patchset 2020-02-21 (LP: #1864261) * net: rtnetlink: validate IFLA_MTU attribute in rtnl_create_link() The above patch applies checks of dev->min_mtu and dev->max_mtu to avoid a malicious user from crashing the kernel with a bad value. It was patching the original patchset to centralize min/max MTU checking from various different subsystems of the networking kernel. However, in that patchset, the max_mtu had not been set to the largest phys (64K) or jumbo (9000 bytes), and defaults to 1500. The recent commit above which enforces strict bounds checking for MTU size exposes the bug of the max mtu not being set correctly for the ipvlan driver (this has been previously fixed in bonding, teaming drivers). Fix: --- This was fixed in the upstream kernel as of v4.18-rc2 for ipvlans, but was not backported to Bionic along with other patches. The missing commit in the Bionic backport: ipvlan: use ETH_MAX_MTU as max mtu commit 548feb33c598dfaf9f8e066b842441ac49b84a8a [Test Case] 1. Install any kernel earlier than 4.15.0-92 (Bionic/Xenial-hwe) 2. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 (where test1 eno1 is the physical interface you are adding the ipvlan on) 3. # ip link ... 14: test1@eno1: mtu 9000 qdisc noop state DOWN mode DEFAULT group default qlen 1000 ... // check that your test1 ipvlan is created with mtu 9000 4. Install 4.15.0-92 kernel or later 5. # ip link add test1 mtu 9000 link eno1 type ipvlan mode l2 RTNETLINK answers: Invalid argument 6. With the above fix commit backported to the xenial-hwe/Bionic, the jumbo mtu ipvlan creation works again, identical to before 92. [Regression Potential] This commit is in upstream mainline as of v4.18-rc2, and hence is already in Cosmic and later, i.e. all post Bionic releases currently. Hence there's low regression potential here. It only impacts ipvlan functionality, and not other networking systems, so core systems should not be affected by this. And affects on setup so it either works or doesn't. Patch is trivial. It only impacts Bionic/Xenial-hwe 4.15.0-92 onwards versions (where the latent bug got exposed). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879658/+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 1878718] Re: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable
a) When I do a short press, then immediately after a release, the next option is selected (the dialog does not have time to appear even). b) When I do a long press, then the options start to circle very quickly until I release the key (see the screencast) I think the bug is caused by this: When you do Super+K, you hold Super and press K repeatedly to switch the options. After you release the Super key, the option is confirmed. When you use the fn key, there is just one key, so after releasing, it immediately selects the option. -- 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/1878718 Title: HP ZBook 15 G6 display key (Fn+F1) autorepeats too fast to be usable Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Steps to reproduce: 1. Press the functional button for switching output to displays (joint, mirror, bulit-in, external) 2. The dialog is invoked What is expected: I should be able to select the desired option and confirm it What happened instead: While the functional button for invoking the dialog is pressed, it iterates extremely fast over the options. I cannot control it. After releasing the key, the currently selected option is confirmed, which is effectively random. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 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: Fri May 15 01:28:30 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9895584a-6648-494d-9d91-e64ba192dd95 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: HP dmi.bios.version: R92 Ver. 01.02.01 dmi.board.name: 860F dmi.board.vendor: HP dmi.board.version: KBC Version 65.23.00 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrR92Ver.01.02.01:bd09/25/2019:svnHP:pnHPZBook15G6:pvr:rvnHP:rn860F:rvrKBCVersion65.23.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ZBook 15 dmi.product.name: HP ZBook 15 G6 dmi.product.sku: 6CJ09AV dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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+git20200226-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/1878718/+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 1867686] Re: FC hosts become unresponsive during array upgrade
Is this dupe of #1860724? -- 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/1867686 Title: FC hosts become unresponsive during array upgrade Status in linux package in Ubuntu: Confirmed Bug description: While running automated array upgrade, my FC hosts become unresponsive and / or stop logging . Sometimes the host stop logging to /var/log/syslog, but I can still SSH into the host. Sometimes I try to SSH to the host in the middle of the test and it'll prompt me for a username that I then input, but it hangs there indefinitely and I have to power cycle the host. Other times my host becomes completely unresponsive and I can't SSH into the host and have to power cycle in order to gain access again. I thought the host might be crashing, but I'm not seeing any file get generated in /var/crash. I also thought my hosts might be going to sleep or hibernating, but I ran "sudo systemctl mask sleep.target suspend.target hibernate.target hybrid- sleep.target" and am not seeing any improvements. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867686/+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 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I've never used a complex setup like this, so I have to ask, are we sure it's kernel bug? -- 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/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+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 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
@kaihengfeng, not sure how to capture dmesg, as the boot process never completes preventing me from accessing a command line. Also, I am unable to switch to another TTY session. Can you please provide guidance or direct me to a article that explains how to capture the 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/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Incomplete Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+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 1860724] Re: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices
I am still seeing this with Ubuntu 20.04 LTS -- 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/1860724 Title: QLogic Direct-Connect host can't discover SCSI-FC or NVMe/FC devices Status in linux package in Ubuntu: Confirmed Bug description: My QLogic direct-connect host can't seem to SANboot or see any SCSI-FC devices in general. I'm also not able to discover any NVMe devices. I'm running with Ubuntu 20.04 kernel-5.4.0-9-generic. There are the HBAs I'm running with: root@ICTM1610S01H4:~# cat /sys/class/fc_host/host*/symbolic_name QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2742 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k QLE2692 FW:v8.08.231 DVR:v10.01.00.19-k lsscsi and multipath -ll don't seem to see my SCSI devices: root@ICTM1610S01H4:/opt/iop/linux/scratch# multipath -ll root@ICTM1610S01H4:/opt/iop/linux/scratch# lsscsi [0:0:0:0]cd/dvd KVM vmDisk-CD0.01 /dev/sr0 [1:0:0:0]cd/dvd HL-DT-ST DVDRAM GUD0N PF02 /dev/sr1 [3:0:0:0]diskATA ST1000NX0313 SNA3 /dev/sda It doesn't appear to be a configuration/hardware issue as installing Ubuntu 18.04 on the same exact server is able to SANboot and see my SCSI devices. root@ICTM1610S01H4:/opt/iop/linux/scratch# lsb_release -rd Description:Ubuntu Focal Fossa (development branch) Release:20.04 root@ICTM1610S01H4:/opt/iop/linux/scratch# apt-cache policy linux-image-generic linux-image-generic: Installed: 5.4.0.9.11 Candidate: 5.4.0.9.11 Version table: *** 5.4.0.9.11 500 500 http://repomirror-ict.eng.netapp.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.9.11 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 23 11:32 seq crw-rw 1 root audio 116, 33 Jan 23 11:32 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Thu Jan 23 15:04:42 2020 InstallationDate: Installed on 2020-01-23 (0 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200107) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: FUJITSU PRIMERGY RX2540 M4 PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic root=UUID=9b9e6b1a-b8d9-4d9c-8782-36729d7f88a4 ro console=tty0 console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-5.4.0-9-generic N/A linux-backports-modules-5.4.0-9-generic N/A linux-firmware 1.184 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/25/2019 dmi.bios.vendor: FUJITSU // American Megatrends Inc. dmi.bios.version: V5.0.0.12 R1.35.0 for D3384-A1x dmi.board.name: D3384-A1 dmi.board.vendor: FUJITSU dmi.board.version: S26361-D3384-A13 WGS04 GS04 dmi.chassis.asset.tag: System Asset Tag dmi.chassis.type: 23 dmi.chassis.vendor: FUJITSU dmi.chassis.version: RX2540M4R4 dmi.modalias: dmi:bvnFUJITSU//AmericanMegatrendsInc.:bvrV5.0.0.12R1.35.0forD3384-A1x:bd06/25/2019:svnFUJITSU:pnPRIMERGYRX2540M4:pvr:rvnFUJITSU:rnD3384-A1:rvrS26361-D3384-A13WGS04GS04:cvnFUJITSU:ct23:cvrRX2540M4R4: dmi.product.family: SERVER dmi.product.name: PRIMERGY RX2540 M4 dmi.product.sku: S26361-K1567-Vxxx dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860724/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1878484] Re: kernel panic on i915
It still crashes on 5.4.0-31-generic #35-Ubuntu I'm still looking for that damm __i915_schedule+0x261/0x350, still haven't been able to pinpoint that to code. [ 9640.917215] BUG: kernel NULL pointer dereference, address: 00e0 [ 9640.917262] #PF: supervisor read access in kernel mode [ 9640.917277] #PF: error_code(0x) - not-present page [ 9640.917289] PGD 0 P4D 0 [ 9640.917310] Oops: [#1] SMP PTI [ 9640.917336] CPU: 2 PID: 1397 Comm: Xorg Tainted: P O 5.4.0-31-generic #35-Ubuntu [ 9640.917351] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./N3700-ITX, BIOS P2.00 04/16/2018 [ 9640.917585] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [ 9640.917605] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39 70 60 74 33 45 89 b4 24 18 04 00 00 8b 80 60 01 00 00 be 00 [ 9640.917619] RSP: 0018:c100f9e0 EFLAGS: 00010002 [ 9640.917635] RAX: 0080 RBX: 9d871d4dfab0 RCX: 9d871d4dfab0 [ 9640.917647] RDX: 9d871d4dfad0 RSI: 9d882b71d180 RDI: 9d871d4dfab0 [ 9640.917660] RBP: c100fa78 R08: c100f9c0 R09: 9d871d4dc420 [ 9640.917673] R10: R11: 0208 R12: 9d8834dec000 [ 9640.917687] R13: c100f9f0 R14: 1000 R15: c100fa00 [ 9640.917702] FS: 7f283650ba80() GS:9d883830() knlGS: [ 9640.917715] CS: 0010 DS: ES: CR0: 80050033 [ 9640.917727] CR2: 00e0 CR3: 000272a98000 CR4: 001006e0 [ 9640.917740] Call Trace: [ 9640.917946] ? intel_compute_aligned_offset+0x120/0x170 [i915] [ 9640.918001] i915_schedule+0x2d/0x50 [i915] [ 9640.918053] __fence_set_priority+0x6b/0x90 [i915] [ 9640.918238] fence_set_priority+0x23/0x60 [i915] [ 9640.918374] i915_gem_object_wait_priority+0x13e/0x170 [i915] [ 9640.918429] intel_prepare_plane_fb+0x1ab/0x2d0 [i915] [ 9640.918464] drm_atomic_helper_prepare_planes+0x94/0x120 [drm_kms_helper] [ 9640.918518] intel_atomic_commit+0xc2/0x2b0 [i915] [ 9640.918574] drm_atomic_nonblocking_commit+0x4d/0x60 [drm] [ 9640.918592] drm_atomic_helper_page_flip+0x63/0xa0 [drm_kms_helper] [ 9640.918617] drm_mode_page_flip_ioctl+0x59d/0x630 [drm] [ 9640.918641] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [ 9640.918661] drm_ioctl_kernel+0xae/0xf0 [drm] [ 9640.918682] drm_ioctl+0x234/0x3d0 [drm] [ 9640.918706] ? drm_mode_cursor2_ioctl+0x10/0x10 [drm] [ 9640.918719] do_vfs_ioctl+0x407/0x670 [ 9640.918730] ? fput+0x13/0x15 [ 9640.918741] ? __sys_recvmsg+0x88/0xa0 [ 9640.918748] ksys_ioctl+0x67/0x90 [ 9640.918754] __x64_sys_ioctl+0x1a/0x20 [ 9640.918763] do_syscall_64+0x57/0x190 [ 9640.918773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 9640.918781] RIP: 0033:0x7f283686937b [ 9640.918788] Code: 0f 1e fa 48 8b 05 15 3b 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00 f3 0f 1e fa b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d e5 3a 0d 00 f7 d8 64 89 01 48 [ 9640.918794] RSP: 002b:7ffce75d29b8 EFLAGS: 0246 ORIG_RAX: 0010 [ 9640.918799] RAX: ffda RBX: 7ffce75d29f0 RCX: 7f283686937b [ 9640.918804] RDX: 7ffce75d29f0 RSI: c01864b0 RDI: 000e [ 9640.918808] RBP: c01864b0 R08: 000dac7e R09: 006c [ 9640.918813] R10: 000e R11: 0246 R12: 55d8a2a4e040 [ 9640.918817] R13: 000e R14: 000dac7e R15: 0002 [ 9640.918823] Modules linked in: bnep wireguard(O) ip6_udp_tunnel udp_tunnel binfmt_misc zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) input_leds joydev nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm intel_rapl_msr mei_hdcp snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq intel_rapl_common intel_powerclamp coretemp kvm_intel snd_seq_device kvm snd_timer punit_atom_debug intel_cstate snd hci_uart mei_txe btqca btrtl mei btbcm btintel soundcore intel_xhci_usb_role_switch roles bluetooth ecdh_generic ecc mac_hid rfkill_gpio acpi_pad intel_int0002_vgpio sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt netconsole hid_logitech_hidpp hid_logitech_dj hid_generic usbhid crct10dif_pclmul crc32_pclmul ghash_clmulni_intel uas usb_storage i915 aesni_intel crypto_simd i2c_algo_bit cryptd glue_helper drm_kms_helper i2c_i801 [ 9640.918894] syscopyarea sysfillrect lpc_ich sysimgblt r8169 fb_sys_fops realtek drm ahci libahci video i2c_hid hid [ 9640.918920] CR2: 00e0 [ 9640.918934] ---[ end trace afb51e7987093d9b ]--- [ 9640.918999] RIP: 0010:__i915_schedule+0x261/0x350 [i915] [ 9640.919004] Code: ff a8 08 0f 84 a0 00 00 00 45 3b b4 24 18 04 00 00 7e 50 49 8b 84 24 d8 03 00 00 48 8b 00 48 85 c0 74 40 48 8b b3 30 ff ff ff <48> 39
[Kernel-packages] [Bug 1877388] Re: If DVD drive is present system very often fails to start-up
OK, I've installed those (at first I kept trying and failing to install https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc5/linux-image- unsigned-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb , but it worked once I installed https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.7-rc5/linux- modules-5.7.0-050700rc5-generic_5.7.0-050700rc5.202005101931_amd64.deb first ) What next? 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/1877388 Title: If DVD drive is present system very often fails to start-up Status in linux package in Ubuntu: Incomplete Bug description: Whenever I power down, upon next boot the system just hangs with Ubuntu at the bottom of the screen and the circle above going around and around forever. It happens nearly every ime I power down, but not every single time. Rebooting rather that powering down works quite often. At first when thing hung I would just hard power off by holding down the power key. Then I'd use the live usb I installed with to run Disks app. More often than not the vfat W95 FAT32 partition at sda1 was damaged. The first repair would fail. The second repair would succeed. And then I'd be able to boot into my system again. After chatting about it a little with EriC^^ in #ubuntu on IRC I learned how to do Alt+Fn+PrtSc S, U, B or S, U, O. Sometimes just doing either of those on the hang screen would result in it booting up fine next time. Sometimes not. After installing 20.04 (a fresh install on a brand new Samsung 860 EVO 1TB sdd hard drive) I copied back all the files in my home direct that I'd backed from 18.04, including hidden files. This confused Firefox so I had to delete related folders and then unintall and reinstall to stop Firefox being confused. This might have nothing whatsoever to do with this issue, just mentioning it just in case something else is similarly confused. EriC^^ suggested I try adding another user and seeing if the issue went away. On the first test (and some but not all subsequent tests) it did seem that TestUser could power down and reboot fine. But actually it didn't seem that different. I powered down, rebooted, used live usb to repair Disk over and over again for hours trying to find a pattern as to when it happened and when it didn't, but failed to find any fixed pattern. Eventually at one point it was taking a while to power down (or reboot, I forget) and so I hit Esc and spotted that it had failed to unmount /cdrom ... ... so then I thought I'd try completely removing my DVD/CDRW drive and that made the issue go away. Before filing this I put the DVD drive back in (but haven't since rebooted), so not sure if apport has picked up it's details or not? Perhaps I'll need to re-file the bug after booting with it present? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: plymouth 0.9.4git20200323-0ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 15:09:23 2020 DefaultPlymouth: /usr/share/plymouth/themes/bgrt/bgrt.plymouth InstallationDate: Installed on 2020-04-26 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip Fingerprint Sensor Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/3p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M |__ Port 3: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: LENOVO 4384WCV ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=9ce94e7a-53bd-4507-ae31-93a2392b2da2 ro quiet splash vt.handoff=7 SourcePackage: plymouth TextPlymouth: /usr/share/plymouth/themes/ubuntu-text/ubuntu-text.plymouth UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/26/2010 dmi.bios.vendor: LENOVO
[Kernel-packages] [Bug 1865471] Re: USB 3.1 Gen 1 not work after using suspend
"pcie_aspm=off" on grub or enter the console don't help. -- 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/1865471 Title: USB 3.1 Gen 1 not work after using suspend Status in linux package in Ubuntu: Incomplete Bug description: Good morning. I use "suspend"(settings -> energy -> When the shutdown...) on 18.04. Each wake up, USB ports 3.1 Gen 1 don't work (only those on the motherboard on the back of the case). --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: christophe 1648 F pulseaudio /dev/snd/controlC2: christophe 1648 F pulseaudio /dev/snd/controlC0: christophe 1648 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-02-18 (14 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: lono wireless extensions. enp6s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A320M-S2H (rev. 1.x) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=9757d7ed-95dd-47d2-a3a7-80be35d05879 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.173.15 RfKill: Tags: bionic Uname: Linux 5.3.0-40-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50 dmi.board.asset.tag: Default string dmi.board.name: A320M-S2H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50:bd11/28/2019:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: A320M-S2H dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865471/+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 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
I have the same problem on 20.04 on a ThinkPad P50. It started when I upgrade from 19.10. It started after some time of being running. I did a new installation of the 20.04 and the problem persists but now only after wake up and if I put it to sleep and wake up again it stops. -- 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/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac
[Kernel-packages] [Bug 1879690] Re: Docker registry doesn't stay up and keeps restarting
I noticed something unexpected with the kernel in -proposed: /proc/version_signature reverts the upstream patchlevel to 5.4.34. If there's a mistake and it's really reverting all the upstream SRU patches, I may have a problem. -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
I installed linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb then linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb (because of dependency, has to be that order), and then rebooted and selected the 994 version (I have vmlinuz-5.3.0-51-generic as default, and can also choose -53- if desired). It booted fine, and shut down seemingly correctly. Do you want me to run any diagnostics or logs? JN -- 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/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1876165] Re: Binder and ashmem drivers are missing from AWS kernel
https://lists.ubuntu.com/archives/kernel-team/2020-May/110153.html -- 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/1876165 Title: Binder and ashmem drivers are missing from AWS kernel Status in linux-aws package in Ubuntu: In Progress Status in linux-aws-5.3 package in Ubuntu: In Progress Status in linux-aws-5.3 source package in Bionic: In Progress Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in Focal: In Progress Bug description: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+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 1864061] Re: PCI/internal sound card not detected
I am still affected by this bug on focal with intel gpu/hda on kernel 5.4.0-26 Adding the value to /etc/modprobe.d/alsa-base.conf does not help me Linux Ashen-One 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux ➜ ~ lspci -v 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05) Subsystem: Acer Incorporated [ALI] Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers Flags: bus master, fast devsel, latency 0 Capabilities: Kernel driver in use: skl_uncore 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 05) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 122 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 4000-4fff [size=4K] Memory behind bridge: a300-a3ff [size=16M] Prefetchable memory behind bridge: 9000-a1ff [size=288M] Capabilities: Kernel driver in use: pcieport 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] HD Graphics 630 Flags: bus master, fast devsel, latency 0, IRQ 131 Memory at a200 (64-bit, non-prefetchable) [size=16M] Memory at b000 (64-bit, prefetchable) [size=256M] I/O ports at 5000 [size=64] Expansion ROM at 000c [virtual] [disabled] [size=128K] Capabilities: Kernel driver in use: i915 Kernel modules: i915 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31) (prog-if 30 [XHCI]) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller Flags: bus master, medium devsel, latency 0, IRQ 126 Memory at a430 (64-bit, non-prefetchable) [size=64K] Capabilities: Kernel driver in use: xhci_hcd 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Thermal Subsystem Flags: bus master, fast devsel, latency 0, IRQ 18 Memory at a432a000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel_pch_thermal Kernel modules: intel_pch_thermal 00:15.0 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #0 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Serial IO I2C Controller Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at a432b000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:15.1 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Serial IO I2C Controller #1 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family Serial IO I2C Controller Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at a432c000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: intel-lpss Kernel modules: intel_lpss_pci 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31) Subsystem: Acer Incorporated [ALI] 100 Series/C230 Series Chipset Family MEI Controller Flags: bus master, fast devsel, latency 0, IRQ 136 Memory at a432d000 (64-bit, non-prefetchable) [size=4K] Capabilities: Kernel driver in use: mei_me Kernel modules: mei_me 00:17.0 SATA controller: Intel Corporation HM170/QM170 Chipset SATA Controller [AHCI Mode] (rev 31) (prog-if 01 [AHCI 1.0]) Subsystem: Acer Incorporated [ALI] HM170/QM170 Chipset SATA Controller [AHCI Mode] Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 127 Memory at a4328000 (32-bit, non-prefetchable) [size=8K] Memory at a433 (32-bit, non-prefetchable) [size=256] I/O ports at 5080 [size=8] I/O ports at 5088 [size=4] I/O ports at 5060 [size=32] Memory at a432e000 (32-bit, non-prefetchable) [size=2K] Capabilities: Kernel driver in use: ahci Kernel modules: ahci 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3 (rev f1) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0, IRQ 123 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: [disabled] Memory behind bridge: a420-a42f [size=1M]
[Kernel-packages] [Bug 1879987] Re: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist.
I tested with debian buster and I wasn't able to reproduce (w/o quiet parameter) I'm not yet too sure if it's a pure initramfs-tools or something introduced by a package hooks. I first thought that plymouth could have beeb a potential candidate, but I disabled it and even purge it and problem persisted. - Eric -- 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/1879987 Title: machine get stuck at boot if specified 'console=ttyS* ' doesn't exist. Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: kernel get stucks at boot if console=ttyS* is specified in the kernel cmdline and that serial HW isn't available on the system. Reproduced with: 4.4 (from Xenial), 4.15 (from Bionic), 5.4 (native, Focal) and 5.7-next (mainline) Removing the non-existent 'console=ttyS*' parameter fixes the situation. I tested it using KVM/qemu, but it has been brought to my attention that it was reproducible in VMware as well. I think it is safe to say that it is unlikely to be specifics to a certain virtualization technology type. Didn't test on baremetal yet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1879987/+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 1861284] Re: Build and ship a signed wireguard.ko
** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Committed -- 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/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+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 1861284] Re: Build and ship a signed wireguard.ko
** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+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 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
I installed both of the packages in reverse order due to dependencies. On reboot, the screen behaved the same, hanging with a white background. The latest boot log is attached. Thanks for the continued effort. ** Attachment added: "vmlinuz-5.7.0-994-generic boot.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+attachment/5375666/+files/vmlinuz-5.7.0-994-generic%20boot.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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 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/1877871/+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 1876165] Re: Binder and ashmem drivers are missing from aws-edge kernel
This needs to be enabled for {eoan,focal}/linux-aws, and then for the
bionic/linux-aws-5.3 and bionic/linux-aws-5.4 derivatives.
** No longer affects: linux-aws (Ubuntu Bionic)
** Summary changed:
- Binder and ashmem drivers are missing from aws-edge kernel
+ Binder and ashmem drivers are missing from AWS kernel
** Also affects: linux-aws (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-aws (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux-aws (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-aws (Ubuntu Eoan)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-aws (Ubuntu Focal)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Also affects: linux-aws-5.3 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux-aws-5.3 (Ubuntu Eoan)
** No longer affects: linux-aws-5.3 (Ubuntu Focal)
** Also affects: linux-aws (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux-aws-5.3 (Ubuntu Bionic)
Importance: Undecided
Status: New
** No longer affects: linux-aws (Ubuntu Bionic)
** Changed in: linux-aws-5.3 (Ubuntu)
Status: New => In Progress
** Changed in: linux-aws-5.3 (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux-aws-5.3 (Ubuntu)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux-aws-5.3 (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
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/1876165
Title:
Binder and ashmem drivers are missing from AWS kernel
Status in linux-aws package in Ubuntu:
In Progress
Status in linux-aws-5.3 package in Ubuntu:
In Progress
Status in linux-aws-5.3 source package in Bionic:
In Progress
Status in linux-aws source package in Eoan:
In Progress
Status in linux-aws source package in Focal:
In Progress
Bug description:
For quite a while the Ubuntu kernel now ships the Ashmem and Binder
drivers as part of linux-modules-extra-*. They were available on
previous linux-aws kernels but seem to have dropped with the 5.3.0
based edge kernel.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a
similar bug report I filed in the past for the GCP kernels.
Can we get both ashmem and binder enabled and added to linux-aws-edge
as they are used for Anbox Cloud?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+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 1878377] Re: USB keyboard doesn't work with rpi3 (armhf)
** No longer affects: linux-raspi2 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1878377 Title: USB keyboard doesn't work with rpi3 (armhf) Status in pi2-kernel-snap: New Status in snapd: New Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: Testing armhf image (ubuntu-core-20-armhf+raspi.img.xz) which download from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/ on Raspberry pi 3B After booting into system, the screen shows "Press enter to configure", press enter key on USB keyboard no respond. Try to connect USB keyboard via USB hub also doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/pi2-kernel-snap/+bug/1878377/+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 1876165] Re: Binder and ashmem drivers are missing from aws-edge kernel
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- 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/1876165 Title: Binder and ashmem drivers are missing from AWS kernel Status in linux-aws package in Ubuntu: In Progress Status in linux-aws source package in Eoan: In Progress Status in linux-aws source package in Focal: In Progress Bug description: For quite a while the Ubuntu kernel now ships the Ashmem and Binder drivers as part of linux-modules-extra-*. They were available on previous linux-aws kernels but seem to have dropped with the 5.3.0 based edge kernel. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849493 for a similar bug report I filed in the past for the GCP kernels. Can we get both ashmem and binder enabled and added to linux-aws-edge as they are used for Anbox Cloud? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1876165/+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 1861284] Re: Build and ship a signed wireguard.ko
** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861284 Title: Build and ship a signed wireguard.ko Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: In Progress Bug description: .. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861284/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
Please follow this one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/comments/8 -- 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/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
There are two things: - On servers, ubuntu-server depends on mdadm, so removing mdadm also removes ubuntu-server package, which means it's not really supported - In general, the installers don't offer installing like that. I don't know why we did not have a task for xenial. ** Description changed: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] - 1. Install server with subiquity to LVM + 1. Install server to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb - 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv + 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. -- 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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Released Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded
Sorry, I didn't actually test Focal and Groovy. Xenial will be supported for about a year, so I think it worth to fix it there as well; however it's relative what worth to fix and what not, as most users probably left Xenial behind already or applied a workaround if they were ever affected by this issue. On the other hand it can be a real pain if you don't know about this and just happen to convert your root LV to raid1 and then your system doesn't boot. "The supported configuration for raid1 is mdadm after all, not removing mdadm and the meta packages that depend on it and using lvm's raid support." I don't know where LVM over DM-RAID is defined as the "supported configuration" as opposed to RAID1 over LVM. I always thought about them as equal alternatives for slightly different use cases. My rule of thumb is when you can afford to get identical sized disks and mirror everything, go with LVM over DM-RAID. If you can't guarantee to have identical sized disks and need a more dynamic solution, then RAID1 over LVM (i.e. using LVM's raid1 support) is more suitable. I recommend the former in productive server environments and the latter in smaller SOHO, home servers and personal computers. If one of my disks goes bye-bye, I wouldn't want to reinstall my system or lose my documents, so I have my / and /home LVs in raid1. However I couldn't care less about my Steam library because I can just re-download the games anytime, so I don't have it mirrored, as I'd rather not want it to use twice the precious disk space. -- 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/1509717 Title: Wily LVM-RAID1 – md: personality for level 1 is not loaded Status in linux package in Ubuntu: Invalid Status in lvm2 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in lvm2 source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in lvm2 source package in Cosmic: Won't Fix Status in linux source package in Disco: Invalid Status in lvm2 source package in Disco: Won't Fix Status in linux source package in Eoan: Invalid Status in lvm2 source package in Eoan: Fix Released Status in lvm2 package in Debian: Incomplete Bug description: [Impact] system does not boot after converting lvm volume to raid1 w/o having mdadm installed. [Test case] 1. Install server with subiquity to LVM 2. Add second disk to it 3. Run pvcreate /dev/vdb 4. Run vgextend ubuntu-vg /dev/vdb 5. Run lvconvert -m1 --type raid1 ubuntu-vg/lv Reboot and check that it still boots. 6. Remove mdadm 7. Upgrade to lvm2 from proposed Reboot and check that it still boots. 8. Downgrade lvm2 to release Reboot and check that it fails to boot [Regression potential] Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier. [Original bug report] After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot. I get the following message each time LVM tries to activate a raid1 LV: md: personality for level 1 is not loaded! Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509717/+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 1879185] Re: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx
I'm running Linux Mint 19.3 Mate. I'm willing to put up a VirtualBox VM in 20.04, but really can't do a reinstall right now, as there's about a weeks' worth of custom updates. (I write application software for numerical stuff, but can't pretend knowledge of kernel / module level stuff.) However, am willing to try what I can. Prof. J C Nash -- 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/1879185 Title: fails with kernel 5.3 on linux mint, HP-Laptop-14-cm0xxx Status in linux package in Ubuntu: Incomplete Bug description: I reset the previous kernel to be able to post, because it is very difficult to work like this, this happens randomly, intermittently with each application or without having anything open. It happened from the last update to kernel 5.3, I suppose that it is the very new laptop since in another partition I have Kali and it happens the same. I appreciate your help, I list the characteristics of this laptop :roll: ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ inxi -Fxz System: Host: ydhm-HP-Laptop-14-cm0xxx Kernel: 5.0.0-32-generic x86_64 bits: 64 compiler: gcc v: 7.4.0 Desktop: Xfce 4.14.1 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic Machine: Type: Laptop System: HP product: HP Laptop 14-cm0xxx v: N/A serial: Mobo: HP model: 84A2 v: 84.24 serial: UEFI: AMI v: F.42 date: 07/03/2019 Battery: ID-1: BAT0 charge: 28.9 Wh condition: 40.8/40.8 Wh (100%) model: Hewlett-Packard Primary status: Charging CPU: Topology: Dual Core model: AMD Ryzen 3 2200U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen L2 cache: 1024 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 19962 Speed: 1433 MHz min/max: 1600/2500 MHz Core speeds (MHz): 1: 1400 2: 1398 3: 1490 4: 1441 Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Hewlett-Packard driver: amdgpu v: kernel bus ID: 04:00.0 Display: x11 server: X.Org 1.20.5 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 1366x768~60Hz OpenGL: renderer: AMD RAVEN (DRM 3.27.0 5.0.0-32-generic LLVM 9.0.0) v: 4.5 Mesa 19.2.8 direct render: Yes Audio: Device-1: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.1 Device-2: AMD vendor: Hewlett-Packard driver: N/A bus ID: 04:00.5 Device-3: AMD vendor: Hewlett-Packard driver: snd_hda_intel v: kernel bus ID: 04:00.6 Sound Server: ALSA v: k5.0.0-32-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus ID: 02:00.0 IF: eno1 state: down mac: Device-2: Realtek vendor: Hewlett-Packard driver: N/A port: e000 bus ID: 03:00.0 Device-3: D-Link DWA-125 Wireless N 150 Adapter(rev.A3) [Ralink RT5370] type: USB driver: rt2800usb bus ID: 1-3:3 IF: wlxacf1df084ac8 state: up mac: Drives: Local Storage: total: 931.51 GiB used: 23.91 GiB (2.6%) ID-1: /dev/sda vendor: HGST (Hitachi) model: HTS541010B7E610 size: 931.51 GiB Partition: ID-1: / size: 139.20 GiB used: 21.62 GiB (15.5%) fs: ext4 dev: /dev/sda5 Sensors: System Temperatures: cpu: 45.1 C mobo: N/A gpu: amdgpu temp: 45 C Fan Speeds (RPM): N/A Info: Processes: 199 Uptime: 27m Memory: 3.38 GiB used: 1.18 GiB (35.0%) Init: systemd runlevel: 5 Compilers: gcc: 7.5.0 Shell: bash v: 4.4.20 inxi: 3.0.32 / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no / ydhm@ydhm-HP-Laptop-14-cm0xxx:~$ mokutil --sb-state SecureBoot disabled Platform is in Setup Mode Ps: I also don't have wifi and bluetooth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879185/+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 1880103] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375616/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375617/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375619/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375620/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375614/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375621/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375623/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375622/+files/PulseList.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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375613/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375624/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1880103] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375618/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1877871] Re: [radeon] X windows hangs following upgrade from 18.04 to 20.04
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2020-05-20/ Download and install the following deb: linux-image-unsigned-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb linux-modules-5.7.0-994-generic_5.7.0-994.202005192206_amd64.deb -- 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/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Incomplete Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 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/1877871/+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 1880103] Re: Awaking problem after suspend mode still happens
apport information ** Tags added: apport-collected tessa ** Description changed: - 101 kernel seems to be better than 99, when the problem happened almost - every time. Nevertheless, it happened again with 2+days uptime and - suspending over night. Maybe it depends on my wireless keyboard? I tried - Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. + 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio + /dev/snd/controlC2: waldi 1668 F pulseaudio + /dev/snd/controlC0: waldi 1668 F pulseaudio + /dev/snd/controlC1: waldi 1668 F pulseaudio + CurrentDesktop: X-Cinnamon + DistroRelease: Linux Mint 19.1 + HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 + InstallationDate: Installed on 2019-02-27 (449 days ago) + InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 + IwConfig: + lono wireless extensions. + + enp6s0no wireless extensions. + + enp5s0no wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-101-generic N/A + linux-backports-modules-4.15.0-101-generic N/A + linux-firmware 1.173.18 + RfKill: + + Tags: tessa + Uname: Linux 4.15.0-101-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers + _MarkForUpload: True + dmi.bios.date: 01/18/2012 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 0501 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: P8H61-M LX2 + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Asset-1234567890 + dmi.chassis.type: 3 + dmi.chassis.vendor: Chassis Manufacture + dmi.chassis.version: Chassis Version + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375612/+files/AlsaInfo.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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log
[Kernel-packages] [Bug 1880103] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1880103/+attachment/5375615/+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/1880103 Title: Awaking problem after suspend mode still happens Status in linux package in Ubuntu: Incomplete Bug description: 101 kernel seems to be better than 99, when the problem happened almost every time. Nevertheless, it happened again with 2+days uptime and suspending over night. Maybe it depends on my wireless keyboard? I tried Alt+SysRq reisub twice, but it didn't work. Mint Cinnamon 19.1, desktop. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC2D0c: waldi 1668 F...m pulseaudio /dev/snd/controlC2: waldi 1668 F pulseaudio /dev/snd/controlC0: waldi 1668 F pulseaudio /dev/snd/controlC1: waldi 1668 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 HibernationDevice: RESUME=UUID=018b3f92-7678-b1d9-8157-f8388f5198a2 InstallationDate: Installed on 2019-02-27 (449 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 IwConfig: lono wireless extensions. enp6s0no wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=e74e78ea-7a9d-41a9-839b-e32c0343041f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-101-generic N/A linux-backports-modules-4.15.0-101-generic N/A linux-firmware 1.173.18 RfKill: Tags: tessa Uname: Linux 4.15.0-101-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 01/18/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H61-M LX2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0501:bd01/18/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H61-MLX2:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1880103/+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 1878749] Re: Kernel bug when running btrfs balance
Hmm, could you please try 20.04? I wonder how you made rootfs Btrfs? ** 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/1878749 Title: Kernel bug when running btrfs balance Status in linux package in Ubuntu: Incomplete Bug description: syslog extract: May 15 00:38:28 rpi4 kernel: [ 1464.345380] kernel BUG at /build/linux-raspi2-5.3-5IVhed/linux-raspi2-5.3-5.3.0/fs/btrfs/relocation.c:4729! May 15 00:38:28 rpi4 kernel: [ 1464.355281] Internal error: Oops - BUG: 0 [#1] SMP May 15 00:38:28 rpi4 kernel: [ 1464.360141] Modules linked in: xt_nat iptable_nat dm_crypt nls_ascii algif_skcipher af_alg ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 xt_comment btsdio nf_log_ipv4 nf_log_common bluetooth bcm2835_v4l2(CE) xt_LOG ecdh_generic bcm2835_mmal_vchiq(CE) ecc vc_sm_cma(CE) xt_multiport v4l2_common xt_recent videobuf2_vmalloc videobuf2_memops brcmfmac videobuf2_v4l2 brcmutil videobuf2_common cfg80211 videodev xt_limit xt_tcpudp raspberrypi_hwmon mc xt_addrtype rpivid_mem spidev uio_pdrv_genirq uio xt_conntrack ip6table_filter ip6_tables nf_conntrack_netbios_ns nf_conntrack_broadcast nf_nat_ftp nf_nat nf_conntrack_ftp nf_conntrack nf_defrag_ipv6 sch_fq_codel nf_defrag_ipv4 iptable_filter bpfilter iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear broadcom bcm_phy_lib hid_generic May 15 00:38:28 rpi4 kernel: [ 1464.360198] usbhid mdio_bcm_unimac crct10dif_ce sdhci_iproc genet gpio_regulator phy_generic fixed uas usb_storage aes_neon_bs aes_neon_blk crypto_simd cryptd aes_arm64 May 15 00:38:28 rpi4 kernel: [ 1464.464074] CPU: 0 PID: 8225 Comm: btrfs-balance Tainted: G C E 5.3.0-1023-raspi2 #25~18.04.1-Ubuntu May 15 00:38:28 rpi4 kernel: [ 1464.474482] Hardware name: Raspberry Pi 4 Model B Rev 1.2 (DT) May 15 00:38:28 rpi4 kernel: [ 1464.480395] pstate: 2045 (nzCv daif +PAN -UAO) May 15 00:38:28 rpi4 kernel: [ 1464.485330] pc : btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.490928] lr : __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.496133] sp : 13b437b0 May 15 00:38:28 rpi4 kernel: [ 1464.499487] x29: 13b437b0 x28: May 15 00:38:28 rpi4 kernel: [ 1464.504870] x27: 0001 x26: 0001 May 15 00:38:28 rpi4 kernel: [ 1464.510253] x25: 9c0ac32c4a80 x24: 9c0bb321c618 May 15 00:38:28 rpi4 kernel: [ 1464.515634] x23: 0001 x22: 9c0b63242a50 May 15 00:38:28 rpi4 kernel: [ 1464.521016] x21: 9c0b23e51ef0 x20: 9c0b4f111000 May 15 00:38:28 rpi4 kernel: [ 1464.526399] x19: 9c0b74bb5000 x18: May 15 00:38:28 rpi4 kernel: [ 1464.531780] x17: x16: 40af26f8be78 May 15 00:38:28 rpi4 kernel: [ 1464.537163] x15: x14: May 15 00:38:28 rpi4 kernel: [ 1464.542545] x13: x12: May 15 00:38:28 rpi4 kernel: [ 1464.547926] x11: x10: 9c0b10e83a40 May 15 00:38:28 rpi4 kernel: [ 1464.553308] x9 : 9c0aca004750 x8 : 40af2775b9e7 May 15 00:38:28 rpi4 kernel: [ 1464.558690] x7 : 9c0b578814e1 x6 : 9c0b578814e0 May 15 00:38:28 rpi4 kernel: [ 1464.564071] x5 : 9c0b552b59c0 x4 : 9c0b552b59c0 May 15 00:38:28 rpi4 kernel: [ 1464.569452] x3 : 9c0b63242a50 x2 : 00096be7 May 15 00:38:28 rpi4 kernel: [ 1464.574833] x1 : x0 : 012e979b4000 May 15 00:38:28 rpi4 kernel: [ 1464.580216] Call trace: May 15 00:38:28 rpi4 kernel: [ 1464.582735] btrfs_reloc_cow_block+0x34c/0x3a0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.587979] __btrfs_cow_block+0x368/0x600 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.592869] btrfs_cow_block+0x100/0x218 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.597583] btrfs_search_slot+0x560/0x930 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.602475] do_relocation+0x408/0x5b8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.607014] relocate_tree_blocks+0x4f8/0x5c0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.612170] relocate_block_group+0x3dc/0x638 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.617325] btrfs_relocate_block_group+0x18c/0x2d8 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.623009] btrfs_relocate_chunk+0x48/0xe0 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.627988] __btrfs_balance+0x864/0xa38 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.632703] btrfs_balance+0x434/0x748 [btrfs] May 15 00:38:28 rpi4 kernel: [ 1464.637301] balance_kthread+0x38/0x70 [btrfs] May 15 00:38:28
[Kernel-packages] [Bug 1878480] Re: Centrino Wireless-N 1000 [Condor Peak]
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc6/ If latest kernel doesn't work then we need to do kernel bisection... -- 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/1878480 Title: Centrino Wireless-N 1000 [Condor Peak] Status in linux package in Ubuntu: Incomplete Bug description: After upgrade to 20.04 my wireless starts to be very unstable, it goes from 65mbs to 1mbs. I need to reenable wirless ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.29.34 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: miguel 2846 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 13 20:57:07 2020 HibernationDevice: RESUME=UUID=0f71c458-758c-439d-9dd0-b7ddcd620218 MachineType: Alienware M14xR1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fcba8370-4563-4d59-8a53-f1a70ebb8e1d ro quiet splash nouveau.blacklist=1 nvidia-drm.modeset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-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: 12/24/2011 dmi.bios.vendor: Alienware dmi.bios.version: A08 dmi.board.name: M14xR1 dmi.board.vendor: Alienware dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Alienware dmi.chassis.version: A08 dmi.modalias: dmi:bvnAlienware:bvrA08:bd12/24/2011:svnAlienware:pnM14xR1:pvrA08:rvnAlienware:rnM14xR1:rvrA08:cvnAlienware:ct8:cvrA08: dmi.product.family: 103C_5335KV dmi.product.name: M14xR1 dmi.product.sku: xxx123x#ABA dmi.product.version: A08 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878480/+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 1879690] Re: Docker registry doesn't stay up and keeps restarting
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- eoan' to 'verification-done-eoan'. If the problem still exists, change the tag 'verification-needed-eoan' to 'verification-failed-eoan'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-eoan -- 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/1879690 Title: Docker registry doesn't stay up and keeps restarting Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Impact] The change applied for bug 1857257 and its followup fix bug 1876645, which were released on focal and eoan -updates, introduced a regression on overlayfs, breaking docker snap. [Test case] See original bug report. [Fix] While we don't have a final fix the solution for now is to revert the following commits: UBUNTU: SAUCE: overlayfs: fix shitfs special-casing UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay [Regression potential] Low. Reverting these two commits will introduce back the issue reported on bug 1857257, but will fix the other use cases which was broken by the latest release. Original bug report. --- Tested kernels: Focal 5.4.0-31.35 Eoan 5.3.0-53.47 To reproduce: 1) Spin up a cloud image 2) snap install docker 3) auth_folder=/var/snap/docker/common/auth 4) mkdir -p $auth_folder 5) docker run --entrypoint htpasswd registry:2 -Bbn user passwd > $auth_folder/htpasswd 6) docker run -d -p 5000:5000 --restart=always --name registry \ -v $auth_folder:/auth \ -e "REGISTRY_AUTH=htpasswd" \ -e "REGISTRY_AUTH_HTPASSWD_REALM=Registry Realm" \ -e REGISTRY_AUTH_HTPASSWD_PATH=/auth/htpasswd \ registry:2 On a good kernel 'docker ps' shows something like: # docker ps CONTAINER IDIMAGE COMMAND CREATED STATUS PORTSNAMES a346b65b4509registry:2 "/entrypoint.sh /etc…" 14 seconds ago Up 12 seconds 0.0.0.0:5000->5000/tcp registry On a bad kernel: docker ps CONTAINER IDIMAGE COMMAND CREATED STATUSPORTS NAMES 0322374f1b1dregistry:2 "/entrypoint.sh /etc…" 5 seconds ago Restarting (2) 1 second ago registry Note status 'Restarting' on the bad kernel. This seems to be introduce by any of the following commits: b3bdda24f1bc UBUNTU: SAUCE: overlayfs: fix shitfs special-casing 6f18a8434050 UBUNTU: SAUCE: overlayfs: use shiftfs hacks only with shiftfs as underlay 629edd70891c UBUNTU: SAUCE: shiftfs: record correct creator credentials cfaa482afb97 UBUNTU: SAUCE: shiftfs: fix dentry revalidation Kernels that don't have these commits seem fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879690/+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 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
Disable misbehaved ACPI GPE as a temporary workaround: https://unix.stackexchange.com/questions/242013/disable-gpe-acpi-interrupts-on-boot ** 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/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_add_reference +
[Kernel-packages] [Bug 1878918] Re: Button power don’t shutdown
Did it happen under 19.10? ** 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/1878918 Title: Button power don’t shutdown Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I realized that since I updated the system to version 20.04 it is not responding when I press the shutdown button on my notebook, even though in the power management in the settings it is to shut down when I press it. When I put it to suspend, he responds, but when I put it off he does nothing ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neto 1092 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 15 10:19:38 2020 InstallationDate: Installed on 2020-02-28 (76 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-09 (5 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P13ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-AD5BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C/532U3C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878918/+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 1878919] Re: kworker/0:1+kacpid uses 100% of one CPU core
Did this issue happen to 16.04.1? -- 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/1878919 Title: kworker/0:1+kacpid uses 100% of one CPU core Status in linux package in Ubuntu: Incomplete Bug description: At some point, kworker/0:1+kacpid starts using 100% of one CPU's core; this can be seen in the top command. I captured some performance data via the following command: $ perf record -g -a sleep 10 Then, perf report gives the following: Samples: 75K of event 'cycles', Event count (approx.): 44710762967 Children Self Command Shared Object Symbol + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] ret_from_fork + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] kthread + 65,46% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] worker_thread + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] process_one_work + 65,44% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_os_execute_deferred + 65,33% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_asynch_execute_gpe_method + 65,32% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_evaluate + 65,26% 0,00% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_execute_method + 65,16% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_aml + 61,00% 0,94% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_parse_loop + 37,83% 0,75% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_exec_end_op + 18,33% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_evaluate_name_path + 16,12% 0,23% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_lookup + 15,79% 0,20% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_and_enter + 15,23%14,99% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ns_search_one_scope + 14,38% 0,00% swapper [kernel.kallsyms] [k] secondary_startup_64 + 14,38% 0,02% swapper [kernel.kallsyms] [k] cpu_startup_entry + 14,31% 0,12% swapper [kernel.kallsyms] [k] do_idle + 13,79% 0,00% swapper [kernel.kallsyms] [k] start_secondary + 12,92% 0,03% swapper [kernel.kallsyms] [k] call_cpuidle + 12,89% 0,00% swapper [kernel.kallsyms] [k] cpuidle_enter + 12,85% 0,05% swapper [kernel.kallsyms] [k] cpuidle_enter_state + 12,35% 2,15% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_object_reference + 12,05% 0,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_to_value + 10,40% 0,04% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_resolve_node_to_value +9,90% 0,44% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_create_operand +9,50% 0,05% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_read_data_from_field +9,39% 0,06% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_field_datum_io +9,26% 0,12% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_access_region +9,23% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_get_next_namepath +9,15% 1,28% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_update_ref_count.part.0 +9,01% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ev_address_space_dispatch +8,96% 0,14% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_extract_from_field +8,78% 7,70% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ex_system_memory_space_handler +7,81% 0,22% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_remove_reference +6,63% 6,43% swapper [kernel.kallsyms] [k] intel_idle +5,31% 0,68% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ps_create_op +5,12% 0,08% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ut_add_reference +4,89% 0,07% kworker/0:1+kac [kernel.kallsyms] [k] acpi_ds_delete_result_if_not_used +4,71% 0,09% kworker/0:1+kac [kernel.kallsyms]
