[Kernel-packages] [Bug 1873052] Re: Showing two cursors after login
The bug's still present, but the fix in #7 works for me too. "as workaround editing /etc/gdm3/custom.conf to uncomment `WaylandEnable=false` should fix 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/1873052 Title: Showing two cursors after login Status in gnome-shell package in Ubuntu: Confirmed Status in linux package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: In Progress Status in gnome-shell source package in Focal: Confirmed Status in linux source package in Focal: Confirmed Status in mutter source package in Focal: Confirmed Status in xorg-server source package in Focal: Confirmed Bug description: Showing two cursors after login to ubuntu-desktop. One cursor moves and is scaled, and one is stationary mid screen and not scaled. The moving cursor does not appear on screenshots, making it difficult to upload a screenshot. Previously reported: https://gitlab.gnome.org/GNOME/mutter/issues/904 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1827428 Package: mutter 3.36.1-3ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 15 20:06:53 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-31 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873052/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911578] Re: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
** Changed in: linux (Ubuntu) Status: Confirmed => 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/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Invalid Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+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 1912032] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDel
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
I changed the package name from "meta" to just linux to get apport- collect to work. Hope that's OK. -- 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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: Confirmed Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi
[Kernel-packages] [Bug 1912032] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453633/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.ven
[Kernel-packages] [Bug 1912032] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453635/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: De
[Kernel-packages] [Bug 1912032] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453634/+files/RfKill.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: De
[Kernel-packages] [Bug 1912032] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453636/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.v
[Kernel-packages] [Bug 1912032] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453629/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis
[Kernel-packages] [Bug 1912032] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453630/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9
[Kernel-packages] [Bug 1912032] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453632/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis
[Kernel-packages] [Bug 1912032] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453631/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.c
[Kernel-packages] [Bug 1912032] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453624/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1912032] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453627/+files/Lsusb-t.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453622/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chass
[Kernel-packages] [Bug 1912032] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453625/+files/Lspci-vt.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendo
[Kernel-packages] [Bug 1912032] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453628/+files/Lsusb-v.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor:
[Kernel-packages] [Bug 1912032] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453621/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell I
[Kernel-packages] [Bug 1912032] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453623/+files/IwConfig.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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendo
[Kernel-packages] [Bug 1912032] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1912032/+attachment/5453626/+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/1912032 Title: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel Status in linux package in Ubuntu: New Bug description: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lance 829 F pulseaudio /dev/snd/controlC1: lance 829 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. Latitude E6510 Package: linux (not installed) PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-38-generic N/A linux-backports-modules-5.8.0-38-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.8.0-38-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: 05/12/2017 dmi.bios.release: 4.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0N5KHN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell
[Kernel-packages] [Bug 1912032] Re: Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
apport information ** Package changed: linux-meta-hwe-5.8 (Ubuntu) => linux (Ubuntu) ** Tags added: apport-collected ** Description changed: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lance 829 F pulseaudio + /dev/snd/controlC1: lance 829 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2021-01-15 (0 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + MachineType: Dell Inc. Latitude E6510 + Package: linux (not installed) + PccardctlIdent: + Socket 0: +no product info available + PccardctlStatus: + Socket 0: +no card + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcFB: 0 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic root=UUID=2acd08e5-6bf2-46ec-bd67-684d0523da41 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 + RelatedPackageVersions: + linux-restricted-modules-5.8.0-38-generic N/A + linux-backports-modules-5.8.0-38-generic N/A + linux-firmware1.187.2 + Tags: focal + Uname: Linux 5.8.0-38-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: 05/12/2017 + dmi.bios.release: 4.6 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: A17 + dmi.board.name: 0N5KHN + dmi.board.vendor: Dell Inc. + dmi.board.version: A00 + dmi.chassis.type: 9 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvrA17:bd05/12/2017:br4.6:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn0N5KHN:rvrA00:cvnDellInc.:ct9:cvr: + dmi.product.name: Latitude E6510 + dmi.product.version: 0001 + dmi.sys.vendor: Dell Inc. ** Attachment added: "AlsaInfo.txt" h
[Kernel-packages] [Bug 1910894] Re: Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS
I just found that I'm actually on a testing kernel instead of generic : dpkg --list | grep linux-image ii linux-image-unsigned-5.0.0-37-generic 5.0.0-37.41+redmiv3 amd64Linux kernel image for version 5.0.0 on 64 bit x86 SMP This was to fix the issue I raised before: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846148 However the wireless also had problem with wireless but I didn't keep track of that bug. I guess the fix for both the linked issue and wireless are in this test kernel that I'm using. -- 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/1910894 Title: Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS Status in linux package in Ubuntu: Confirmed Bug description: run apt update && apt upgrade. after that booted with kernerl 5.4 LTS Wireless connection keep on asking for password or encryption keys for wi-fi which are already linked properly with 5.0.0-37-generic. Laptop: Redmi Book 14 2019 lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 uname -r 5.0.0-37-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910894/+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 1912032] [NEW] Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel
You have been subscribed to a public bug: This is really the result of the 20.04.1 iso images being built with 'linux-generic-hwe-20.04' which shouldn't have been included until 20.04.2 is released next month. For more detailed info about that please see bug #1911614. This was a fresh install of Ubuntu using the 20.04.1 media. During install I chose to download updates as well as installing 3rd party drivers. Towards the very end of the install I was warned that nvidia-340 installation couldn't complete successfully followed by a message that other issues regarding updates or removal of unneeded packages may be encountered. Below is a detailed list of the various boot processes but the logs may also show several aborted boot processes where I hit Ctl+Alt+Del after failing to get the grub menu to appear during boot. Initial boot resulted in a black screen with an occasionally blinking cursor. I mean I'd see the cursor blink maybe every 20 to 30 seconds. And I couldn't bring up a TTY - at least not that I could see. Second boot I added the nomodeset boot parameter to the 5.8 series kernel. Still just a black screen but I was able to pull up a TTY and sudo reboot. Third boot I added nomodeset to the 5.4 series kernel and this time I got stuck in a log-in loop. I had selected auto-login during installation. Fourth boot I went for the 5.4 series kernel recovery mode, then enabled networking, and stumbled around in the terminal trying to figure out what nvidia packages were installed. After I figured out what was installed I purged nvidia-340 followed by apt autoremove and reboot. Success! The 5.8 series kernel booted with no intervention :^) So specific to this bug it's just that the nvidia driver failed to install properly but the real root of the problem is that Focal should not be getting 5.8 series kernel updates (reference bug #1911614). I also noticed on my daily driver that all of the 5.8 series kernel updates have shown up as "other updates", or at least none of them have shown up as security updates so I'm considering this a potential security problem and I'll let those who know what they're doing weigh in on that. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic-hwe-20.04 5.8.0.38.43~20.04.23 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 15 18:24:02 2021 InstallationDate: Installed on 2021-01-15 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Nvidia-340 fails to build during Focal install due to upgrade to 5.8 kernel https://bugs.launchpad.net/bugs/1912032 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1910894] Re: Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS
apport-collect 1910894 ERROR: connecting to Launchpad failed: Unable to find the server at api.launchpad.net ** 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/1910894 Title: Wireless worked in 5.0.0-37-generic doesn't work in 5.4 LTS Status in linux package in Ubuntu: Confirmed Bug description: run apt update && apt upgrade. after that booted with kernerl 5.4 LTS Wireless connection keep on asking for password or encryption keys for wi-fi which are already linked properly with 5.0.0-37-generic. Laptop: Redmi Book 14 2019 lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 uname -r 5.0.0-37-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910894/+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 1858463] Re: Desktop freezing while SSD under heavy load
[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/1858463 Title: Desktop freezing while SSD under heavy load Status in linux package in Ubuntu: Expired Bug description: Every time my SSD is under heavy writing load (e.g. copying large files from a USB stick, or downloading an ISO from a fast website), the entire Ubuntu (Gnome) desktop, including mouse pointer, freezes. My computer is an Asus UX410UAK with a Micron 1100 SSD. guillaume@massada:~$ sudo dmidecode | grep -i UX Version: UX410UAK.308 Product Name: UX410UAK Family: UX Product Name: UX410UAK guillaume@massada:~$ cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: ATA Model: Micron_1100_MTFD Rev: A020 Type: Direct-AccessANSI SCSI revision: 05 This is a recurring problem, and has always been with this machine (including previous kernel and Ubuntu versions, at least for the past 2 years). ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jan 6 18:20:01 2020 InstallationDate: Installed on 2018-07-28 (526 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-meta UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1685 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK 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 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-25-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-25-generic N/A linux-backports-modules-5.4.0-25-generic N/A linux-firmware1.187 Tags: focal wayland-session Uname: Linux 5.4.0-25-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: 04/17/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.312 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.312:bd04/17/2019:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: guillaume 1423 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-11 (208 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK Package: linux (not installed) ProcE
[Kernel-packages] [Bug 1904186] Re: Linux kernel 5.8 is now EOL on kernel.org
[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/1904186 Title: Linux kernel 5.8 is now EOL on kernel.org Status in linux package in Ubuntu: Expired Bug description: According to kernel.org, the 5.8 branch of the Linux kernel is now End-Of-Life (EOL). This mean it will not be supported as much as the 5.9 branch will. It should be better to switch Groovy and Hisute to 5.9 branch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904186/+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 1904343] Re: WiFi Working, Wired connection not.
[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/1904343 Title: WiFi Working, Wired connection not. Status in linux package in Ubuntu: Expired Bug description: Yesterday I wanted to move from Windows 10 to Linux (again) but I had bad luck I guess with the network-manager and its current version. My WiFi is working without any problems but the Ethernet (wired connection) is not working. Tried (installed and fully updated) Pop OS 20.10, Kubuntu 20.10, KDE Neon based on 20.04 same problem on all of them. Not working from Live USB too. Went back to Windows 10 - everything works without any problems. Tried some debugging: taking out the cable and plugging it back. No luck. Restarting the laptop - not working. Laptop model Acer ES1-512 if it matters. acer.com/ac/en/US/content/support-product/5611;-;Aspire%20ES1-512 On network, I have Broadcom and Atheros - not sure which one is for the ethernet. P.S: Whine Kubuntu was loading (the text window) I saw with red Failed - network manager online or something like that, can't really remember the whole thing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904343/+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 1855757] Re: [nvidia] Background image corrupted after standby or resume from suspend
I installed the focal-proposed updates yesterday, just checked and I can confirm the background corruption issue is still there, tho it's not as much as before. Before it used to change to a complete grey static, but now the wallpaper is still visible to an extent. I'll attach a screenshot. ** Attachment added: "Screenshot from 2021-01-16 09-44-49.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+attachment/5453618/+files/Screenshot%20from%202021-01-16%2009-44-49.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1855757 Title: [nvidia] Background image corrupted after standby or resume from suspend Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-390 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in mutter source package in Focal: Confirmed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-390 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1855757/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpa
[Kernel-packages] [Bug 1912037] 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 1912037 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/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+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 1912037] Re: No sound on Dell Latitude E6420 with Kernel 5.8.0
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1912037 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: Incomplete Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+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 1912037] [NEW] No sound on Dell Latitude E6420 with Kernel 5.8.0
Public bug reported: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman ** 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/1912037 Title: No sound on Dell Latitude E6420 with Kernel 5.8.0 Status in linux package in Ubuntu: New Bug description: Hi I have discover a odd bug on my laptop a Dell Latitude E6420 with the Kernel 5.8.0. When I try use sound on my laptop with this Kernel there is no sound. I decide to test another Kernel which is Kernel 5.4.0 and when I use it sounds comes out of the computer without any problem. The Linux I use i based on Ubuntu 20.04. And if I understand correctly there are reports that 5.8.0 has removed many sound cards and that might be the reason why my laptop doesn't have any sound with this Kernel. I hope this will be fix in the future. Yours Christer Wickman To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912037/+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 1912033] Re: Thinkpad - add palm sensor support needed for WWAN
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Alex Hung (alexhung) -- 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912033/+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 1912033] 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 1912033 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912033/+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 1912033] [NEW] Thinkpad - add palm sensor support needed for WWAN
Public bug reported: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Description changed: [Impact] - Add new palm sensor supports to Lenovo Thinkpad systems + Add new palm sensor supports to Lenovo Thinkpad systems [Fix] - thinkpad_acpi is updated to check palm sensor presence and its events + thinkpad_acpi is updated to check palm sensor presence and its events [Test] - Tested on Thinkpad systems + Tested on Thinkpad systems [Where problems could occur] - Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor - and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't - be affected either. - - There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" - - Note: On some platforms, because of an issue in the HW implementation, - the palm sensor presence may be incorrectly advertised as always - enabled even if a palm sensor is not present. The palm sensor is - intended for WWAN transmission power control and should be available - and correct on all WWAN enabled systems. It is not recommended to use - this interface for other use cases. + Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. - - Note: "thinkpad_acpi: Add palm sensor support" was cherry-picked from mainline, and - "thinkpad_acpi: correct palmsensor error checking" is cherry-picked from maintainer's - tree (git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-drivers-x86.git) + There can an issue as discussed in commit log of "thinkpad_acpi: Add + palm sensor support" + + Note: On some platforms, because of an issue in the HW implementation, + the palm sensor presence may be incorrectly advertised as always + enabled even if a palm sensor is not present. The palm sensor is + intended for WWAN transmission power control and should be available + and correct on all WWAN enabled systems. It is not recommended to use + this interface for other use cases. + + Note: "thinkpad_acpi: Add palm sensor support" was cherry-picked from + mainline, and "thinkpad_acpi: correct palmsensor error checking" is + cherry-picked from maintainer's tree + (git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- + drivers-x86.git) ** Description changed: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems [Fix] thinkpad_acpi is updated to check palm sensor presence and its events [Test] Tested on Thinkpad systems [Where problems could occur] Low risks. Only thinkpad systems are affected. Also thinkpad systems without palm sensor and without TP_HKEY_EV_PALM_DETECTED & TP_HKEY_EV_PALM_UNDETECTED events won't be affected either. There can an issue as discussed in commit log of "thinkpad_acpi: Add palm sensor support" Note: On some platforms, because of an issue in the HW implementation, the palm sensor presence may be incorrectly advertised as always enabled even if a palm sensor is not present. The palm sensor is intended for WWAN transmission power control and should be available and correct on all WWAN enabled systems. It is not recommended to use this interface for other use cases. - - Note: "thinkpad_acpi: Add palm sensor support" was cherry-picked from - mainline, and "thinkpad_acpi: correct palmsensor error checking" is - cherry-picked from maintainer's tree - (git://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- - drivers-x86.git) -- 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/1912033 Title: Thinkpad - add palm sensor support needed for WWAN Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Add new palm sensor supports to Lenovo Thinkpad systems
[Kernel-packages] [Bug 1912028] Re: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different fr
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1912028 Title: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 390.141-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 17:42:38 2021 DuplicateSignature: package:libnvidia-compute-390:390.141-0ubuntu0.20.04.1 Unpacking libnvidia-compute-390:amd64 (390.141-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-qSCzrl/39-libnvidia-compute-390_390.141-0ubuntu0.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2020-08-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1912028/+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 1912028] [NEW] package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different
Public bug reported: I ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 390.141-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 17:42:38 2021 DuplicateSignature: package:libnvidia-compute-390:390.141-0ubuntu0.20.04.1 Unpacking libnvidia-compute-390:amd64 (390.141-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-qSCzrl/39-libnvidia-compute-390_390.141-0ubuntu0.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2020-08-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal package-conflict -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1912028 Title: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: I ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libnvidia-compute-390 390.141-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Jan 15 17:42:38 2021 DuplicateSignature: package:libnvidia-compute-390:390.141-0ubuntu0.20.04.1 Unpacking libnvidia-compute-390:amd64 (390.141-0ubuntu0.20.04.1) ... dpkg: error processing archive /tmp/apt-dpkg-install-qSCzrl/39-libnvidia-compute-390_390.141-0ubuntu0.20.04.1_amd64.deb (--unpack): trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 ErrorMessage: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 InstallationDate: Installed on 2020-08-27 (141 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: nvidia-graphics-drivers-390 Title: package libnvidia-compute-390 390.141-0ubuntu0.20.04.1 failed to install/upgrade: trying to overwrite shared '/etc/OpenCL/vendors/nvidia.icd', which is different from other instances of package libnvidia-compute-390:amd64 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1912028/+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 1912027] Re: Groovy update: upstream stable patchset 2021-01-15
** Changed in: linux (Ubuntu Groovy) Status: New => In Progress ** Changed in: linux (Ubuntu Groovy) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2021-01-15 -upstream stable patchset 2021-01-15 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v5.10.3, + v5.4.86, v5.10.4 + + from git://git.kernel.org/ + + net: ipconfig: Avoid spurious blank lines in boot log + x86/split-lock: Avoid returning with interrupts enabled + exfat: Avoid allocating upcase table using kcalloc() + soc/tegra: fuse: Fix index bug in get_process_id + usb: mtu3: fix memory corruption in mtu3_debugfs_regset() + USB: serial: option: add interface-number sanity check to flag handling + USB: gadget: f_acm: add support for SuperSpeed Plus + USB: gadget: f_midi: setup SuperSpeed Plus descriptors + usb: gadget: f_fs: Re-use SS descriptors for SuperSpeedPlus + USB: gadget: f_rndis: fix bitrate for SuperSpeed and above + usb: chipidea: ci_hdrc_imx: Pass DISABLE_DEVICE_STREAMING flag to imx6ul + ARM: dts: exynos: fix roles of USB 3.0 ports on Odroid XU + ARM: dts: exynos: fix USB 3.0 VBUS control and over-current pins on Exynos5410 + ARM: dts: exynos: fix USB 3.0 pins supply being turned off on Odroid XU + coresight: tmc-etf: Fix NULL ptr dereference in tmc_enable_etf_sink_perf() + coresight: tmc-etr: Check if page is valid before dma_map_page() + coresight: tmc-etr: Fix barrier packet insertion for perf buffer + coresight: etb10: Fix possible NULL ptr dereference in etb_enable_perf() + f2fs: fix to seek incorrect data offset in inline data file + scsi: megaraid_sas: Check user-provided offsets + HID: i2c-hid: add Vero K147 to descriptor override + serial_core: Check for port state when tty is in error state + fscrypt: remove kernel-internal constants from UAPI header + fscrypt: rename DCACHE_ENCRYPTED_NAME to DCACHE_NOKEY_NAME + fscrypt: add fscrypt_is_nokey_name() + ubifs: prevent creating duplicate encrypted filenames + ext4: prevent creating duplicate encrypted filenames + f2fs: prevent creating duplicate encrypted filenames + Bluetooth: Fix slab-out-of-bounds read in hci_le_direct_adv_report_evt() + quota: Sanity-check quota file headers on load + fs: quota: fix array-index-out-of-bounds bug by passing correct argument to vfs_cleanup_quota_inode() + media: msi2500: assign SPI bus number dynamically + crypto: af_alg - avoid undefined behavior accessing salg_name + nl80211: validate key indexes for cfg80211_registered_device + md: fix a warning caused by a race between concurrent md_ioctl()s + UBUNTU: upstream stable to v5.10.3 + drm/gma500: fix double free of gma_connector + drm/aspeed: Fix Kconfig warning & subsequent build errors + drm/mcde: Fix handling of platform_get_irq() error + drm/tve200: Fix handling of platform_get_irq() error + arm64: dts: renesas: hihope-rzg2-ex: Drop rxc-skew-ps from ethernet-phy node + arm64: dts: renesas: cat875: Remove rxc-skew-ps from ethernet-phy node + soc: renesas: rmobile-sysc: Fix some leaks in rmobile_init_pm_domains() + soc: mediatek: Check if power domains can be powered on at boot time + arm64: dts: mediatek: mt8183: fix gce incorrect mbox-cells value + arm64: dts: ipq6018: update the reserved-memory node + soc: qcom: geni: More properly switch to DMA mode + Revert "i2c: i2c-qcom-geni: Fix DMA transfer race" + RDMA/bnxt_re: Set queue pair state when being queried + rtc: pcf2127: fix pcf2127_nvmem_read/write() returns + selinux: fix error initialization in inode_doinit_with_dentry() + ARM: dts: aspeed-g6: Fix the GPIO memory size + ARM: dts: aspeed: s2600wf: Fix VGA memory region location + RDMA/core: Fix error return in _ib_modify_qp() + RDMA/rxe: Compute PSN windows correctly + x86/mm/ident_map: Check for errors from ident_pud_init() + ARM: p2v: fix handling of LPAE translation in BE mode + RDMA/rtrs-clt: Remove destroy_con_cq_qp in case route resolving failed + RDMA/rt
[Kernel-packages] [Bug 1912027] [NEW] Groovy update: upstream stable patchset 2021-01-15
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 2021-01-15 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) 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/1912027 Title: Groovy update: upstream stable patchset 2021-01-15 Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: New Bug description: 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 2021-01-15 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912027/+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 1910866] Re: nvme drive fails after some time
@Marcelo So far it looks good :-) It passes the "fio" command test when A/B testing between a known bad kernel and this new kernel. I will continue running it on this machine over the weekend to ensure longer usage doesn't have any remaining issues - but looks like it resolves the issue so far :-D Thanks! $ uname -a Linux xps-13-9360 5.8.0-38-generic #43+lp1910866 SMP Fri Jan 15 20:29:27 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Thanks! I'll take a look :-) -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.0-34-generic N/A linux-backports-modules-5.8.0-34-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus:
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Hi, Andrew. I created a test kernel with the fix and it is available at: https://kernel.ubuntu.com/~mhcerri/lp1910866_linux-5.8.0-38-generic_5.8.0-38.43+lp1910866_amd64.tar.gz You can install it by extracting the tarball and installing the debian packages: $ tar xf lp1910866_linux-5.8.0-38-generic_5.8.0-38.43+lp1910866_amd64.tar.gz $ sudo apt install ./*.deb Please let us know if the test kernel solves the 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMA
[Kernel-packages] [Bug 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
Maybe contains extra information. ** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+attachment/5453569/+files/Xorg.0.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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+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 1911352] Re: Black screen on boot after 20.04 upgraded to kernel 5.8
I have the same problem on my Acer. Since Kernel 5.8.0-36 and also 5.8.0-38 Ubuntu 20.04.1 cannot start in graphics mode. (It is possible to log in on the console using e.g. Ctrl+Alt+F4 though.) With Kernel 5.4.0-58 the system works as expected. The problem occurs only on this system, which is also the only one with a Nvidia GPU (Nvidia drivers are currently not installed though because I initially suspected the updated nvidia-driver-460 were the problem.) dmidecode -t1 # dmidecode 3.2 Getting SMBIOS data from sysfs. SMBIOS 3.2.0 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: Acer Product Name: Aspire A515-54G Version: V1.16 Serial Number: I deleted it. UUID: I deleted it. Wake-up Type: Power Switch SKU Number: Family: Aspire 5 ** Attachment added: "I guess the interesting part starts at line 80." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+attachment/5453568/+files/syslog -- 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/1911352 Title: Black screen on boot after 20.04 upgraded to kernel 5.8 Status in linux package in Ubuntu: Confirmed Bug description: Yesterday Ubuntu asked me to reboot after automatic updates, and when I rebooted it doesn't start up. Sometimes it stays on the Dell logo, sometimes it goes to a black screen and doesn't get past that (not sure what causes each variation -- perhaps for reboot it does the Dell logo, cold start up it does the black screen?). After the updates it's trying to boot the 5.8.0 kernel. In the boot menu, if I manually select the 5.4.0 kernel everything works fine. So presumably it's something about the 5.8 kernel on this hardware. When this occurred I was running the Nouveau open source graphics driver. I switched to the NVIDIA driver (460) to see if that would help, but it didn't change anything. So it may or may not be graphics related. I'm attaching my /var/log/kern.log and /var/log/syslog for yesterday -- Jan 12, I think it would be around 13:30 that I first rebooted after the upgrade (and a bunch of times after that). I ran the logs through grep -v 'var-snap-lxd-common-lxd' as a huge percentage of the lines were this (presumably irrelevant): Jan 12 19:09:55 BenXPS15 kernel: [14515.297170] audit: type=1400 audit(1610431795.003:29126): apparmor="DENIED" operation="open" namespace="root//lxd-juju-804318-0_" profile="snap.juju-db.daemon" name="/proc/631/net/netstat" pid=3906 comm="ftdc" requested_mask="r" denied_mask="r" fsuid=100 ouid=100 For reference: * This is a Dell XPS 15 (9550) laptop with an NVIDIA GeForce GTX 960M (I think it's hybrid graphics). i7-6700HQ 2.6GHz with 8 cores, 256 GB SSD, 16 MB RAM. * I installed Ubuntu 20.04 Focal in August 2020, and now it says it's on "Ubuntu 20.04.1 LTS". * /proc/version_signature: Ubuntu 5.4.0-59.65-generic 5.4.78 * "sudo lspci -vnvn" output is included in the attached logs.zip --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ben4518 F pulseaudio /dev/snd/pcmC0D0p: ben4518 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-27 (138 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-59-generic root=/dev/mapper/vgubuntu-root ro quiet splash ProcVersionSignature: Ubuntu 5.4.0-59.65-generic 5.4.78 RelatedPackageVersions: linux-restricted-modules-5.4.0-59-generic N/A linux-backports-modules-5.4.0-59-generic N/A linux-firmware1.187.7 Tags: focal Uname: Linux 5.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/12/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.1 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.1:bd12/12/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911352/+subscriptions -- Mailing list: https://launchpad.net/~kerne
[Kernel-packages] [Bug 1911814] Re: Cannot install Ubuntu 18.04 LTS Alongside Pre-Installed Windows 10
Hello All. The root cause was determined to be that Ubuntu could not see the installed hard drive, which was verified using a number of commands including 'fdisk -l' from the installation environment. I had another look at the system BIOS settings and changed 'Onboard SATA Mode' from 'Intel RST Premium' to 'AHCI'. This allowed the Ubuntu 20.04 and 16.04 install to recognize the hard drive partitions during the install and still allows Windows to boot normally. I was able to complete the Ubuntu 16.04 install without difficulty after making this change. I suspect that the 18.04 would have installed correctly as well but did not validate this. 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/1911814 Title: Cannot install Ubuntu 18.04 LTS Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: Also reported for Ubuntu 16.04.4 LTS: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578 Hello. I am trying to install Ubuntu 18.04.5 LTS from newly written USB alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it did not. I had previously reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi). Secure Boot was disabled in the BIOS on the first failed attempt. I tried again with Secure Boot enabled - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1788 F pulseaudio CasperVersion: 1.394.3 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 LiveMediaBuild: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Acer Aspire TC-895 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=/casper/vmlinuz file=/cdrom/preseed/username.seed boot=casper only-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.173.19 Tags: bionic Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/19/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A0 dmi.board.name: Aspire TC-895 dmi.board.vendor: Acer dmi.board.version: V:1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A0:bd05/19/2020:svnAcer:pnAspireTC-895:pvr:rvnAcer:rnAspireTC-895:rvrV1.0:cvnAcer:ct3:cvr: dmi.product.family: Aspire T dmi.product.name: Aspire TC-895 dmi.product.sku: dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911814/+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 1911827] Re: Cannot install Ubuntu 20.04 LTS Alongside Pre-Installed Windows 10
Hello All. The root cause was determined to be that Ubuntu could not see the installed hard drive, which was verified using a number of commands including 'fdisk -l' from the installation environment. I had another look at the system BIOS settings and changed 'Onboard SATA Mode' from 'Intel RST Premium' to 'AHCI'. This allowed the Ubuntu 20.04 (and 16.04) install to recognize the hard drive partitions during the install and still allows Windows to boot normally. I was able to complete the Ubuntu 16.04 install without difficulty after making this change. I did not validate than Ubuntu 20.04 would install correctly but suspect that it would have given the same symptoms were presented. 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/1911827 Title: Cannot install Ubuntu 20.04 LTS Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: Also reported for Ubuntu 16.04.4 LTS: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578 Also reported for Ubuntu 18.04.5 LTS: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911814 Hello. I am trying to install Ubuntu 20.04.1 LTS from newly written USB alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it did not. I had previously reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi). I found an additional and more up-to-date guide here: https://help.ubuntu.com/community/Installation and as a result was able to also disable Fast Startup, but this did not resolve the issue. Secure Boot was enabled during this install attempt. I am able to proceed through the minimal install with no package upgrades or 3rd party downloads normally until I reach the "Installation type" screen. It never displays any information within the table (i.e. Device, Type, Mount point, Format?, etc.). As a result, I am not able to proceed with the install. As recommended in the first guide described above, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 6764 F pulseaudio CasperMD5CheckResult: pass CasperVersion: 1.445.1 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 LiveMediaBuild: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Acer Aspire TC-895 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-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: 05/19/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R01-A0 dmi.board.name: Aspire TC-895 dmi.board.vendor: Acer dmi.board.version: V:1.0 dmi.chassis.type: 3 dmi.chassis.vendor: Acer dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR01-A0:bd05/19/2020:svnAcer:pnAspireTC-895:pvr:rvnAcer:rnAspireTC-895:rvrV1.0:cvnAcer:ct3:cvr: dmi.product.family: Aspire T dmi.product.name: Aspire TC-895 dmi.product.sku: dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911827/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Attachment added: "journalctl -b -1 -k on focal" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+attachment/5453567/+files/journal.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/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1911578] Re: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10
Hello All. The root cause was determined to be that Ubuntu could not see the installed hard drive, which was verified using a number of commands including 'fdisk -l' from the installation environment. I had another look at the system BIOS settings and changed 'Onboard SATA Mode' from 'Intel RST Premium' to 'AHCI'. This allowed the Ubuntu 16.04 install to recognize the hard drive partitions during the install and still allows Windows to boot normally. I was able to complete the install without difficulty after making this change. Thanks for your quick response on this support request! -- 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/1911578 Title: Cannot install Ubuntu 16.04 Alongside Pre-Installed Windows 10 Status in linux package in Ubuntu: Confirmed Bug description: Hello. I am trying to install Ubuntu 16.04.4 LTS from USB (which has been used successfully in the past) alongside pre-installed Windows 10 on a new Acer Aspire TC-895-EB11 desktop. I expected that the install process would recognize the free partition created on the GPT disk, but it does not. I reviewed and followed the steps in this guide (https://askubuntu.com/questions/221835/how-do-i-install-ubuntu- alongside-a-pre-installed-windows-with-uefi) - no change. I disabled Secure Boot in the BIOS - no change. The drive & partitions do not appear to be recognized by Ubuntu. As recommended in the guide, I am submitting this bug report. Any assistance would be much appreciated! I only purchased this desktop to run Ubuntu, but would prefer to keep the Windows 10 partition usable in case I ever want to use it. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911578/+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 1855678] Re: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected
** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855678 Title: Will not suspend, if I have Native Instruments Audio Kontrol 1 connected Status in linux package in Ubuntu: Confirmed Bug description: $ lsusb .. Bus 003 Device 002: ID 17cc:0815 Native Instruments Audio Kontrol 1 .. If I have the device connected when I choose suspend to RAM then display blanks, suspend fails and system does not respond to any user input except power button. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-24-generic 5.3.0-24.26 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jarnos 1175 F pulseaudio /dev/snd/controlC0: jarnos 1175 F pulseaudio /dev/snd/controlC1: jarnos 1175 F pulseaudio /dev/snd/pcmC1D0p: jarnos 1175 F...m pulseaudio CurrentDesktop: XFCE Date: Mon Dec 9 11:10:33 2019 InstallationDate: Installed on 2019-12-05 (3 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: Dell Inc. OptiPlex 9010 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0bb9eda8-c46e-4b31-9c77-631505c56a2a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/28/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A30 dmi.board.name: 051FJ8 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 15 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA30:bd06/28/2018:svnDellInc.:pnOptiPlex9010:pvr01:rvnDellInc.:rn051FJ8:rvrA00:cvnDellInc.:ct15:cvr: dmi.product.name: OptiPlex 9010 dmi.product.sku: OptiPlex 9010 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855678/+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 1911392] Re: Touchpad no longer detected
Problem also occurs with older kernel 4.15.0-128. Just tested with an Ubuntu 20 live CD. Same problem. I therefore assume it's a hardware problem that is unrelated to 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/1911392 Title: Touchpad no longer detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on my Lenovo Ideapad 720S-13IKB stopped working yesterday. It was always working fine before that. It no longer shows up in my device list. See attached file. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-130-generic 4.15.0-130.134 ProcVersionSignature: Ubuntu 4.15.0-130.134-generic 4.15.18 Uname: Linux 4.15.0-130-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cb 1884 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 13 08:13:59 2021 InstallationDate: Installed on 2018-06-16 (941 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 81A8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-130-generic root=UUID=364c39f2-ff11-4b3f-afb9-27fc63aa44c4 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-130-generic N/A linux-backports-modules-4.15.0-130-generic N/A linux-firmware 1.173.19 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/23/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 5SCN38WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 720S-13IKB dmi.modalias: dmi:bvnLENOVO:bvr5SCN38WW:bd02/23/2018:svnLENOVO:pn81A8:pvrLenovoideapad720S-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad720S-13IKB: dmi.product.family: ideapad 720S-13IKB dmi.product.name: 81A8 dmi.product.version: Lenovo ideapad 720S-13IKB dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911392/+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 1902457] Re: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade
Problem still continues after upgrade to 5.8.0-38-generic #43-Ubuntu SMP Tue Jan 12 12:42:13 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux -- 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/1902457 Title: regression: no sound cards detected on lenovo yoga c930 after focal->groovy upgrade Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to Groovy, my sound cards no longer work. Alsa-info says "no soundcards detected" --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (465 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 007: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. 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=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 5: Dev 6, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 8: Dev 7, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 8: Dev 7, If 0, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-26-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 RelatedPackageVersions: linux-restricted-modules-5.8.0-26-generic N/A linux-backports-modules-5.8.0-26-generic N/A linux-firmware1.190 Tags: groovy Uname: Linux 5.8.0-26-generic x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: Upgraded to groovy on 2020-10-30 (2 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: False dmi.bios.date: 10/09/2018 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: 8GCN32WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA C930-13IKB dmi.ec.firmware.release: 1.32 dmi.modalias: dmi:bvnLENOVO:bvr8GCN32WW:bd10/09/2018:br1.32:efr1.32:svnLENOVO:pn81C4:pvrLenovoYOGAC930-13IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYOGAC930-13IKB: dmi.product.family: YOGA C930-13IKB dmi.product.name: 81C4 dmi.product.sku: LENOVO_MT_81C4_BU_idea_FM_YOGA C930-13IKB dmi.product.version: Lenovo YOGA C930-13IKB dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (487 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: linux (not installed) Tags: groovy Uname: Linux 5.10.0-051000rc5-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: Upgraded to groovy on 2020-10-30 (24 days ago) UserGroups: adm cdrom dialout dip i2c input lpadmin plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: XFCE DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2019-07-25 (496 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 007: ID 10c4:ea60 Silicon Labs CP210x UART Bridge Bus 001 Device 006: ID 06cb:0081 Synaptics, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81C4 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-31-generic root=/dev/mapper/xubuntu--c930-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 RelatedPackageVersions: linux-restricted-modules-5.8.0-31-generic N/A linux-backports-modules-5.8.0-31-generic N/A linux-firmware1.190.1 Tags: groovy
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
Andrew, we plan to address this in the Focal 5.8 hwe kernel and we're going to be building a test kernel. We would really appreciate you testing it since you have a reliable reproducer. -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs: linux-image-5.8.0-36-generic linux-base RelatedPackageVersions: linux-restricted-modules-5.8.
[Kernel-packages] [Bug 1910866] Re: nvme drive fails after some time
@kaihengfeng Thanks for the quick response! bug 1908555 linked there only lists groovy as a target series, I hope that this will also be applied to the focal HWE kernel :-) Also I am happy to test any kernel in a -proposed channel or PPA to confirm it fixes the issue if that helps :-) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature: Ubuntu 5.8.0-34.37-generic 5.8.18 Uname: Linux 5.8.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:56:28 2021 InstallationDate: Installed on 2020-08-15 (146 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Intel Corporation NUC8i7HVK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-34-generic root=UUID=c212e9d4-a049-4da0-8e34-971cb7414e60 ro quiet splash vt.handoff=7 RebootRequiredPkgs:
[Kernel-packages] [Bug 1911943] [NEW] pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30
Public bug reported: supposedly the bluetooth firmware from: https://launchpad.net/ubuntu/+source/linux-firmware- raspi2/3-0ubuntu1~20.04.1 should be shipped in the latest pi-kernel snap in the edge/beta channel. the BCM4345C5.hcd (as mentioned in the last changelog entry above) is essential for proper bluetooth audio playback over A2DP. the linux-firmware-raspi2 package from -proposed does not seem to be included in pi-kernel 20/edge as it should. ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1911943 Title: pi-kernel snap: broadcom bluetooth firmware missing from 5.4.0-1027.30 Status in linux-raspi package in Ubuntu: New Bug description: supposedly the bluetooth firmware from: https://launchpad.net/ubuntu/+source/linux-firmware- raspi2/3-0ubuntu1~20.04.1 should be shipped in the latest pi-kernel snap in the edge/beta channel. the BCM4345C5.hcd (as mentioned in the last changelog entry above) is essential for proper bluetooth audio playback over A2DP. the linux-firmware-raspi2 package from -proposed does not seem to be included in pi-kernel 20/edge as it should. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1911943/+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 1910866] Re: nvme drive fails after some time
OK, the fix will be in next 5.8 update: commit f62ddacc4cb141b86ed647f9dd9eeb7653b0cc43 Author: Keith Busch Date: Fri Oct 30 10:28:54 2020 -0700 Revert "nvme-pci: remove last_sq_tail" BugLink: https://bugs.launchpad.net/bugs/1908555 [ Upstream commit 38210800bf66d7302da1bb5b624ad68638da1562 ] Multiple CPUs may be mapped to the same hctx, allowing mulitple submission contexts to attempt commit_rqs(). We need to verify we're not writing the same doorbell value multiple times since that's a spec violation. Revert commit 54b2fcee1db041a83b52b51752dade6090cf952f. Link: https://bugzilla.redhat.com/show_bug.cgi?id=1878596 Reported-by: "B.L. Jones" Signed-off-by: Keith Busch Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Ian May ** Bug watch added: Red Hat Bugzilla #1878596 https://bugzilla.redhat.com/show_bug.cgi?id=1878596 -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, reset controller Jan 08 19:19:42 robot kernel: nvme nvme1: I/O 22 QID 0 timeout, reset controller Jan 08 19:21:04 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:04 robot kernel: nvme nvme1: Abort status: 0x371 Jan 08 19:21:25 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:25 robot kernel: nvme nvme1: Removing after probe failure status: -19 Jan 08 19:21:41 robot kernel: INFO: task jbd2/nvme1n1p1-:731 blocked for more than 120 seconds. Jan 08 19:21:41 robot kernel: jbd2/nvme1n1p1- D0 731 2 0x4000 Jan 08 19:21:45 robot kernel: nvme nvme1: Device not ready; aborting reset, CSTS=0x1 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993784 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123967, lost async page write Jan 08 19:21:45 robot kernel: EXT4-fs error (device nvme1n1p1): __ext4_find_entry:1535: inode #57278595: comm gsd-print-notif: reading directory lblock 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993384 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123917, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1920993320 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1833166472 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 240123909, lost async page write Jan 08 19:21:45 robot kernel: blk_update_request: I/O error, dev nvme1n1, sector 1909398624 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0 Jan 08 19:21:45 robot kernel: Buffer I/O error on dev nvme1n1p1, logical block 0, lost sync page write Jan 08 19:21:45 robot kernel: EXT4-fs (nvme1n1p1): I/O error while writing superblock ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-34-generic 5.8.0-34.37 ProcVersionSignature:
[Kernel-packages] [Bug 1899802] Re: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander
Focal Testing completed by DellEMC ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1899802 Title: [Ubuntu 21.04 FEAT] mpt3sas: Request to include the patch set which supports topology where zoning is enabled in expander Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: Request to include patch set "PATCH 00/14] mpt3sas: Add support for multi-port path topology" which will support the topologies where zoning is enabled in the expander as shown below, Zone 1 Zone 2 |-| || | HD1 . HD25 | | HD26 ..HD50| | |==| | | | | | | | | | Expander| | | |==| | | | | || | |---|-| ||---| x8| |x8 ___|__|___ |HBA | || Current driver doesn't support this type of topology and will add only one zoned drives to the OS. So to support these types of topology we need below patch set in the driver. https://marc.info/?l=linux-scsi&m=160226366707807&w=2 So, requesting you include this patch for next upcoming Ubuntu kernel release. Currently we have posted this patch set to upstream community and they yet to review this patch set. Meanwhile If I get the base kernel source code for next upcoming Ubuntu kernel then I can prepare the patches over this base kernel source and share it in this BZ. Thanks, Sreekanth To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1899802/+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 1910866] Re: nvme drive fails after some time
@kaihengfeng So v5.7 was fine and after many reboots it has been found that this commit below introduced the issue. Do I also need to find when the issue was resolved ? (between v5.8-rc1 and v5.9.10) or is this information enough ? 54b2fcee1db041a83b52b51752dade6090cf952f is the first bad commit commit 54b2fcee1db041a83b52b51752dade6090cf952f Author: Keith Busch Date: Mon Apr 27 11:54:46 2020 -0700 nvme-pci: remove last_sq_tail The nvme driver does not have enough tags to wrap the queue, and blk-mq will no longer call commit_rqs() when there are no new submissions to notify. Signed-off-by: Keith Busch Reviewed-by: Sagi Grimberg Signed-off-by: Christoph Hellwig Signed-off-by: Jens Axboe drivers/nvme/host/pci.c | 23 --- 1 file changed, 4 insertions(+), 19 deletions(-) And my $ git bisect log is the following FWIW. git bisect start # good: [3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162] Linux 5.7 git bisect good 3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162 # bad: [b3a9e3b9622ae10064826dccb4f7a52bd88c7407] Linux 5.8-rc1 git bisect bad b3a9e3b9622ae10064826dccb4f7a52bd88c7407 # bad: [ee01c4d72adffb7d424535adf630f2955748fa8b] Merge branch 'akpm' (patches from Andrew) git bisect bad ee01c4d72adffb7d424535adf630f2955748fa8b # bad: [16d91548d1057691979de4686693f0ff92f46000] Merge tag 'xfs-5.8-merge-8' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux git bisect bad 16d91548d1057691979de4686693f0ff92f46000 # good: [cfa3b8068b09f25037146bfd5eed041b78878bee] Merge tag 'for-linus-hmm' of git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma git bisect good cfa3b8068b09f25037146bfd5eed041b78878bee # good: [3fd911b69b3117e03181262fc19ae6c3ef6962ce] Merge tag 'drm-misc-next-2020-05-07' of git://anongit.freedesktop.org/drm/drm-misc into drm-next git bisect good 3fd911b69b3117e03181262fc19ae6c3ef6962ce # good: [1966391fa576e1fb2701be8bcca197d8f72737b7] mm/migrate.c: attach_page_private already does the get_page git bisect good 1966391fa576e1fb2701be8bcca197d8f72737b7 # bad: [0c8d3fceade2ab1bbac68bca013e62bfdb851d19] bcache: configure the asynchronous registertion to be experimental git bisect bad 0c8d3fceade2ab1bbac68bca013e62bfdb851d19 # bad: [84b8d0d7aa159652dc191d58c4d353b6c9173c54] nvmet: use type-name map for ana states git bisect bad 84b8d0d7aa159652dc191d58c4d353b6c9173c54 # good: [72e6329f86c714785ac195d293cb19dd24507880] nvme-fc and nvmet-fc: revise LLDD api for LS reception and LS request git bisect good 72e6329f86c714785ac195d293cb19dd24507880 # good: [e4fcc72c1a420bdbe425530dd19724214ceb44ec] nvmet-fc: slight cleanup for kbuild test warnings git bisect good e4fcc72c1a420bdbe425530dd19724214ceb44ec # good: [31fdad7be18992606078caed6ff71741fa76310a] nvme: consolodate io settings git bisect good 31fdad7be18992606078caed6ff71741fa76310a # bad: [2a5bcfdd41d68559567cec3c124a75e093506cc1] nvme-pci: align io queue count with allocted nvme_queue in nvme_probe git bisect bad 2a5bcfdd41d68559567cec3c124a75e093506cc1 # good: [6623c5b3dfa5513190d729a8516db7a5163ec7de] nvme: clean up error handling in nvme_init_ns_head git bisect good 6623c5b3dfa5513190d729a8516db7a5163ec7de # good: [74943d45eef4db64b1e5c9f7ad1d018576e113c5] nvme-pci: remove volatile cqes git bisect good 74943d45eef4db64b1e5c9f7ad1d018576e113c5 # bad: [54b2fcee1db041a83b52b51752dade6090cf952f] nvme-pci: remove last_sq_tail git bisect bad 54b2fcee1db041a83b52b51752dade6090cf952f # first bad commit: [54b2fcee1db041a83b52b51752dade6090cf952f] nvme-pci: remove last_sq_tail -- 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/1910866 Title: nvme drive fails after some time Status in linux package in Ubuntu: Confirmed Bug description: Sorry for the vague title. I thought this was a hardware issue until someone else online mentioned their nvme drive goes "read only" after some time. I tend not to reboot my system much, so have a large journal. Either way this happens once in a while. The / drive is fine, but /home is on nvme which just disappears. I reboot and everything is fine. But leave it long enough and it'll fail again. Here's the most recent snippet about the nvme drive before I restarted the system. Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 448 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 449 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 450 QID 5 timeout, aborting Jan 08 19:19:11 robot kernel: nvme nvme1: I/O 451 QID 5 timeout, aborting
[Kernel-packages] [Bug 1910840] Re: [nvidia] Xorg freeze
** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1910840 Title: [nvidia] Xorg freeze Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Bug description: After login the screen freezes with mouse pointer duplicating. No operations can be performed .Need to do hard reboot.This started happening after upgrade(5.0.58) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-52.57~18.04.1-generic 5.4.65 Uname: Linux 5.4.0-52-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jan 9 11:46:45 2021 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 5.4.0-58-generic, x86_64: installed nvidia, 390.138, 5.4.0-59-generic, x86_64: installed GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04b6] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04b6] InstallationDate: Installed on 2020-11-02 (68 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: Dell Inc. Dell System XPS L502X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-52-generic root=UUID=e6874eb1-356d-41dd-b4e2-a1f27d050215 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0YR8NN dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA12:bd09/07/2012:svnDellInc.:pnDellSystemXPSL502X:pvr:rvnDellInc.:rn0YR8NN:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: HuronRiver System dmi.product.name: Dell System XPS L502X dmi.product.sku: System SKUNumber dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1910840/+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 1911917] Re: Kernel general protection fault when using NFQUEUE iptables target
** Description changed: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING - and POSTROUTING, the kernel crashes. + and POSTROUTING, the kernel crashes. Current Focal linux-generic- + hwe-20.04 kernel (5.8.0.38.43) is not affected. + + How to reproduce: + - Set up Focal host with a packet forwarding scenario (at least two interface: client subnet -> server subnet). + + sudo sysctl net.ipv4.ip_forward=1 + sudo apt-get install build-essential python-dev libnetfilter-queue-dev + git clone https://github.com/kti/python-netfilterqueue.git + cd python-netfilterqueue + sudo python setup.py install + cd examples + sudo iptables-restore < iptables.conf.nfq # From the comment attachment + sudo ./print_and_accept.py + - Run packet through the host. + + Stack trace: [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac
[Kernel-packages] [Bug 1902179] Re: [20.04 FEAT] Support/enhancement of NVMe IPL
Ok, so 'chreipl' is used by the subiquity installer to prepare for the
post-install reboot.
This means that a fix for chreipl is indeed to have proper NVMe support in
place, incl. installer.
There is now just a little bit of time pressure, since this is relevant for
install time, it should not only land in the Ubuntu archives, but also on the
ISO image, and 20.04.2 is coming very soon...
So I guess we would need it in the next couple of days to have a little chance
to pick it up for focal/20.04.2 - otherwise it might slip to the .3 release
(the install time support).
--
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
parameters".
* The entire set of commits/patches is only new for focal.
* The SRU for SRUing "s390/ipl: support NVMe IPL kernel parameters" to
groovy/20.10 was handled by a separate request.
_
SRU Justification: (groovy)
==
[Impact]
* The basics for being able to IPL (boot) from NVMe devices on s390x
were introduced with kernel 5.8.
* This was tested and is proven to work with groovy.
* Now a patch was requested to be added to groovy that introduces
support for NVMe IPL kernel parameters.
[Fix]
* d9f12e48d08ec08ace574050a838e001e442e
[Kernel-packages] [Bug 1911917] Re: Kernel general protection fault when using NFQUEUE iptables target
** Attachment removed: "iptables rules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911917/+attachment/5453517/+files/iptables.conf.nfq -- 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/1911917 Title: Kernel general protection fault when using NFQUEUE iptables target Status in linux package in Ubuntu: Confirmed Bug description: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds serio_raw video sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 r
[Kernel-packages] [Bug 1911917] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1911917 Title: Kernel general protection fault when using NFQUEUE iptables target Status in linux package in Ubuntu: Confirmed Bug description: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds serio_raw video sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul gha
[Kernel-packages] [Bug 1910995] Re: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build
download the package here: https://launchpad.net/ubuntu/+archive/primary/+files/bcmwl-kernel- source_6.30.223.271+bdcom-0ubuntu7_amd64.deb Open a Terminal (Ctrl+Alt+T) enter this on terminal: cd Downloads/ sudo dpkg -i bcmwl-kernel-source_6.30.223.271+bdcom-0ubuntu7_amd64.deb that's all:) -- 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/1910995 Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Confirmed Bug description: after update the packages and reboot my computer, the wifi do not work any more. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-36.40~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-34-generic Date: Thu Jan 7 06:11:05 2021 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.271+bdcom-0ubuntu5:/var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/src/shared/linux_osl.c:949:10: error: implicit declaration of function ‘ioremap_nocache’; did you mean ‘ioremap_cache’? [-Werror=implicit-function-declaration] InstallationDate: Installed on 2020-09-18 (114 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageVersion: 6.30.223.271+bdcom-0ubuntu5 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.2 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu5: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1910995/+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 1911917] Re: Kernel general protection fault when using NFQUEUE iptables target
** Attachment added: "iptables rules" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911917/+attachment/5453517/+files/iptables.conf.nfq -- 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/1911917 Title: Kernel general protection fault when using NFQUEUE iptables target Status in linux package in Ubuntu: New Bug description: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds serio_raw video sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 mu
[Kernel-packages] [Bug 1911917] Re: Kernel general protection fault when using NFQUEUE iptables target
** Attachment added: "KernelCrash file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1911917/+attachment/5453516/+files/linux-image-5.4.0-62-generic-202101151448.crash -- 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/1911917 Title: Kernel general protection fault when using NFQUEUE iptables target Status in linux package in Ubuntu: New Bug description: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: G W 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds serio_raw video sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor ra
[Kernel-packages] [Bug 1911917] [NEW] Kernel general protection fault when using NFQUEUE iptables target
Public bug reported: When a packet is forwarded through an Ubuntu Focal host with kernel version 5.4.0-62-generic and NFQUEUE target is used in mangle PREROUTING and POSTROUTING, the kernel crashes. [ 856.055991] general protection fault: [#1] SMP PTI [ 856.151292] CPU: 0 PID: 722 Comm: nfq-cpp Kdump: loaded Tainted: GW 5.4.0-62-generic #70-Ubuntu [ 856.152503] Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 [ 856.153448] RIP: 0010:validate_xmit_skb_list+0x34/0x70 [ 856.154058] Code: 57 41 56 41 55 41 54 53 48 85 ff 74 45 49 89 ff 49 89 f4 49 89 d5 45 31 f6 eb 0c 48 89 03 48 8b 58 08 4d 85 ff 74 2e 4c 89 ff <4d> 8b 3f 4c 89 ea 4c 89 e6 48 c7 07 00 00 00 00 48 89 7f 08 e8 73 [ 856.156228] RSP: 0018:a061404776d8 EFLAGS: 00010286 [ 856.156868] RAX: 8d1c2fa6d900 RBX: 8d1c2fa6d900 RCX: 9f32fd20 [ 856.157715] RDX: a0614047771b RSI: 00800013ca29 RDI: dead0100 [ 856.361073] RBP: a06140477700 R08: 8d1c2fd6a8ac R09: 0001 [ 856.543925] R10: 8d1c30373870 R11: a061404779f8 R12: 8d1c29afb000 [ 856.544761] R13: a0614047771b R14: 8d1c2fa6d900 R15: dead0100 [ 856.545586] FS: 7fd887366740() GS:8d1c3fc0() knlGS: [ 856.546514] CS: 0010 DS: ES: CR0: 80050033 [ 856.547206] CR2: 7ffcbb2be8d8 CR3: 6cace001 CR4: 000606f0 [ 856.548029] Call Trace: [ 856.548349] sch_direct_xmit+0x150/0x340 [ 856.548824] __dev_queue_xmit+0x57b/0x8e0 [ 856.549353] dev_queue_xmit+0x10/0x20 [ 856.549841] neigh_resolve_output+0x110/0x1c0 [ 856.550426] ip_finish_output2+0x19b/0x590 [ 856.550990] ? nf_ct_del_from_dying_or_unconfirmed_list+0x34/0x70 [nf_conntrack] [ 856.551929] __ip_finish_output+0xbf/0x1e0 [ 856.552464] ip_finish_output+0x2d/0xb0 [ 856.552972] nf_reinject+0x12e/0x200 [ 856.553452] nfqnl_reinject+0x52/0x60 [nfnetlink_queue] [ 856.554110] nfqnl_recv_verdict+0x289/0x4b0 [nfnetlink_queue] [ 856.554826] ? __nla_validate_parse+0x116/0x140 [ 856.555409] nfnetlink_rcv_msg+0x172/0x2a0 [nfnetlink] [ 856.556062] ? __switch_to_asm+0x40/0x70 [ 856.556579] ? __switch_to_asm+0x34/0x70 [ 856.681025] ? __switch_to_asm+0x40/0x70 [ 856.811662] ? __switch_to_asm+0x34/0x70 [ 856.812216] ? __switch_to_asm+0x40/0x70 [ 856.812770] ? __switch_to_asm+0x34/0x70 [ 856.813324] ? __switch_to_asm+0x40/0x70 [ 856.813879] ? __switch_to_asm+0x34/0x70 [ 856.814434] ? __switch_to_asm+0x40/0x70 [ 856.815009] ? __switch_to_asm+0x34/0x70 [ 856.815567] ? nfnetlink_net_exit_batch+0x70/0x70 [nfnetlink] [ 856.816327] netlink_rcv_skb+0x50/0x120 [ 856.816859] nfnetlink_rcv+0x6c/0x14b [nfnetlink] [ 856.817463] netlink_unicast+0x187/0x220 [ 856.817982] netlink_sendmsg+0x222/0x3e0 [ 856.818502] sock_sendmsg+0x65/0x70 [ 856.818973] sys_sendmsg+0x212/0x280 [ 856.819491] ___sys_sendmsg+0x88/0xd0 [ 856.820020] ? sock_recvmsg+0x70/0x80 [ 856.831151] ? __sys_recvfrom+0x19e/0x1d0 [ 856.831715] __sys_sendmsg+0x5c/0xa0 [ 856.832197] __x64_sys_sendmsg+0x1f/0x30 [ 856.832716] do_syscall_64+0x57/0x190 [ 856.833207] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 856.833848] RIP: 0033:0x7fd8875e7747 [ 856.834331] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 856.836582] RSP: 002b:7ffcbb2be708 EFLAGS: 0246 ORIG_RAX: 002e [ 856.837563] RAX: ffda RBX: 7ffcbb2be7b0 RCX: 7fd8875e7747 [ 856.838452] RDX: RSI: 7ffcbb2be720 RDI: 0003 [ 856.839319] RBP: R08: 0020 R09: 0301 [ 856.840276] R10: R11: 0246 R12: [ 856.841177] R13: 5ca98538 R14: R15: [ 856.842044] Modules linked in: xt_NFQUEUE xt_state xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xt_tcpudp iptable_mangle bpfilter nfnetlink_queue nfnetlink binfmt_misc nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua input_leds serio_raw video sch_fq_codel drm ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel crypto_simd cryptd glue_helper ahci psmouse libahci virtio_net net_failover failover ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-62-generic 5.4.0-62.70 ProcVersionSignature: Ubuntu 5.4.0-62.70-generic 5.4.78 Uname: Linux 5.4.0-62-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 15 14:52 seq crw-rw 1 root audio 116, 33 Jan 15 14:52 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0u
[Kernel-packages] [Bug 1902179] Comment bridged from LTC Bugzilla
--- Comment From jjhe...@us.ibm.com 2021-01-15 08:35 EDT---
(In reply to comment #82)
> Is the NVMe drive with or without nvme-multipath support?
> Does it help to disable multipath?
>
> Please see the below pullrequest from Canonical employee in efivar project
> that explains the issue a bit, and the various paths that the NVMe devices
> can have.
>
> https://github.com/rhboot/efivar/pull/158
>
> This also affected efibootmgr project for the EFI platforms with newer
> kernels, as shipped in focal.
>
> You can also try booting with the following kernel cmdline option appended
> in the param file i.e. `nvme_core.multipath=N` to get the "non-multipath
> nvme0 nodes in the sysfs".
>
> BTW
> https://www.ibm.com/support/knowledgecenter/STSLR9_8.3.1/com.ibm.fs9100_831.
> doc/svc_fc_nvme_multipathconfighosts.html has an excellent summary of nvme
> multipath situation in various distros.
Yes, multipath is the problem here. When multipath is enabled we have a
different sysfs structure. I'll have to work up a fix.
Can you move ahead with the code as it is, and then we can provide a bug
fix patch when ready? This chreipl bug should not impede NVMe
installation or a normal boot process.
--
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/1902179
Title:
[20.04 FEAT] Support/enhancement of NVMe IPL
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Fix Released
Status in s390-tools package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in s390-tools source package in Focal:
New
Status in linux source package in Groovy:
Fix Released
Status in s390-tools source package in Groovy:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in s390-tools source package in Hirsute:
Fix Released
Bug description:
SRU Justification: (focal)
==
[Impact]
* The base for being able to IPL (boot) NVMe devices on s390x was
introduced with kernel 5.8.
* This got now requested (for hardware enablement reasons) for Ubuntu
20.04 LTS as well.
* On top a brand new commit got upstream accepted that introduces
support for NVMe IPL kernel parameters, which is not yet in groovy.
[Fix]
* cherry pick of commit 3737e8ee4f2fc7e77994d1a8bd618a9dda5a5514
3737e8ee4f2f "s390: nvme ipl"
* cherry pick of commit 23a457b8d57dc8d0cc1dbd1882993dd2fcc4b0c0 23a457b8d57d
"s390: nvme reipl"
does not apply cleanly, hence the following backport:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1902179/+attachment/5430310/+files/0002-s390-nvme-reipl.patch
* cherry pick of commit d9f12e48d08ec08ace574050a838e001e442ee38
d9f12e48d08e "s390/ipl: support NVMe IPL kernel parameters"
[Test Case]
* IBM z15 or LinuxONE III hardware is needed with an NVMe device
attached to a LPAR.
* Install the patched kernel on focal/20.04 installation and make sure
that zipl re-ran (the patched version of zipl with the s390-tools
commit mentioned in this LP bug - or take the s390-tools version for
groovy for testing purposes).
* If everything is in place (means patched kernel, as well as patched
s390-tools/zipl) an installation from scratch on an NVMe devices should be
possible - in case everything needed landed on an updated image.
With the 20.04.2 image that should be the case.
[Regression Potential]
* There is a certain regression risk with these patches, because:
* the 'zipl' (s390x-specific) boot-loader is touched
* if something is wrong there, in worst-case systems where the
modified zipl ran may no longer be bootable!
* The modifications are targetted towards nvme devices ('blkext'
driver), but they are closely related to zFCP devices and share some
code parts,
* hence in worst case they could have an impact on zFCP devices, too.
* But this is very unlikely, since a (largely) separate IPL type
'nvme' got introduced and NVMe ipl is handled in separate case
statements and functions.
* The patches are all upstream accepted (the first two with 5.8, that
last with v5.10-rc1, hence the latter one is as of today in linux-
next).
* A patched focal kernel was build and shared for further testing. I
did some regression testing with the patched kernel on non-NVMe
systems - the NVMe based tests need to be done by IBM (due to the lack
of hardware).
* All modifications are limited to the s390x architecture and there
again to the unique way of booting aka IPL
(arch/s390/include/asm/ipl.h, arch/s390/include/uapi/asm/ipl.h,
arch/s390/kernel/ipl.c and arch/s390/boot/ipl_parm.c).
[Other]
* The general NVMe ipl (boot) functionality in given with 3737e8ee4f2f
"s390: nvme ipl" and 23a457b8d57d "s390: nvme reipl" and is already
proven to work with groovy.
* New for groovy AND focal is only "s390/ipl: support NVMe IPL kernel
[Kernel-packages] [Bug 1907962] Re: The touchpad doesn't work and sometimes keyboard
Hi, I found the solution for the touchpad - it is written on this webpage: https://www.bw-pc.uni-freiburg.de/linux. => sudo nano / etc / modules => Insert the line: i2c_hid => Quit "nano" with CTRL + o and CTRL + x => reboot However, the question with the keyboard is still open. Sometimes it does not work. The only thing that help is to put the computer in to the sleep mode or restart. But it happens very rarely. -- 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/1907962 Title: The touchpad doesn't work and sometimes keyboard Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Ubuntu 5.4.0-58.64-generic 5.4.73 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oleksandr 1379 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Dec 13 14:13:00 2020 InstallationDate: Installed on 2020-12-11 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK U7410 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=be9b4d42-06a6-492c-a49c-b1f88b6c58c6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/23/2020 dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.bios.version: Version 2.12 dmi.board.name: FJNB2D4 dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.board.version: A2 dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED dmi.chassis.version: LIFEBOOK U7410 dmi.modalias: dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.12:bd06/23/2020:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKU7410:pvr10601115935:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2D4:rvrA2:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKU7410: dmi.product.family: LIFEBOOK-FTS dmi.product.name: LIFEBOOK U7410 dmi.product.sku: SK00 dmi.product.version: 10601115935 dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1907962/+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 1908264] Re: Disable Atari partition support for cloud kernels
I submitted a v2 for the Azure kernels: https://lists.ubuntu.com/archives/kernel-team/2021-January/116454.html https://lists.ubuntu.com/archives/kernel-team/2021-January/116455.html https://lists.ubuntu.com/archives/kernel-team/2021-January/116456.html https://lists.ubuntu.com/archives/kernel-team/2021-January/116457.html -- 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/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Invalid Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Committed Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: In Progress Status in linux-aws source package in Focal: Fix Committed Status in linux-azure source package in Focal: In Progress Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: In Progress Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Invalid Status in linux-azure-4.15 source package in Hirsute: Invalid Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+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 1910576] Re: [MIR] libbpf (dependency of iproute2)
laney@dev> ./change-override -S -c main -s hirsute libbpf Override component to main libbpf 0.3-2 in hirsute: universe/misc -> main libbpf-dev 1:0.3-2 in hirsute amd64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute arm64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute armhf: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute ppc64el: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute riscv64: universe/libdevel/optional/100% -> main libbpf-dev 1:0.3-2 in hirsute s390x: universe/libdevel/optional/100% -> main libbpf0 1:0.3-2 in hirsute amd64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute arm64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute armhf: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute ppc64el: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute riscv64: universe/libs/optional/100% -> main libbpf0 1:0.3-2 in hirsute s390x: universe/libs/optional/100% -> main Override [y|N]? y 13 publications overridden. ** Changed in: libbpf (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1910576 Title: [MIR] libbpf (dependency of iproute2) Status in iproute2 package in Ubuntu: Invalid Status in libbpf package in Ubuntu: Fix Released Bug description: [Availability] libbpf | 0.1.0-1 | groovy/universe | source libbpf | 0.3-2 | hirsute/universe | source [Rationale] Libbpf is (or is about to become) a dependency for building iproute2 which already is in main. Using BPF is becoming more wide-spread. The library allows to load and use eBPF programs from user-space (functionality provided by the kernel). It is already maintained in main for Debian (https://tracker.debian.org/pkg/libbpf) [Security] Since the code is taken out of the Linux kernel, this should be treated similar to the kernel for security. Research uncovered no records about security issues. [Quality assurance] At this point there are no open bug reports against libbpf (except this one) in Ubuntu. Also no open bugs found in Debian. Project is taken from the kernel source and claims static analysis via LGTM and Coverty. Also has CI via Travis (https://travis-ci.com/github/libbpf/libbpf). Right now there are no dep-8 tests. Though potentially it should be possible to create those, would this really add additional benefit beyond having upstream CI? A test build on hirsute was showing no warnings beyond lintian complaining about things which would be changed if we had delta (unstable as series for example). Otherwise was clean. [Dependencies] libc6: main libelf1: main zlib1g: main [Standards compliance] $ lintian --pedantic libbpf_0.3-2.dsc P: libbpf source: no-homepage-field P: libbpf source: silent-on-rules-requiring-root [Maintenance] As this is only taking out code from the kernel into a separate library package, the maintenance effort should be minimal. Packaging is done in Debian and is synced into Ubuntu (no delta). [Background information] A discourse about why this is packaged outside the kernel can be found at https://lwn.net/Articles/836911/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1910576/+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 1909005] Re: Ubuntu does not resume (wake up) from suspend
Today I booted with 5.4.0-62-generic kernel and the behavior changed a bit. With this kernel when I resume from suspend screen lights up and I am back at login. However I cannot enter password or login and I get an "authentication. error" while password textbox vibrates constantly. I have attached a picture. ** Attachment added: "Picture of broken login screen" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+attachment/5453468/+files/1ncX3Yadf-CstpjLvKD7mjUqicmFuebj6 -- 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/1909005 Title: Ubuntu does not resume (wake up) from suspend Status in linux package in Ubuntu: Incomplete Bug description: Whenever Ubuntu gets into suspend state, I cannot wake it up. -Keystrokes start the fans but screen does not turn on and Ubuntu still seems to be suspended because in my teamviewer account the computer is still offline. -Power button clicks do not help -I always have to turn off computer by holding power button and then turn it on again. The only kernel that works is the following: "linux-image-5.0.0-1070 -oem-osp1". But with this old kernel I run into different problems. I have the latest BIOS version from Dell (released 2020-11-27) and the latest updates in Ubuntu 20.04. I will post logs during suspend and important logs (found in Logs gui tool) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-58-generic 5.4.0-58.64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 Uname: Linux 5.4.0-58-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: philip 2340 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Dec 22 13:59:14 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X18 InstallationDate: Installed on 2019-12-04 (383 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 0cf3:e009 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3593 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic root=UUID=26003f0f-3564-472f-984c-a9a00e480fd0 ro mem_sleep_default=deep tsc=reliable quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-58-generic N/A linux-backports-modules-5.4.0-58-generic N/A linux-firmware1.187.6 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-11-04 (47 days ago) dmi.bios.date: 11/13/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 04N9HV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/13/2020:svnDellInc.:pnInspiron3593:pvr:rvnDellInc.:rn04N9HV:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3593 dmi.product.sku: 0979 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909005/+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 1861294] Re: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu
This affect me many times, I'm using Acer Swift-3 laptop with Intel UHD graphics. Jan 15 17:37:22 KY-PC kernel: GpuWatchdog[82704]: segfault at 0 ip 55c640e6f7a9 sp 7f1f32e4c4e0 error 6 in Typora[55c63d51f000+5cbc000] Jan 15 17:37:22 KY-PC kernel: Code: 00 79 09 48 8b 7d c0 e8 d5 f6 bd fe c7 45 c0 aa aa aa aa 0f ae f0 41 8b 84 24 e0 00 00 00 89 45 c0 48 8d 7d c0 e8 67 5c 6b fc 04 25 00 00 00 00 37 13 00 00 48 83 c4 38 5b 41 5c 41 5d 41 5e Jan 15 17:37:22 KY-PC kernel: audit: type=1701 audit(1610703442.770:463): auid=1000 uid=1000 gid=1000 ses=2 pid=82684 comm="GpuWatchdog" exe="/usr/share/typora/Typora" sig=11 res=1 Jan 15 17:37:22 KY-PC audit[82684]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=82684 comm="GpuWatchdog" exe="/usr/share/typora/Typora" sig=11 res=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/1861294 Title: Gpu watchdog segfault and video+kbd+mouse freeze on optiplex 7060 intel gpu Status in linux package in Ubuntu: Incomplete Bug description: Running up-to-date Ubuntu-18.04.3 with kernel 5.3.0-26 on a Dell Optiplex 7060 with an i7-8700 CPU and Intel UHD Graphics 630 (Coffeelake 3x8 GT2). I had chrome, slack and vmware-player running in Gnome. While doing some git clone, screen+mouse+keyboard froze for 2 minutes after which xorg and everything else recovered. I saw this in dmesg: kernel: show_signal_msg: 2 callbacks suppressed kernel: GpuWatchdog[20399]: segfault at 0 ip 556fd1665ded sp 7efbf17e46c0 error 6 in chrome[556fcd72a000+7171000] kernel: Code: 48 c1 c9 03 48 81 f9 af 00 00 00 0f 87 c9 00 00 00 48 8d 15 a9 5a 9c fb f6 04 11 20 0f 84 b8 00 00 00 be 01 00 00 00 ff 50 30 04 25 00 00 00 00 37 13 00 00 c6 05 c1 6d kernel: nvme nvme0: I/O 202 QID 6 timeout, aborting kernel: nvme nvme0: I/O 203 QID 6 timeout, aborting kernel: nvme nvme0: I/O 204 QID 6 timeout, aborting kernel: nvme nvme0: I/O 205 QID 6 timeout, aborting kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: Abort status: 0x0 kernel: nvme nvme0: I/O 202 QID 6 timeout, reset controller kernel: nvme nvme0: 12/0/0 default/read/poll queues While writing this bug report, the system froze again, and this time it didn't recover. After a cold reset I didn't see any other GpuWatchdog messages in journalctl. Ubuntu applied a BIOS firmware update before the first freeze, so my BIOS was updated as part of the cold reset I did. Not sure if this is relevant to reproducing the freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861294/+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 1904590] Re: Virtualbox does not work on 20.04-edge kernel due to DKMS build failure
*** This bug is a duplicate of bug 1901904 ***
https://bugs.launchpad.net/bugs/1901904
** This bug is no longer a duplicate of bug 1891916
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1 fails to build with kernel 5.8
** This bug has been marked a duplicate of bug 1901904
[SRU] virtualbox 6.1.10-dfsg-1~ubuntu1.20.04.1 ADT test failure with
linux-hwe-5.8 5.8.0-25.26~20.04.1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dkms in Ubuntu.
https://bugs.launchpad.net/bugs/1904590
Title:
Virtualbox does not work on 20.04-edge kernel due to DKMS build
failure
Status in dkms package in Ubuntu:
Confirmed
Status in virtualbox package in Ubuntu:
Confirmed
Bug description:
Building DKMS kernel modules for Virtualbox for kernel 5.8 (Ubuntu
kernel linux-image-generic-hwe-20.04-edge) fails and subsequently
Virtualbox does not work.
Ubuntu release:
~$ lsb_release -rd
Description: Ubuntu 20.04.1 LTS
Release: 20.04
Relevant Virtualbox packages/versions:
virtualbox6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-dkms 6.1.10-dfsg-1~ubuntu1.20.04.1
virtualbox-guest-additions-iso6.1.10-1~ubuntu1.20.04.1
virtualbox-qt 6.1.10-dfsg-1~ubuntu1.20.04.1
Kernel packages:
~$ dpkg-query -f '${Package} ${Status}\n' -W "linux-image*" | awk '$NF ==
"installed"{print $1}'
linux-image-5.4.0-54-generic
linux-image-5.8.0-28-generic
linux-image-5.8.0-29-generic
linux-image-generic
linux-image-generic-hwe-20.04-edge
Kernel:
~$ uname -r
5.8.0-29-generic
I get an error when building DKMS for Virtualbox for kernel 5.8:
~$ sudo /usr/lib/dkms/dkms_autoinstaller start 5.8.0-29-generic
* dkms: running auto installation service for kernel 5.8.0-29-generic
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning build area...
make -j8 KERNELRELEASE=5.8.0-29-generic -C
/lib/modules/5.8.0-29-generic/build
M=/var/lib/dkms/virtualbox/6.1.10/build...(bad exit status: 2)
Error! Bad return status for module build on kernel: 5.8.0-29-generic (x86_64)
Consult /var/lib/dkms/virtualbox/6.1.10/build/make.log for more information.
Build log file:
~$ cat /var/lib/dkms/virtualbox/6.1.10/build/make.log
DKMS make.log for virtualbox-6.1.10 for kernel 5.8.0-29-generic (x86_64)
di 17 nov 2020 16:30:39 CET
make: Entering directory '/usr/src/linux-headers-5.8.0-29-generic'
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M]
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
In file included from ./include/asm-generic/percpu.h:7,
from ./arch/x86/include/asm/percpu.h:556,
from ./arch/x86/include/asm/preempt.h:6,
from ./include/linux/preempt.h:78,
from ./include/linux/spinlock.h:51,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/../SUPDrvInternal.h:79,
from
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:32:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c: In
function ‘supdrvOSChangeCR4’:
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
error: ‘cpu_tlbstate’ undeclared (first use in this function); did you mean
‘cpuhp_state’?
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs.h:318:9: note: in definition of macro
‘__pcpu_size_call_return’
318 | typeof(variable) pscr_ret__; \
| ^~~~
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:24:
note: in expansion of macro ‘this_cpu_read’
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
|^
/var/lib/dkms/virtualbox/6.1.10/build/vboxdrv/linux/SUPDrv-linux.c:760:38:
note: each undeclared identifier is reported only once for each function it
appears in
760 | RTCCUINTREG uOld = this_cpu_read(cpu_tlbstate.cr4);
| ^~~~
./include/linux/percpu-defs
[Kernel-packages] [Bug 1910291] Re: update ENA driver, incl. new ethtool stats
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Groovy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Bionic)
Importance: Undecided => Medium
--
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/1910291
Title:
update ENA driver, incl. new ethtool stats
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Focal:
In Progress
Status in linux source package in Groovy:
In Progress
Bug description:
Update Amazon ENA driver in {bionic,focal,groovy}-generic with latest
upstream commits from mainline applicable to each series, including
"net: ena: ethtool: Add new device statistics".
[Impact]
* Supplies ENA device stats requested by AWS.
* Supplies general bug fixes for the ENA driver.
[Test Case]
Use of any ENA-enabled instance is a basic regression test. The "new
ethtool stats" can be verified by observing additional entries listed
by ;ethtool -S'.
[Regression Potential]
Low: These commits are all mainline cherry-picks or trivial (file
rename) backports. Only the Amazon ENA driver is affected.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910291/+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 1910965] Re: riscv: backport support for SiFive Unmatched
** Changed in: linux (Ubuntu Groovy) Importance: Undecided => High ** Changed in: linux (Ubuntu Groovy) 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/1910965 Title: riscv: backport support for SiFive Unmatched Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: New Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: == SRU Justifcation Groovy/RISCV == The SiFive HiFive Unmatched board should be supported as well as the current Unleashed. There are various upstream commits for this support and some misc fixes for the Unleashed and Unmatched that are required for this board support. == The fix(es) == The following changes since commit 7295e646e91b648b7f45b4f36eba14bfe59dd3f6: UBUNTU: Ubuntu-riscv-5.8.0-13.15 (2020-12-15 10:33:23 +0100) are available in the Git repository at: https://git.launchpad.net/~colin-king/+git/ubuntu-riscv-groovy for you to fetch changes up to 86de0730500269fee8b71fcb1be29193455c3be7: UBUNTU: [Config] Align configs with Unleashed defconfigs (2021-01-11 09:37:13 +) Colin Ian King (1): UBUNTU: [Config] Align configs with Unleashed defconfigs David Abdurachmanov (5): PCI: microsemi: Add host driver for Microsemi PCIe controller Microsemi PCIe expansion board DT entry. HACK: Revert "of/device: Really only set bus DMA mask when appropriate" SiFive Unleashed CPUFreq SiFive HiFive Unleashed: Add PWM LEDs (D1, D2, D3, D4) Greentime Hu (2): irqchip/sifive-plic: Fix broken irq_set_affinity() callback irqchip/sifive-plic: Fix getting wrong chip_data when interrupt is hierarchy Pragnesh Patel (1): clk: sifive: Add clock enable and disable ops Rob Herring (2): dt-bindings: More whitespace clean-ups in schema files dt-bindings: Explicitly allow additional properties in board/SoC schemas Sagar Kadam (2): dt-bindings: riscv: sifive-l2-cache: convert bindings to json-schema dt-bindings: riscv: convert pwm bindings to json-schema Sagar Shrikant Kadam (1): i2c: ocores: fix polling mode workaround on FU540-C000 SoC Yash Shah (6): RISC-V: Update l2 cache DT documentation to add support for SiFive FU740 RISC-V: sifive_l2_cache: Update L2 cache driver to support SiFive FU740 dt-bindings: riscv: Update DT binding docs to support SiFive FU740 SoC riscv: dts: add initial support for the SiFive FU740-C000 SoC dt-bindings: riscv: Update YAML doc to support SiFive HiFive Unmatched board riscv: dts: add initial board data for the SiFive HiFive Unmatched Zong Li (5): clk: sifive: Extract prci core to common base clk: sifive: Use common name for prci configuration clk: sifive: Add a driver for the SiFive FU740 PRCI IP block clk: sifive: Fix the wrong bit field shift dt-bindings: fu740: prci: add YAML documentation for the FU740 PRCI Documentation/devicetree/bindings/clock/sifive/fu740-prci.yaml | 60 Documentation/devicetree/bindings/gpio/sifive,gpio.yaml| 4 +- Documentation/devicetree/bindings/i2c/i2c-ocores.txt | 6 +- Documentation/devicetree/bindings/pwm/pwm-sifive.txt | 33 --- Documentation/devicetree/bindings/pwm/pwm-sifive.yaml | 72 + Documentation/devicetree/bindings/riscv/cpus.yaml | 6 + Documentation/devicetree/bindings/riscv/sifive-l2-cache.txt| 51 Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 127 + Documentation/devicetree/bindings/riscv/sifive.yaml| 20 +- Documentation/devicetree/bindings/serial/sifive-serial.yaml| 4 +- Documentation/devicetree/bindings/spi/spi-sifive.yaml | 10 +- arch/riscv/Kconfig | 8 + arch/riscv/Kconfig.socs| 2 +- arch/riscv/boot/dts/sifive/Makefile| 3 +- arch/riscv/boot/dts/sifive/fu540-c000.dtsi | 5 + arch/riscv/boot/dts/sifive/fu740-c000.dtsi | 293 +++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00-microsemi.dts | 28 ++ arch/riscv/boot/dts/sifive/hifive-unleashed-a00.dts| 66 + arch/riscv/boot/dts/sifive/hifive-unmatched-a00.dts| 253 + arch/riscv/configs/defconfig | 5 + debian.riscv/config/annotations| 17 +- debian.riscv/config/config.common.ubuntu | 47 +-- drivers/cl
[Kernel-packages] [Bug 1909678] Re: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-screen
** Also affects: linux-raspi (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1909678 Title: Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login- screen Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Groovy: New Status in linux-raspi source package in Hirsute: New Bug description: It is the same bug already described here: https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and- mouse-on-raspberry-pi-4b-with-ubuntu-20-10 My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired). How I could reproduce the mentioned crash: - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes - After five minutes, screen will turn black - If you move the mouse then, screen will be back again but frozen (mouse/keyboard not working). - restarting gdm.service via ssh is possible: sudo systemctl restart gdm.service - restarting it via Alt+SysRq+k is possible, but login after that fails for some reason Workaround: In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false as described here: https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+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 1906370] Re: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option
The patch for the config change landed in hirsute's kernel: Ubuntu-5.10.0-12.13 and kernel 5.10.0.12.14 is in proposed, hence updating the status Fix Committed. ** Changed in: linux (Ubuntu) Status: In Progress => Fix Committed ** Changed in: ubuntu-z-systems 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/1906370 Title: [21.04 FEAT] Deactivate CONFIG_QETH_OSN kernel config option Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: OSN devices' final shipment was as part of the IBM z13 release. The primary exploiter was the IBM Communication Controller, which was pulled out of marketing in March 2015 and should be out of service now. Therefore, we pull the support from all Linux distros going forward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1906370/+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
