[Kernel-packages] [Bug 1945553] Re: It hangs while booting up with AMD W6800 [1002:73A3]
** No longer affects: linux-oem-5.14 (Ubuntu) ** No longer affects: linux-oem-5.10 (Ubuntu) ** No longer affects: linux-oem-5.14 (Ubuntu Focal) ** No longer affects: linux-oem-5.14 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.14 (Ubuntu Impish) ** No longer affects: linux-oem-5.10 (Ubuntu Focal) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) ** No longer affects: linux-oem-5.10 (Ubuntu Impish) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945553 Title: It hangs while booting up with AMD W6800 [1002:73A3] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [Impact] It hangs when booting up with AMD W6800 [1002:73A3] graphics card. [Fix] Bisect the kernel and found below fix from v5.15-rc1 mainline kernel 5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5) [Test] Verified the patch on a Dell workstation with AMD W6800 graphics card [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945553/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
Build the kernel with 3 patches backported, and the test looks good. https://kernel.ubuntu.com/~ikepanhc/lp1932117.2/ @Xinwei, Could you check internally if it is ok to backport these patches for Ubuntu 5.4 kernel? a13c97118749 crypto: hisilicon/sec2 - Add workqueue for SEC driver. 57ca81245f4d crypto: hisilicon - Use one workqueue per qm instead of per qp eaebf4c3b103 crypto: hisilicon - Unify hardware error init/uninit into QM ** Changed in: kunpeng920 Status: In Progress => Incomplete ** Changed in: kunpeng920/ubuntu-18.04-hwe Status: In Progress => Incomplete ** Changed in: kunpeng920/ubuntu-20.04 Status: In Progress => 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/1932117 Title: Lots of hisi_qm zombie task slow down system after stress test Status in kunpeng920: Incomplete Status in kunpeng920 ubuntu-18.04-hwe series: Incomplete Status in kunpeng920 ubuntu-20.04 series: Incomplete Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux source package in Hirsute: Invalid Status in linux source package in Impish: Invalid Bug description: [Impact] hisi_qm does not clean up kernel process after calculation is done. Many zombie processes slow down system. After checkbox cpu stress test, it takes more then 2min to ssh in. [Test Plan] 1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 2) ps aux | grep hisi_qm | wc -l Expected result is less then 100 [Regression Risk] hisi_qm only affects kunpeng920 platform. Minimal risk for other platform, and full regression test is needed on kunpeng920. === [Bug Description] With focal 5.4 kernel, crypto driver does not clean up its created process when calculation is done. Many zombie processes slow down system. e.g. Takes more then 10sec for ssh connection. [Steps to Reproduce] 1) Install Ubuntu 20.04 with GA (5.4) kernel 2) sudo apt install -y stress-ng 3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times --af-alg 0 4) ps aux | grep hisi_qm | wc -l [Actual Results] >10 [Expected Results] <100 [Reproducibility] 100% [Additional information] Can not reproduce with focal HWE (5.8) kernel. [Resolution] To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1945553] Re: It hangs while booting up with AMD W6800 [1002:73A3]
** Description changed: [Impact] + It hangs when booting up with AMD W6800 [1002:73A3] graphics card. [Fix] + Bisect the kernel and found below fix from v5.15-rc1 mainline kernel + 5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5) [Test] + Verified the patch on a Dell workstation with AMD W6800 graphics card [Where problems could occur] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1945553 Title: It hangs while booting up with AMD W6800 [1002:73A3] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] It hangs when booting up with AMD W6800 [1002:73A3] graphics card. [Fix] Bisect the kernel and found below fix from v5.15-rc1 mainline kernel 5810323ba692 drm/amd/pm: Fix a bug communicating with the SMU (v5) [Test] Verified the patch on a Dell workstation with AMD W6800 graphics card [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-aws/5.4.0.1058.61)
All autopkgtests for the newly accepted linux-meta-aws (5.4.0.1058.61) for focal have finished running. The following regressions have been reported in tests triggered by the package: backport-iwlwifi-dkms/8324-0ubuntu3~20.04.4 (arm64, amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-aws [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1945531] 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 1945531 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/1945531 Title: screen freezes at boot Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: On do-release-upgrade to Impish with the 5.13 kernel the boot messages stop scrolling at: fb0: switching to amdgpudrmfb from EFI VGA The system may be continuing to boot but the screen stops updating. The 5.11 and 5.12 kernels both boot correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945531/+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 1705799] Re: Ubuntu 17.04 for ARM64 Mate desktop moving windows lags behind the mouse
[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/1705799 Title: Ubuntu 17.04 for ARM64 Mate desktop moving windows lags behind the mouse Status in linux package in Ubuntu: Expired Bug description: 0 down vote favorite I run Ubuntu base 17.04(http://cdimage.ubuntu.com/ubuntu-base/releases/17.04/release/ubuntu-base-17.04-base-arm64.tar.gz) on Amlogic S912 and install Mate desktop,the kernel I use is 4.9.26. But when I move the window there is a big lag, the window can not follow my mouse. But I run Ubuntu 16.04 with the same kernel 4.9.26 on Amlogic S912, it works well. --- ApportVersion: 2.20.4-0ubuntu4.5 Architecture: arm64 CurrentDesktop: MATE DistroRelease: Ubuntu 17.04 Package: linux (not installed) Tags: zesty Uname: Linux 4.9.26 aarch64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1705799/+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 1945531] Re: screen freezes at boot
** Tags added: impish ** Also 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/1945531 Title: screen freezes at boot Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: On do-release-upgrade to Impish with the 5.13 kernel the boot messages stop scrolling at: fb0: switching to amdgpudrmfb from EFI VGA The system may be continuing to boot but the screen stops updating. The 5.11 and 5.12 kernels both boot correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1945531/+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 1852905] Re: nvidia-drivers-435 won't load on GeForce GTX 980M
[Expired for nvidia-graphics-drivers-435 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1852905 Title: nvidia-drivers-435 won't load on GeForce GTX 980M Status in nvidia-graphics-drivers-435 package in Ubuntu: Expired Bug description: Preamble I have an Entroware Athena with GeForce GTX 980M GPU. It was running 18.04, and then upgraded to 19.10 where it was running fine. I was on GNOME but due to another unrelated bug I switched to MATE. While away, I think some packages updated on it and when I tried using the machine it was slow, feeling like I was using a VESA driver (very slow framerate on the desktop). I thought it needed an nvidia driver update and reboot, however, I couldn't install the latest nvidia driver. It got into a situation where nvidia-drivers-435 wouldn't install because xserver-xorg-video-nvidia-435 and libnvidia-cfg1-435 were being held back. So I did: sudo apt install nvidia-driver-435 xserver-xorg-video-nvidia-435 libnvidia-cfg1-435 When I rebooted, it's still not using the nvidia binary driver. I also noted it doesn't seem to trigger dkms at all. Surely it needs to? (base) alan@mother:~$ sudo apt install nvidia-driver-435 xserver-xorg-video-nvidia-435 libnvidia-cfg1-435 --reinstall Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: augeas-lenses chromium-codecs-ffmpeg-extra g++-7 gcc-8-base:i386 guile-2.0-libs libarmadillo8 libaugeas0 libavcodec-extra57 libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55 libboost-program-options1.65.1 libcharls1 libcrystalhd3 libcue1 libdouble-conversion1 libenca0 libgeos-3.6.2 libgfortran4 libglew2.0 libgovirt-common libgovirt2 libiptcdata0 liblivemedia62 libllvm7 libllvm8 libllvm8:i386 liblvm2app2.2 liblvm2cmd2.02 libmysqlclient20 libnetcf1 libnfs11 libnvidia-common-390 libnvidia-common-430 libostree-1-1 libplacebo4 libpostproc54 libproj12 libprotobuf-lite10 libpython3.6-dev libstdc++-7-dev libswresample2 libswscale4 libtagc0 libtinfo5:i386 libupnp6 libwayland-client0:i386 libwayland-server0:i386 libwxgtk3.0-0v5 libx264-152 libx265-146 libzip4 net-tools python-idna python-oauth python-zope.interface python3.6-dev schroot-common xserver-xorg-input-all-hwe-18.04 xserver-xorg-input-libinput-hwe-18.04 xserver-xorg-input-wacom-hwe-18.04 xserver-xorg-legacy-hwe-18.04 xserver-xorg-video-intel-hwe-18.04 xserver-xorg-video-nouveau-hwe-18.04 xserver-xorg-video-radeon-hwe-18.04 xserver-xorg-video-vmware-hwe-18.04 Use 'sudo apt autoremove' to remove them. 0 to upgrade, 0 to newly install, 3 reinstalled, 0 to remove and 0 not to upgrade. Need to get 1,986 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 libnvidia-cfg1-435 amd64 435.21-0ubuntu2 [69.2 kB] Get:2 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 nvidia-driver-435 amd64 435.21-0ubuntu2 [413 kB] Get:3 http://gb.archive.ubuntu.com/ubuntu eoan/restricted amd64 xserver-xorg-video-nvidia-435 amd64 435.21-0ubuntu2 [1,504 kB] Fetched 1,986 kB in 0s (85.7 MB/s) (Reading database ... 306958 files and directories currently installed.) Preparing to unpack .../libnvidia-cfg1-435_435.21-0ubuntu2_amd64.deb ... Unpacking libnvidia-cfg1-435:amd64 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Preparing to unpack .../nvidia-driver-435_435.21-0ubuntu2_amd64.deb ... Unpacking nvidia-driver-435 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Preparing to unpack .../xserver-xorg-video-nvidia-435_435.21-0ubuntu2_amd64.deb ... Unpacking xserver-xorg-video-nvidia-435 (435.21-0ubuntu2) over (435.21-0ubuntu2) ... Setting up libnvidia-cfg1-435:amd64 (435.21-0ubuntu2) ... Setting up xserver-xorg-video-nvidia-435 (435.21-0ubuntu2) ... Setting up nvidia-driver-435 (435.21-0ubuntu2) ... Processing triggers for libc-bin (2.30-0ubuntu2) ... (base) alan@mother:~$ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nvidia-driver-435 435.21-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: MATE Date: Sun Nov 17 12:00:29 2019 InstallationDate: Installed on 2019-06-19 (150 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: nvidia-graphics-drivers-435 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to:
[Kernel-packages] [Bug 1823819] Re: Upgrade to 19.04 fails with linux-image-5.0.0-8
[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/1823819 Title: Upgrade to 19.04 fails with linux-image-5.0.0-8 Status in linux package in Ubuntu: Expired Bug description: Upgrade to 19.04 Ubuntu MATE fails with following: Could not install 'linux-image-5.0.0-8-generic triggers looping, abandoned Could not install the upgrades The upgrade has aborted. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a). Same error as Bug #1823116 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-8-generic 5.0.0-8.9 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu25 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: testdev1634 F pulseaudio CurrentDesktop: MATE Date: Mon Apr 8 18:22:14 2019 InstallationDate: Installed on 2019-04-08 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. ens33 no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: VMware, Inc. VMware Virtual Platform ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-8-generic root=UUID=f20f596d-9e53-4bb6-bf4a-df5764d8ddb2 ro quiet splash RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-04-09 (0 days ago) dmi.bios.date: 04/13/2018 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823819/+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 1807838] Re: Ubuntu crashed totally. Nothing responded. Could not even shut down.
[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/1807838 Title: Ubuntu crashed totally. Nothing responded. Could not even shut down. Status in linux package in Ubuntu: Expired Bug description: I was running a bash script which copied directories from a partition on my hard drive (never store data in the Linux partition) to external USB drives. After the script finished, Ubuntu 18.10 crashed. The mouse pointer moved but no window, or menu or keys responded. Could not even get the Menu to open so that I could shut down. Had to power down manually. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3117 F pulseaudio /dev/snd/controlC0: robert 3117 F pulseaudio CurrentDesktop: MATE Date: Tue Dec 11 02:54:28 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807838/+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 1807605] Re: Could not report Linux error
[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/1807605 Title: Could not report Linux error Status in Ubuntu MATE: Invalid Status in linux package in Ubuntu: Expired Bug description: System tried to update and got an error due to the defective superspec package. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 3284 F pulseaudio /dev/snd/controlC0: robert 3284 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 9 12:41:11 2018 InstallationDate: Installed on 2018-11-30 (9 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=9bdf74d9-8608-440e-8020-66b698586d9d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1807605/+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 1379849] Re: [LENOVO 767374G] suspend/resume failure
[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/1379849 Title: [LENOVO 767374G] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: problem of standby ProblemType: KernelOops DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-21-generic 3.16.0-21.28 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gabriele 1753 F pulseaudio Date: Fri Oct 10 18:19:44 2014 DuplicateSignature: suspend/resume:LENOVO 767374G:7NETC2WW (2.22 ) ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume HibernationDevice: RESUME=UUID=4eb1ea2b-34e7-49d4-a952-8bcd4a2e6266 InstallationDate: Installed on 2014-09-19 (20 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - beta1 amd64 (20140828) InterpreterPath: /usr/bin/python3.4 MachineType: LENOVO 767374G ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-21-generic root=UUID=261f869f-bbc3-4a18-ad23-b90ad80e21de ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.16.0-21-generic N/A linux-backports-modules-3.16.0-21-generic N/A linux-firmware 1.135 SourcePackage: linux Title: [LENOVO 767374G] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 03/22/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC2WW (2.22 ) dmi.board.name: 767374G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETC2WW(2.22):bd03/22/2011:svnLENOVO:pn767374G:pvrThinkPadX61:rvnLENOVO:rn767374G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 767374G dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1379849/+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 1429761] Re: [ASUSTeK Computer Inc. 1225B] suspend/resume failure
[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/1429761 Title: [ASUSTeK Computer Inc. 1225B] suspend/resume failure Status in linux package in Ubuntu: Expired Bug description: OS : ubuntu MATE 15.4 Boot à partir d'un disque USb IOMEGA Logiciels installés : LibreOffice, Thunderbird, Firefox, GIMP, et Cairo Dock ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-7-generic 3.19.0-7.7 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic i686 Annotation: This occured during a previous suspend and prevented it from resuming properly. ApportVersion: 2.16.2-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robiquet 1589 F pulseaudio /dev/snd/controlC0: robiquet 1589 F pulseaudio Date: Mon Mar 9 08:55:06 2015 ExecutablePath: /usr/share/apport/apportcheckresume Failure: suspend/resume InstallationDate: Installed on 2015-03-03 (5 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Alpha i386 (20150225) InterpreterPath: /usr/bin/python3.4 MachineType: ASUSTeK Computer Inc. 1225B ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-7-generic root=UUID=8e7aa24b-57c8-4263-992b-762736abd497 ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux Title: [ASUSTeK Computer Inc. 1225B] suspend/resume failure UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 02/20/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 205 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: 1225B dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 205 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.:bvr205:bd02/20/2012:svnASUSTeKComputerInc.:pn1225B:pvr1.0:rvnASUSTeKComputerInc.:rn1225B:rvr205:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: 1225B dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1429761/+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 1441387] Re: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:1:5087]
[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/1441387 Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:1:5087] Status in linux package in Ubuntu: Expired Bug description: screen saver locked up computer - forced to hard shutdown computer and turn back on. ProblemType: KernelOops DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-12-generic 3.19.0-12.12 ProcVersionSignature: Ubuntu 3.19.0-12.12-generic 3.19.3 Uname: Linux 3.19.0-12-generic x86_64 Annotation: Your system might become unstablenow and might need to be restarted. ApportVersion: 2.17-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: chris 1431 F pulseaudio /dev/snd/controlC0: chris 1431 F pulseaudio Date: Tue Apr 7 19:18:50 2015 Failure: oops HibernationDevice: RESUME=UUID=6b93044d-8184-4d0e-a59d-be6f05e7ec45 InstallationDate: Installed on 2015-03-28 (10 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Beta amd64 (20150326) IwConfig: eth0 no wireless extensions. eth1 no wireless extensions. lono wireless extensions. MachineType: Dell Inc. Inspiron 530 ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.19.0-12-generic root=UUID=96efd830-9fa8-4f21-bafa-b076290da0b2 ro rootflags=subvol=@ quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon 0.12+git20090217-3ubuntu8 RfKill: SourcePackage: linux Title: NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! [kworker/1:1:5087] UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/24/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.18 dmi.board.name: 0FM586 dmi.board.vendor: Dell Inc. dmi.chassis.type: 3 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: OEM dmi.modalias: dmi:bvnDellInc.:bvr1.0.18:bd02/24/2009:svnDellInc.:pnInspiron530:pvr:rvnDellInc.:rn0FM586:rvr:cvnDellInc.:ct3:cvrOEM: dmi.product.name: Inspiron 530 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1441387/+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 1494884] Re: package linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de sali
[Expired for linux-lts-utopic (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-lts-utopic (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1494884 Title: package linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 Status in linux-lts-utopic package in Ubuntu: Expired Bug description: I have no idea what is going on ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-48.64~14.04.1-generic 3.16.7-ckt15 Uname: Linux 3.16.0-48-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Fri Sep 11 12:31:35 2015 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 2 InstallationDate: Installed on 2015-05-21 (112 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) SourcePackage: linux-lts-utopic SystemImageInfo: Error: [Errno 2] No existe el archivo o el directorio: 'system-image-cli' Title: package linux-image-3.16.0-49-generic 3.16.0-49.65~14.04.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1494884/+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 1454651] Re: Ubuntu Mate with Window Manager Marco fails to properly resume from Suspend on DELL XPS13
[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/1454651 Title: Ubuntu Mate with Window Manager Marco fails to properly resume from Suspend on DELL XPS13 Status in linux package in Ubuntu: Expired Bug description: I have the DELL XPS13 laptop which came factory pre-installed with Ubuntu 14.04. I changed the desktop to Ubuntu Mate. This had the Window Manager "Marco (Simple desktop effects)" activated. Whenever I went into Suspend, the laptop did resume, but the desktop was not redrawn, no panels, no menus and submenus, no buttons. When I moved the mouse pointer over the places where I assumed the elements to be, some of them did show up, and were clickable. After a reboot, all was normal. WORKAROUND: System > Control Center > MATE Tweak > Windows > Window Manager from Marco to Compiz. --- ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ullix 2099 F pulseaudio /dev/snd/controlC0: ullix 2099 F pulseaudio CurrentDesktop: MATE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-trusty-amd64-20140620-0 DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b6c248b-36d3-4dcf-9e9e-427d50206af6 InstallationDate: Installed on 2015-04-24 (19 days ago) InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 20140620-04:25 MachineType: Dell Inc. XPS 13 9343 NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=fda802ca-9257-4fed-bb0d-9f4756dca419 ro pcie_aspm=force radeon.modeset=0 plymouth:debug drm.debug=0xe nouveau.modeset=0 video.use_native_backlight=1 quiet splash pcie_aspm=force radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 RelatedPackageVersions: linux-restricted-modules-3.13.0-52-generic N/A linux-backports-modules-3.13.0-52-generic N/A linux-firmware 1.127.11 Tags: trusty Uname: Linux 3.13.0-52-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner sudo tape video _MarkForUpload: True dmi.bios.date: 03/25/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 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/1454651/+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 1509529] Re: package linux-signed-image-3.19.0-31-generic 3.19.0-31.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
[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/1509529 Title: package linux-signed-image-3.19.0-31-generic 3.19.0-31.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 Status in linux package in Ubuntu: Expired Bug description: Se realiza la operacion en la aplicacion "Actualizacion de software" en Ubuntu Mate 15.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: linux-signed-image-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: amd64 Date: Fri Oct 23 15:08:39 2015 DuplicateSignature: package:linux-signed-image-3.19.0-31-generic:3.19.0-31.36:subprocess installed post-installation script returned error exit status 127 ErrorMessage: subprocess installed post-installation script returned error exit status 127 InstallationDate: Installed on 2015-10-22 (1 days ago) InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4.2 SourcePackage: linux-signed Title: package linux-signed-image-3.19.0-31-generic 3.19.0-31.36 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509529/+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 1509759] Re: Incorrect hierarchies under /sys/devices
[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/1509759 Title: Incorrect hierarchies under /sys/devices Status in linux package in Ubuntu: Expired Bug description: I have one device on bus no 1 and is figured wrong . /sys/devices/pci:00/:00:1c.0/:01:00.0/ On my opinion this must look like this: /sys/devices/pci:01/:01:00.0 .. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-31-generic 3.19.0-31.36 ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7 Uname: Linux 3.19.0-31-generic i686 ApportVersion: 2.17.2-0ubuntu1.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: asu1262 F...m pulseaudio CurrentDesktop: MATE Date: Sun Oct 25 08:31:35 2015 HibernationDevice: RESUME=/dev/mapper/192--168--0--102--vg-swap_1 IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Olidata S.p.A. ALABAMA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-31-generic root=/dev/mapper/192--168--0--102--vg-root ro splash quiet vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.19.0-31-generic N/A linux-backports-modules-3.19.0-31-generic N/A linux-firmware 1.143.3 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/08/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S0101 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS0101:bd07/08/2008:svnOlidataS.p.A.:pnALABAMA:pvrToBeFilledByO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: ALABAMA dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: Olidata S.p.A. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1509759/+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 1518503] Re: package linux-headers-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: package linux-headers-3.16.0-51-generic is not ready for configuration canno
[Expired for linux-lts-utopic (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux-lts-utopic (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lts-utopic in Ubuntu. https://bugs.launchpad.net/bugs/1518503 Title: package linux-headers-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: package linux-headers-3.16.0-51-generic is not ready for configuration cannot configure (current status `half-installed') Status in linux-lts-utopic package in Ubuntu: Expired Bug description: maybe I did a wrong cmd when I tried to clean the system, because after that this problem appears. Ubuntu mate 14 04 ProblemType: Package DistroRelease: Ubuntu 14.04 Package: linux-headers-3.16.0-51-generic 3.16.0-51.69~14.04.1 ProcVersionSignature: Ubuntu 3.16.0-53.72~14.04.1-generic 3.16.7-ckt18 Uname: Linux 3.16.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Fri Nov 20 14:02:13 2015 DuplicateSignature: package:linux-headers-3.16.0-51-generic:3.16.0-51.69~14.04.1:package linux-headers-3.16.0-51-generic is not ready for configuration cannot configure (current status `half-installed') ErrorMessage: package linux-headers-3.16.0-51-generic is not ready for configuration cannot configure (current status `half-installed') InstallationDate: Installed on 2015-04-02 (231 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS amd64 (20150323) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: linux-lts-utopic Title: package linux-headers-3.16.0-51-generic 3.16.0-51.69~14.04.1 failed to install/upgrade: package linux-headers-3.16.0-51-generic is not ready for configuration cannot configure (current status `half-installed') UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lts-utopic/+bug/1518503/+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 1594974] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build
[Expired for bcmwl (Ubuntu) because there has been no activity for 60 days.] ** Changed in: bcmwl (Ubuntu) Status: Incomplete => Expired -- 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/1594974 Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: bcmwl kernel module failed to build Status in bcmwl package in Ubuntu: Expired Bug description: just happened...no idea why ProblemType: Package DistroRelease: Ubuntu 14.04 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2 ProcVersionSignature: Ubuntu 3.13.0-89.136-generic 3.13.11-ckt39 Uname: Linux 3.13.0-89-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 DKMSKernelVersion: 4.4.0-26-generic Date: Tue Jun 21 23:28:52 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu0.2:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/shared/linux_osl.c:935:2: error: implicit declaration of function ‘rdtscl’ [-Werror=implicit-function-declaration] InstallationDate: Installed on 2015-10-16 (249 days ago) InstallationMedia: Ubuntu MATE 14.04.2 "Trusty Tahr" - LTS i386 (20150323) PackageVersion: 6.30.223.248+bdcom-0ubuntu0.2 RelatedPackageVersions: dpkg 1.17.5ubuntu5.7 apt 1.0.1ubuntu2.14 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu0.2: 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/1594974/+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 1592813] Re: System freezes if memory is full
[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/1592813 Title: System freezes if memory is full Status in linux package in Ubuntu: Expired Bug description: If one or more process becames near of using 100% of system ram memory, Ubuntu will completely freeze. It is not possible even to switch to a VT to try to kill one or more procs. First I tought it could be some problem with swap and I tried to disable my swap partition, but didn't make a difference. Before using Ubuntu 14.04 64bit, I was using 8.04 32bits and this problem never happende with it. If the memory was near 100%, new apps would crash when trying to malloc, but the system would still be rock solid allowing me to close running apps to free memory. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-46-generic 3.13.0-46.79 ProcVersionSignature: Ubuntu 3.13.0-46.79-generic 3.13.11-ckt15 Uname: Linux 3.13.0-46-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: renato 2391 F pulseaudio CurrentDesktop: MATE Date: Wed Jun 15 09:52:27 2016 HibernationDevice: RESUME=UUID=4f544f74-0b59-4895-959b-9a2e60ce4485 InstallationDate: Installed on 2015-03-10 (462 days ago) InstallationMedia: Ubuntu MATE 14.04.1 "Trusty Tahr" - final amd64 (2014) MachineType: ASUSTeK Computer Inc. M51Sn ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic root=UUID=818b643f-29ae-4599-8039-470975a54543 ro biosdevname=0 quiet splash RelatedPackageVersions: linux-restricted-modules-3.13.0-46-generic N/A linux-backports-modules-3.13.0-46-generic N/A linux-firmware 1.127.22 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M51Sn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr305:bd05/04/2008:svnASUSTeKComputerInc.:pnM51Sn:pvr1.0:rvnASUSTeKComputerInc.:rnM51Sn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M51Sn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592813/+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 1890211] Re: 5.8 kernel appears to break video in two groovy installs
[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/1890211 Title: 5.8 kernel appears to break video in two groovy installs Status in linux package in Ubuntu: Expired Bug description: Ran apt to update/upgrade in both of my groovy distros, Lubuntu & U-MATE 20.10 . . . on reboot not only was my grub list broken in both cases but seemingly the update to the new 5.8.0-12 kernel shows splash logo, but "logs" to a black screen. Display power light is "on" but screen is black. I repeated this several times in both systems . . . having to boot using SG2 to another distro to repair grub . . . then after I did that I got to grub list and went to "advanced options" and rolled back to the prior 5.4.0-42 kernel . . . and GUI is operational. I believe in TW I am running 5.7 kernel and that system has video. I have an Nvidia card and I'm using "nouveau" as my driver. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu43 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: non-space2 1665 F pulseaudio /dev/snd/controlC0: non-space2 1665 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Mon Aug 3 15:45:08 2020 InstallationDate: Installed on 2019-06-17 (413 days ago) InstallationMedia: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. enp9s0no wireless extensions. enp10s0 no wireless extensions. MachineType: Apple Inc. MacPro5,1 ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=17bcb813-d05e-4cc3-bcdf-16d283156780 ro quiet splash resume=UUID=f9ae531f-ec45-4a13-a75d-d3fd4cd80fe0 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.189 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to groovy on 2019-12-13 (234 days ago) dmi.bios.date: 07/30/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 138.0.0.0.0 dmi.board.asset.tag: 0 dmi.board.name: Mac-F221BEC8 dmi.board.vendor: Apple Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F221BEC8 dmi.modalias: dmi:bvnAppleInc.:bvr138.0.0.0.0:bd07/30/2018:svnAppleInc.:pnMacPro5,1:pvr0.0:rvnAppleInc.:rnMac-F221BEC8:rvr:cvnAppleInc.:ct7:cvrMac-F221BEC8: dmi.product.family: MacPro dmi.product.name: MacPro5,1 dmi.product.sku: System SKU# dmi.product.version: 0.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890211/+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 1903426] Re: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit s
[Expired for b43-fwcutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: b43-fwcutter (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to b43-fwcutter in Ubuntu. https://bugs.launchpad.net/bugs/1903426 Title: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 Status in b43-fwcutter package in Ubuntu: Expired Bug description: Upgrading system from Ubuntu MATE 20.04 to Ubuntu MATE 20.10 via Alt+F2 and then update-manager -c Updates begins but error shows with Could not install 'firmware-b43-installer' (Screenshot attached) Upgrade completes but shows error message "Upgrade could not be installed, system may be unusable" System shows that the firmware is installed: firmware-b43-installer/groovy,groovy,now 1:019-6 all [installed] firmware installer for the b43 driver ProblemType: Package DistroRelease: Ubuntu 20.10 Package: firmware-b43-installer 1:019-6 ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14 Uname: Linux 5.8.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Nov 7 17:22:21 2020 ErrorMessage: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2019-04-25 (562 days ago) InstallationMedia: Ubuntu-MATE 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: b43-fwcutter Title: package firmware-b43-installer 1:019-6 failed to install/upgrade: installed firmware-b43-installer package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to groovy on 2020-11-08 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/1903426/+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 1945556] [NEW] Fix missing HDMI audio on Intel RKL
Public bug reported: [Impact] HDMI audio is missing on Intel RKL. [Fix] Also use BIOS provided value for HDA link. [Test] HDMI audio is back after the fix gets applied. [Where problems could occur] Because this is a regression, this patch simply brings back the old behavior for RKL systems. There could be RKL systems get fixed by the offending commit, so this might break those hypothetical systems. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Low Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Won't Fix ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Low Status: Confirmed ** Affects: linux (Ubuntu Impish) Importance: Low Status: Confirmed ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1940911 sutton ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Won't Fix ** Changed in: linux (Ubuntu Impish) Status: New => Confirmed ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Low ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided => Low ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Tags added: oem-priority originate-from-1940911 sutton -- 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/1945556 Title: Fix missing HDMI audio on Intel RKL Status in HWE Next: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.13 source package in Focal: Confirmed Status in linux-oem-5.14 source package in Focal: Confirmed Status in linux source package in Impish: Confirmed Status in linux-oem-5.13 source package in Impish: Invalid Status in linux-oem-5.14 source package in Impish: Invalid Bug description: [Impact] HDMI audio is missing on Intel RKL. [Fix] Also use BIOS provided value for HDA link. [Test] HDMI audio is back after the fix gets applied. [Where problems could occur] Because this is a regression, this patch simply brings back the old behavior for RKL systems. There could be RKL systems get fixed by the offending commit, so this might break those hypothetical systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945556/+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 1943524] Re: [EHL] Intel ishtp VNIC driver
** Information type changed from Private to Public ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1943524 Title: [EHL] Intel ishtp VNIC driver Status in intel: New Status in linux-intel-5.13 package in Ubuntu: New Status in linux-intel-5.13 source package in Focal: New Bug description: Description The driver enables a virtual network interface for communicating with a dedicated low power chip over ISHTP Hardware: ElkhartLake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.13-yocto-210727T062416Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1943524/+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 1945553] [NEW] It hangs while booting up with AMD W6800 [1002:73A3]
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.13 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Hirsute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Hirsute) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Impish) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.10 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.13 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Impish) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1937250 somerville ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.13 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.14 (Ubuntu Impish) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu Hirsute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Impish) Status: New => In Progress ** Changed in: linux (Ubuntu Impish) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.10 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.13 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.13 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1937250 somerville -- 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/1945553 Title: It hangs while booting up with AMD W6800 [1002:73A3] Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux-oem-5.14 source package in Hirsute: Invalid Status in linux source package in Impish: In Progress Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13
[Kernel-packages] [Bug 1945548] Re: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board
** Also affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945548 Title: I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board Status in intel: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: New Bug description: [Summary] I225-IT Ethernet (8086:0d9f) does not work on AAEON's EHL Board [Steps to reproduce] 1. Install https://cdimage.ubuntu.com/focal/daily-preinstalled/20210929/ to the system 2. Boot to desktop 3. Check if all Ethernet get IP address [Expected result] All Ethernet Port should up and runing and get the IP address. [Actual result] I225-IT Ethernet (8086:0d9f) does not work and did not get IP address [Failure rate] 100% [Additional information] CID: 202109-29492 SKU: N/A system-manufacturer: AAEON system-product-name: UPN-EHL01 bios-version: UNEHAM0D CPU: Intel Atom(R) x6425RE Processor @ 1.90GHz (4x) GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:4571] (rev 01) kernel-version: 5.13.0-1004-intel [Stage] Issue reported and logs collected right after it happened To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1945548/+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 1699772]
Very informative post. Thanks for sharing it. https://www.rubbishremovalgeelong.com.au/;>rubbish removal Geelong -- 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/1699772 Title: linux-image-4.13.0-12-generic, linux-image-4.10.0-24-generic, linux- image-4.8.0-56-generic, linux-image-4.4.0-81-generic, linux- image-3.13.0-121-generic | Regression: many user-space apps crashing Status in LibreOffice: Won't Fix Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Status in linux source package in Artful: Won't Fix Status in linux source package in Bionic: Fix Released Status in linux package in Debian: Fix Released Bug description: Distribution: Ubuntu 16.04 x64 (Flavour: KDE Neon User Edition 5.10) linux-image-4.4.0-81-generic appears to contain a regression, probably related to the CVE-2017-1000364 fix backport / patch. Using this kernel, the Oracle Java browser plugin always crashes during stack-related actions on initialization. This means, the plugin completely stopped working. It works perfectly fine in linux-image-4.4.0-79-generic (vurlerable to CVE-2017-1000364) as well as linux-image-4.11.6-041106-generic, which also contains a fix for CVE-2017-1000364. uname -a: > Linux Zweiblum 4.4.0-81-generic #104-Ubuntu SMP Wed Jun 14 08:17:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux I tested Oracle Java 1.8 u131 as well as 1.6 u64 in Firefox 51.0.1 as well as Iceweasel / Firefox/3.5.16 in a chroot. Using linux-image-4.4.0-81-generic it crashes in all combinations while with both other kernels it works. I was not able to obtain any detailed crash information from Firefox 51.0.1, but Iceweasel 3.5.16 crashed completely, allowing me to obtain a stack trace which shows the relation to stack operations performed by the plugin, even without proper debug symbols: > (gdb) bt full > #0 0x7fa06d805307 in _expand_stack_to(unsigned char*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #1 0x7fa06d8053ae in os::Linux::manually_expand_stack(JavaThread*, unsigned char*) () >from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #2 0x7fa06d80cf0b in JVM_handle_linux_signal () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #3 0x7fa06d802e13 in signalHandler(int, siginfo*, void*) () from /opt/java-8-oracle/jre/lib/amd64/server/libjvm.so > No symbol table info available. > #4 I first assumed a bug in the Java plugin, but it works fine in Linux 4.11.6. The crash will be triggered by any applet, for example the test applet at: * https://java.com/en/download/installed8.jsp I'm running the Ubuntu 16.04 based KDE Neon distribution which somehow apparently does not allow me to use apport to report this bug: > $ LANG= apport-cli linux-image-4.4.0-81-generic > > *** Collecting problem information > > The collected information can be sent to the developers to improve the > application. This might take a few minutes. > . > > *** Problem in linux-image-4.4.0-81-generic > > The problem cannot be reported: > > This is not an official KDE package. Please remove any third party package and try again. If someone can tell me how to get apport working for this package, I can use it to collect additional information, but (unfortunately?) the problem should be fairly easy to reproduce... To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1699772/+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 1893002] Re: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging
This is fixed by: alsa-ucm-conf (1.2.2-1ubuntu0.8) focal; urgency=medium * d/p/0001-HDA-Intel-add-RearMic-JackControl.patch Add "Rear Mic Jack" to make P520 rear mic works correctly. (LP: #1929371) -- Jeremy Szu Tue, 25 May 2021 11:42:01 + So set this bug to fix_released. ** Changed in: alsa-ucm-conf (Ubuntu Focal) Status: New => Fix Released ** Changed in: alsa-ucm-conf (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1893002 Title: alsa-ucm-conf: the rear mic on Lenovo p520 can't be detected when hot plugging Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in alsa-ucm-conf source package in Groovy: Won't Fix Bug description: This bug is for tracking purpose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1893002/+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 1940488] Re: dell300x: rsi wifi and bluetooth crash after suspend and resume
** Changed in: linux (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1940488 Title: dell300x: rsi wifi and bluetooth crash after suspend and resume Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-dell300x source package in Bionic: Fix Released Bug description: I tested the upstream stable kernel 4.19.191, also could reproduce this issue, and reported this testing result to stable mail list. [Impact] On the Dell300x machine, after system suspend and resume, the wifi and bluetooth can't work anymore. [Fix] Revert a patch which was applied to bionic kernel from stable update. [Test] Booting up with the patched kernel, run $sudo rtcwake -m freeze -s 10, then check dmesg to make sure there is crashing log, and run 'nmcli d wifi' and 'bluetoothctl, power on, scan on', all worked well. [Where problems could occur] After applying this SRU, the rsi wifi and bluetooth could have come change, like wifi and bluetooth can't work well after resume, but this possibility is very low, I already run '$sudo rtcwake -m freeze -s 10' for 50 times, the wifi and bluetooth still worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1940488/+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 1941669] Re: alsa: the soundwire audio doesn't work on the Dell TGL-H machines
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1941669 Title: alsa: the soundwire audio doesn't work on the Dell TGL-H machines Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: These 2 patches were merged to upstream kernel from v5.12, no need to send them to impish/oem-5.13/unstable kernels. And this patch is already in the oem-5.10 kernel, for focal kernel, since focal kernel doesn't support soundwire audio, these 2 patches are useless for focal kernel. [Impact] The Dell precision 5760 is a TGL-H machine, and it has soundwire audio design, when running the hirsute kernel, the audio driver fails to load sof-firmware, then the whole audio fails to initialize and fails to work. [Fix] Backport 2 patches, these will remove hardcoded firmware name and allow load firmware according to the firmware name defined by pciid [Test] Booting the patched kernel, check dmesg, there is no errors about loading audio sof-firmware, playsound to spk and headphone, all worked well, record sound from internal mic and external mic, all worked well. [Where problems could occur] The patch remove the hardcoded firmware for all TGL soundwire machines, this could make the TGL soundwire machines fail to load the sof-firmware then the whole audio fail to work. But this possibiliy is low, since we tested the patches on different TGL soundwire machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1941669/+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 1878623] Re: Dell Inspiron 1525 Laptop internal speakers not working
This bug should be fixed from the pulseaudio, I close this bug first, If there is still speaker issue, could reopen the bug. ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878623 Title: Dell Inspiron 1525 Laptop internal speakers not working Status in linux package in Ubuntu: Fix Released Bug description: I upgraded from ubuntu 19.10 to 20.04 recently. 20.04 is excellent for me other than the laptop internal speakers (e.g when watching you tube video) do not work/are not recognised in 20.04. The internal speakers did work in 19.10. I can still listen to sound via headphone socket and external speakers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: alfred 983 F pulseaudio /dev/snd/pcmC0D0p: alfred 983 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 14 15:09:01 2020 InstallationDate: Installed on 2019-11-21 (174 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 1525 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=44d00494-3bf6-479f-a3aa-582d0bc78c25 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (2 days ago) dmi.bios.date: 10/16/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0U990C dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd10/16/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: Inspiron 1525 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878623/+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 1945535] Re: Xorg freeze
*** This bug is a duplicate of bug 1944397 *** https://bugs.launchpad.net/bugs/1944397 It seems to be the vc4 kernel driver (Broadcom graphics) that keeps crashing. I suggest we treat this as a duplicate of bug 1944397 unless proven otherwise. ** Package changed: xorg (Ubuntu) => linux-raspi (Ubuntu) ** This bug has been marked a duplicate of bug 1944397 HDMI does not display anything with Impish RPi desktop image -- 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/1945535 Title: Xorg freeze Status in linux-raspi package in Ubuntu: New Bug description: gnome constantly freezes on ubuntu 21.10. steps to reproduce: open chromium-browser Click on the top bar gnome freezes instantly, requiring a hard reset. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-1007.8-hostname 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:39:12 2021 DistUpgraded: 2021-09-29 14:59:02,376 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:2C:45:7B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1945535/+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 1888166] Re: soc/amd/renoir: change the module name to make it work with ucm3
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1888166 Title: soc/amd/renoir: change the module name to make it work with ucm3 Status in HWE Next: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] the alsa upstream worte the ucm3 files for amd renoir audio, but to load the ucm3, it depends on the kernel module name, and the upstream ucm3 needs the name snd-xxx, so we need to backport the patch from mainline kernel to change the kernel module name to meet ucm3 requirement. [Fix] Backport 1 patch from upstream. [Test Case] boot the kernel with the patch on amd renoir machines (lenovo machines), the audio driver works well (via command line like aplay or areord), then upgrade the alsa-lib and alsa-ucm-conf to 1.2.3.2, now we could see the audio devices from gnome, and they work well. [Regression Risk] Low, this SRU are only specific to soc/amd/renoir, and we already tested on 2 lenovo machines, their audio worked as before. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1888166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-snapdragon/4.15.0.1114.117)
All autopkgtests for the newly accepted linux-meta-snapdragon (4.15.0.1114.117) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lxd/3.0.3-0ubuntu1~18.04.1 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-snapdragon [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time
** Changed in: pulseaudio (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1902464 Title: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Incomplete Bug description: After backporting following patches from PA and alsa-ucm-conf and then it works. https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354 https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355 https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB- Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51] Here is the test PPA: https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test Since the upstream not yet accepted those patches, the regression potential may quite high. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1924685] Re: No sound output/input available after installing 21.04
The latest ubuntu 5.11 kernel like 5.11.0-37.41-generic already includes all fixes for the machines in this bug. set this bug to fix_released. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Importance: Undecided => Critical -- 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/1924685 Title: No sound output/input available after installing 21.04 Status in OEM Priority Project: Won't Fix Status in Release Notes for Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Image: Hirsute 21.04 (20210415 daily build) Device: Dell Precision 5750 After installing 21.04, the sound card is unavailable. In Sound Settings, there is only one choice: "Dummy Output" . The only way to hear sound is to connect a Bluetooth speaker. Note: this device was enabled with 20.04 and 5.6.0-1035-oem kernel: https://certification.ubuntu.com/hardware/202002-27726 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-14-generic 5.11.0-14.15 ProcVersionSignature: Ubuntu 5.11.0-14.15-generic 5.11.12 Uname: Linux 5.11.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu62 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1561 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 15:10:05 2021 InstallationDate: Installed on 2021-04-16 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415) MachineType: Dell Inc. Precision 5750 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-14-generic root=UUID=2562d52a-de88-45e9-9d0a-3a79e48b1638 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-14-generic N/A linux-backports-modules-5.11.0-14-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.release: 1.6 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:br1.6:svnDellInc.:pnPrecision5750:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5750 dmi.product.sku: 0990 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1924685/+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 1945535] [NEW] Xorg freeze
You have been subscribed to a public bug: gnome constantly freezes on ubuntu 21.10. steps to reproduce: open chromium-browser Click on the top bar gnome freezes instantly, requiring a hard reset. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-1007.8-hostname 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 29 15:39:12 2021 DistUpgraded: 2021-09-29 14:59:02,376 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805/806 xHCI USB 3.0 Controller Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1360x768M@60 smsc95xx.macaddr=E4:5F:01:2C:45:7B vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to impish on 2021-09-29 (0 days ago) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.1-2ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug arm64 arm64-image freeze impish raspi-image third-party-packages ubuntu wayland-session -- Xorg freeze https://bugs.launchpad.net/bugs/1945535 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1786013] Autopkgtest regression report (linux-meta-kvm/4.15.0.1101.97)
All autopkgtests for the newly accepted linux-meta-kvm (4.15.0.1101.97) for bionic have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.10.8-1ubuntu2~18.04.3 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu4.2 (amd64) kpatch/0.5.0-0ubuntu1.1 (amd64) glibc/2.27-3ubuntu1.4 (amd64) ddcci-driver-linux/0.3.1-2ubuntu0.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1939297] Re: External monitors are black (connected through USB-C hub)
I've just booted up on the 5.11.0-37-generic and it seems to be fixed for me also: ~[08:44]> uname -a Linux jay-t15-u 5.11.0-37-generic #41~20.04.2-Ubuntu SMP Fri Sep 24 09:06:38 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Other people with this issue - worth updating to the latest kernel and testing? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939297 Title: External monitors are black (connected through USB-C hub) Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: After upgrading the kernel from 5.8 to 5.11 (5.11.0-25-generic), external monitors (both HDMI and DP) connected through USB-C hub (ThinkPad Thunderbolt 3 Dock Gen 2) do not function properly. I can see them in the Displays settings utility, but they are not receiving any signal. The laptop is ThinkPad T490s and uses Intel UHD Graphics 620 (Whiskey Lake) as a graphic card with the default driver (no Additional Drivers). I see the following errors in dmesg repeated several times per second [5.383739] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful [5.907908] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun [ 854.832801] i915 :00:02.0: [drm] *ERROR* CPU pipe C FIFO underrun ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-25-generic 5.11.0-25.27~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 9 14:01:47 2021 InstallationDate: Installed on 2020-07-26 (378 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1939297/+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 1942619] Re: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu]
After 20 days with the mainline 5.14.0 kernel, I have not seen a reoccurrence this behavior. There was one "WARNING: ... decide_linksettings [amdgpu]" kernel message, but the inability to bring the display port monitors back up did not occur. -- 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/1942619 Title: WARNING: ... decide_link_settings+0x1ab/0x1d0 [amdgpu] Status in linux package in Ubuntu: Confirmed Bug description: This has hit me twice in the last 24 hours. Displays come in and out of power saving, without actually displaying anything. The console doesn't become usable. It seems to be unrecoverable, shutdown gets stuck somewhere and I end up having to hit the reset button. This is a desktop machine, which suspends frequently, usually without issue. Radeon RX 570, dual monitor, display link ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.31.33 ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22 Uname: Linux 5.11.0-31-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Sep 3 10:11:35 2021 InstallationDate: Installed on 2019-06-18 (808 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-31-generic root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-31-generic N/A linux-backports-modules-5.11.0-31-generic N/A linux-firmware 1.197.3 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-09 (116 days ago) dmi.bios.date: 11/27/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.90 dmi.board.name: B450M Steel Legend dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942619/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
This bug was fixed in the package linux-firmware - 1.201 --- linux-firmware (1.201) impish; urgency=medium * Rebase to upstream commit 7a30050592e20f494ad331b90737913d59167c3f Rebase against git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git - i915: Update ADLP DMC v2.12 - amdgpu: add initial firmware for Yellow Carp (LP: #1945227) - iwlwifi: add FWs for new So device types with multiple RF modules - linux-firmware: Update firmware file for Intel Bluetooth 8265 - linux-firmware: Update firmware file for Intel Bluetooth 9260 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX200 - linux-firmware: Update firmware file for Intel Bluetooth AX210 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - qed: Add firmware 8.59.1.0 - linux-firmware: Update firmware file for Intel Bluetooth 9560 - linux-firmware: Update firmware file for Intel Bluetooth AX201 - linux-firmware: Update firmware file for Intel Bluetooth AX211 - linux-firmware: update frimware for mediatek bluetooth chip (MT7921) - cxgb4: Update firmware to revision 1.26.2.0 - amdgpu: Add initial firmware for Beige Goby - amdgpu: update VCN firmware for raven - amdgpu: update VCN firmware for raven2 - amdgpu: update VCN firmware for picasso - amdgpu: update VCN firmware for renoir - amdgpu: update VCN firmware for vangogh - amdgpu: update VCN firmware for sienna cichlid - amdgpu: update VCN firmware for navy flounder - amdgpu: update VCN firmware for dimgrey cavefish - linux-firmware: Update firmware file for Intel Bluetooth 9462 - brcm: Add 43455 based AP6255 NVRAM for the ACEPC T8 Mini PC -- Timo Aaltonen Wed, 29 Sep 2021 11:36:54 +0300 ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1944754] Re: linux-tools-aws package does not contain libperf-jvmti.so
This bug is awaiting verification that the linux-aws/5.11.0-1020.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute ** Tags added: verification-needed-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1944754 Title: linux-tools-aws package does not contain libperf-jvmti.so Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws source package in Impish: Fix Committed Bug description: SRU Justification [Impact] For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf. To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so. [Test Plan] Install linux-tools-aws, check for libperf-jvmti.so [Where problems could occur] Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression. [Additional info] SF: #00319833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1944754/+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 1944754] Re: linux-tools-aws package does not contain libperf-jvmti.so
This bug is awaiting verification that the linux-aws/5.4.0-1058.61 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1944754 Title: linux-tools-aws package does not contain libperf-jvmti.so Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Bionic: Fix Committed Status in linux-aws source package in Focal: Fix Committed Status in linux-aws source package in Hirsute: Fix Committed Status in linux-aws source package in Impish: Fix Committed Bug description: SRU Justification [Impact] For debugging purposes, on EC2, people will install linux-tools-$(uname -r) to help with debugging the system. This selects the kernel specific linux-tools package, and for the AWS variant, we are missing the library libperf-jvmti.so to enable tracing Java applications with perf. To get a libperf-jvmti.so library, we need to perform an additional and confusing step by installing linux-tools-generic to get a copy of the library. Customers on AWS EC2 should not have to do this. We would like the linux-tools-aws packages to contain libperf-jvmti.so. [Test Plan] Install linux-tools-aws, check for libperf-jvmti.so [Where problems could occur] Given that linux-tools-aws installs in a versioned (unique) directory, there should be no conflicts or possibility of regression. [Additional info] SF: #00319833 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1944754/+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 1945351] Re: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011
This bug is awaiting verification that the linux-oracle/5.11.0-1020.21 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-hirsute' to 'verification-done-hirsute'. If the problem still exists, change the tag 'verification-needed-hirsute' to 'verification-failed-hirsute'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-hirsute -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1945351 Title: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011 Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle source package in Hirsute: Fix Committed Bug description: [Impact] No support for arm64 console currently [Fix] Add arm64 console support [Test] Confirm that it boots on desired arm64 hardware, as well as VMs, and produces console output. [Regression Potential] This was never working on arm64 so there should be no risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1945351/+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 1933880] Re: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-465 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-465 in Ubuntu. https://bugs.launchpad.net/bugs/1933880 Title: systemd-logind crash when suspend with nvidia-suspend.service masked, bringing session down with it Status in nvidia-graphics-drivers-465 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Run `sudo apt install nvidia-driver-465`. Then, without a need for a restart, run `sudo apt autoremove nvidia-driver-465`. 2. Leaving the terminal open, suspend the machine. Expected behavior: the machine suspend successfully and can be woken up successfully. Actual behavior: the machine doesn't suspend. It either: - hang with no respond other than SysRq+REISUB (or maybe network, but I didn't test), or - return you back to the login screen. Upon logging in, you'll notice that the terminal you opened is gone. Upon further inspection (on a session that doesn't hang), it's been found that X server died with: Fatal server error: [66.422] (EE) systemd-logind disappeared (stopped/restarted?) And checking journal for systemd-logind log, it said: Error during inhibitor-delayed operation (already returned success to client): Unit nvidia-suspend.service is masked. before the new process takes it place. The system is Ubuntu 20.04, X.org session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 29 03:34:00 2021 InstallationDate: Installed on 2021-03-15 (105 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=th_TH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic root=UUID=06f2a676-a62c-443a-8bc8-4e0eda4600f4 ro log_buf_len=2M quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/01/2021 dmi.bios.release: 1.31 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN31WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0Q55756 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.ec.firmware.release: 1.31 dmi.modalias: dmi:bvnLENOVO:bvrEUCN31WW:bd01/01/2021:br1.31:efr1.31:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55756WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-465/+bug/1933880/+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 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Same problem, I use mint 20.2 NVIDIA driver 470.63.01 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_hda_ext_core snd_soc_acpi_intel_match
[Kernel-packages] [Bug 1938722] Re: watchdog: BUG: soft lockup on Threadripper 2950X
Tripped this again today w/ 5.4.0-86-generic: [179417.505068] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:1:691464] [179417.505110] Modules linked in: xt_multiport cpuid veth xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf_nat br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua edac_mce_amd ftdi_sio eeepc_wmi kvm_amd usbserial asus_wmi sparse_keymap snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio kvm snd_hda_codec_hdmi video snd_hda_intel snd_intel_dspcfg wmi_bmof snd_hda_codec snd_hda_core snd_hwdep snd_pcm k10temp snd_timer snd soundcore ccp mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype sch_fq_codel xt_tcpudp xt_conntrack nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter bpfilter msr 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 hid_generic uas usbhid hid [179417.505142] usb_storage amdgpu crct10dif_pclmul crc32_pclmul ghash_clmulni_intel amd_iommu_v2 gpu_sched aesni_intel ttm crypto_simd drm_kms_helper cryptd syscopyarea glue_helper sysfillrect sysimgblt fb_sys_fops igb mxm_wmi drm dca i2c_algo_bit ahci libahci i2c_piix4 wmi gpio_amdpt gpio_generic [179417.505153] CPU: 2 PID: 691464 Comm: kworker/2:1 Not tainted 5.4.0-86-generic #97-Ubuntu [179417.505154] Hardware name: System manufacturer System Product Name/ROG STRIX X399-E GAMING, BIOS 1203 10/09/2019 [179417.505160] Workqueue: events free_work [179417.505164] RIP: 0010:smp_call_function_many+0x208/0x270 [179417.505166] Code: 92 00 3b 05 8e c9 70 01 89 c7 0f 83 9b fe ff ff 48 63 c7 48 8b 0b 48 03 0c c5 80 99 84 af 8b 41 18 a8 01 74 0a f3 90 8b 51 18 <83> e2 01 75 f6 eb c8 89 cf 48 c7 c2 e0 b8 c4 af 4c 89 fe e8 00 1d [179417.505166] RSP: 0018:a88c84877d00 EFLAGS: 0202 ORIG_RAX: ff13 [179417.505167] RAX: 0003 RBX: 97e83d0abd40 RCX: 97e83d072080 [179417.505168] RDX: 0003 RSI: RDI: 0001 [179417.505168] RBP: a88c84877d40 R08: 97e836da7c40 R09: 0003 [179417.505169] R10: 97e836da7c40 R11: 0002 R12: ae481930 [179417.505169] R13: R14: 0001 R15: 0080 [179417.505170] FS: () GS:97e83d08() knlGS: [179417.505170] CS: 0010 DS: ES: CR0: 80050033 [179417.505171] CR2: 7fde360abfb0 CR3: 0003f880a000 CR4: 003406e0 [179417.505171] Call Trace: [179417.505176] ? load_new_mm_cr3+0xf0/0xf0 [179417.505177] on_each_cpu+0x2d/0x60 [179417.505178] flush_tlb_kernel_range+0x38/0x90 [179417.505179] __purge_vmap_area_lazy+0x70/0x6d0 [179417.505180] free_vmap_area_noflush+0xe1/0xf0 [179417.505180] remove_vm_area+0x9a/0xb0 [179417.505181] __vunmap+0x5f/0x210 [179417.505182] free_work+0x25/0x30 [179417.505184] process_one_work+0x1eb/0x3b0 [179417.505185] worker_thread+0x4d/0x400 [179417.505186] kthread+0x104/0x140 [179417.505187] ? process_one_work+0x3b0/0x3b0 [179417.505188] ? kthread_park+0x90/0x90 [179417.505190] ret_from_fork+0x22/0x40 [179426.629482] Sending NMI from CPU 11 to CPUs 17: [179445.505306] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [kworker/2:1:691464] -- 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/1938722 Title: watchdog: BUG: soft lockup on Threadripper 2950X Status in linux package in Ubuntu: Confirmed Bug description: Description:Ubuntu 20.04.2 LTS Release:20.04 Been suddenly seeing a number of crashes today on my threadripper 2950x box today after the system being off over the weekend. Suspect it may be tied to Ubuntu 5.4.0-80.90-generic 5.4.124 kernel, as I wasn't seeing it last week or previously. Aug 2 16:52:14 threadripper kernel: [ 600.168436] watchdog: BUG: soft lockup - CPU#19 stuck for 22s! [kworker/19:0:11301] Aug 2 16:52:14 threadripper kernel: [ 600.168490] Modules linked in: veth xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat nf _nat br_netfilter bridge stp llc aufs overlay nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi eeepc_wmi snd_hda_intel edac_mce_amd snd_intel_dspcfg asus_wmi ftdi_sio snd_hda_codec kvm_amd usbserial sparse_keymap snd_ hda_core kvm video wmi_bmof snd_hwdep snd_pcm snd_timer snd ccp soundcore k10temp mac_hid nf_log_ipv6 ip6t_REJECT nf_reject_ipv6 xt_hl ip6t_rt nf_log_ipv4 nf_log_common ipt_REJECT nf_reject_ipv4 xt_LOG xt_limit xt_addrtype sch_fq_codel xt_tcpudp xt_conntrack
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Results of doing a memtest. ** Attachment added: "memtest-2021-09-29-14-40.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5529183/+files/memtest-2021-09-29-14-40.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1939966] Re: [Asus TUF Gaming FA506IV] Random system stops
Lasted 16 hours before blackscreening (a new record). I'm all out of ideas. ** Attachment added: "prevboot-2021-09-29-a.txt" https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1939966/+attachment/5529182/+files/prevboot-2021-09-29-a.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1939966 Title: [Asus TUF Gaming FA506IV] Random system stops Status in linux-hwe-5.11 package in Ubuntu: New Status in nvidia-graphics-drivers-470 package in Ubuntu: New Bug description: Every once in a while (it's been three times this week), the entire system will just stop. There's still electricity running. The keyboard is lit up, and the monitor is black (electricity-running black, and not shutdown-black). There's no picture and no sound. Just immediately before it does, I know it's about to happen because whatever audio is playing at the time will begin repeating, and then the computer goes down. I don't actually know if it's an Xorg problem. It just sounded like the closest possibility, based on the way the computer actually behaves. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 470.57.02 Tue Jul 13 16:14:05 UTC 2021 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04) ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Aug 14 19:34:11 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:1e21] Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21] InstallationDate: Installed on 2021-03-20 (147 days ago) InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA506IV.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: FA506IV 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.ec.firmware.release: 3.9 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: TUF Gaming FA506IV dmi.product.name: TUF Gaming FA506IV_TUF506IV dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 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.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
SRU: * https://lists.ubuntu.com/archives/kernel-team/2021-September/124403.html (linux-firmware/focal) * https://lists.ubuntu.com/archives/kernel-team/2021-September/124404.html (linux-firmware/impish) ** Summary changed: - Missing CNVi firmware for Intel AX211/AX201 on ADL + Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201/9560/9462 on ADL-S/ADL-P Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1942299] Re: CD/DVD tray ejects on boot or waking from suspend
Fixed after updating to the latest kernel: Linux 5.4.0-88-generic (on Ubuntu 20.04 LTS Focal amd64) Thank you :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1942299 Title: CD/DVD tray ejects on boot or waking from suspend Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: [Impact] A regression was introduced via upstream -stable patches which causes the CD / DVD rom drive to open when the system boots, or wakes from suspend. This has had some side effects on some systems where you cannot insert media at all, since the drive will eject as soon as the tray is closed. The problematic patch is: commit 7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 Author: ManYi Li Date: Fri Jun 11 17:44:02 2021 +0800 Subject: scsi: sr: Return appropriate error code when disk is ejected Link: https://github.com/torvalds/linux/commit/7dd753ca59d6c8cc09aa1ed24f7657524803c7f3 This was backported to: Bionic 4.15.0-155-generic Focal 5.4.0-82-generic Hirsute 5.11.0-32-generic Impish 5.13.0-1-generic [Fix] The issue was fixed in the below commit: commit 5c04243a56a7977185b00400e59ca7e108004faf Author: Li Manyi Date: Mon Jul 26 19:49:13 2021 +0800 Subject: scsi: sr: Return correct event when media event code is 3 Link: https://github.com/torvalds/linux/commit/5c04243a56a7977185b00400e59ca7e108004faf This patch is already applied to Ubuntu kernels through upstream -stable, and will land in the following releases, currently in -proposed: Bionic 4.15.0-159-generic Focal 5.4.0-87-generic Hirsute 5.11.0-37-generic Impish 5.13.0-16-generic [Testcase] If your machine is affected, the CD / DVD rom drive will eject and / or open during boot or waking from suspend. This can be seen on some hypervisors, particularly VMware. [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299/+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 1943616] Re: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 Fixed after updating to the latest kernel: Linux 5.4.0-88-generic Thank you :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943616 Title: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 20.04.3 LTS amd64. Updating to kernel 5.4.0-84 seems to have been the cause. It's a known bug in the Linux kernel This is the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=213795 There's a patch there too. Related launchpad bugs: After hibernation #1943379 https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379 On Impish #1942299 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943616/+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 1943616] Re: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal
*** This bug is a duplicate of bug 1942299 *** https://bugs.launchpad.net/bugs/1942299 I can't see how to close this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1943616 Title: CD-ROM tray opens on wake from suspend on Ubuntu 20.04 LTS Focal Status in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I'm using Ubuntu 20.04.3 LTS amd64. Updating to kernel 5.4.0-84 seems to have been the cause. It's a known bug in the Linux kernel This is the upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=213795 There's a patch there too. Related launchpad bugs: After hibernation #1943379 https://bugs.launchpad.net/ubuntu/+source/udev/+bug/1943379 On Impish #1942299 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942299 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1943616/+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 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 I'm using Ubuntu 20.04 on an old Lenovo Yoga and none of the workaround had any effect except adding "psmouse.synaptics_intertouch=0" to GRUB_CMDLINE_LINUX in /etc/default/grub. The only problem is that now it wont stay suspended.. It does go under suspend mode for like 3 seconds and wakes up immediatly, but at least the trackpad/nub still works. sighs -- 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/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW 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 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-32-generic root=/dev/mapper/ubuntu--vg-root ro ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-32-generic N/A linux-backports-modules-4.15.0-32-generic N/A linux-firmware 1.173.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET42W (1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BSCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0E50512 STD dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET42W(1.20):bd09/13/2017:svnLENOVO:pn20BSCTO1WW:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BSCTO1WW:rvrSDK0E50512STD:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 3rd dmi.product.name: 20BSCTO1WW dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788928/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1933938] Re: Missing CNVi firmware for Intel AX211/AX201 on ADL
** Changed in: linux-firmware (Ubuntu Focal) Status: Incomplete => In Progress ** Changed in: linux-firmware (Ubuntu Impish) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1933938 Title: Missing CNVi firmware for Intel AX211/AX201 on ADL Status in HWE Next: New Status in intel: New Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-firmware source package in Focal: In Progress Status in linux-oem-5.13 source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux-firmware source package in Impish: In Progress Status in linux-oem-5.13 source package in Impish: Invalid Bug description: [SRU Justfication] [Impact] Intel CNVi moves key elements of Wi-Fi and Bluetooth Technology into Intel processors. As a result, their driver may have to be revised across processor generations. [Fix] This depends on a few changes set to address all issues on supporting: * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.* (ADL-S) * BT: intel/ibt-0040-0041.* (ADL-P) * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: intel/ibt-1040-4150.* * BT: intel/ibt-0040-4150.* * PCI [8086:7af0] Subsystem [8086:0aaa] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* AX201 wifi firmware for ADL platforms will be available with FW API >= 64, so a patchset "iwlwifi: bump FW API to 64 for AX devices" will be required. Depending fixes are pulled as well. For reset of them, 3 additional commits for iwlwifi, also in mainline now, are required. The last patch for 9462 Bluetooth is still under review at the time of writing. This is the only patch that is not yet in unstable. [Test Case] Install these CRF on ADL-S/ADL-P platforms and check if WiFi/Bluetooth is working. [Where problems could occur] While this is a new generation, we may have common issues like power consumption, network throughput, suspend/resume issues. [Other Info] Intel is to release the corresponding firmware blobs next week. These are verified with pre-released firmware. == original bug report == * PCI [8086:7af0] Subsystem [8086:4090] (AX211) * WiFi: iwlwifi-so-a0-gf-a0-* * BT: intel/ibt-1040-0041.sfi * PCI [8086:7af0] Subsystem [8086:4070] (AX201) * WiFi: iwlwifi-so-a0-hr-b0-* * BT: ibt-1040-4150.sfi * PCI [8086:7af0] Subsystem [8086:0264] (9462) * WiFi: iwlwifi-so-a0-jf-b0-* * BT: intel/ibt-1040-1020.* * BT: intel/ibt-0040-1020.* To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1933938/+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 1941673] Re: keyboard and touchpad crashes after opening lid
I have probably not the same hardware, but I have unresponding keyboard and touchpad very often after resume. They work again after maybe 20 seconds. Nothing appears in dmesg. I have also a maybe related bug: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1945444 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941673 Title: keyboard and touchpad crashes after opening lid Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: I have set the configuration s.t If I close the lid my laptop will suspend. But after resume from suspend keyboard and touchpad do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:42:51 2021 InstallationDate: Installed on 2021-07-19 (37 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1941673/+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 1941673] Re: keyboard and touchpad crashes after opening lid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-signed-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1941673 Title: keyboard and touchpad crashes after opening lid Status in linux-signed-hwe-5.11 package in Ubuntu: Confirmed Bug description: I have set the configuration s.t If I close the lid my laptop will suspend. But after resume from suspend keyboard and touchpad do not work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Aug 26 09:42:51 2021 InstallationDate: Installed on 2021-07-19 (37 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1941673/+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 1945517] [NEW] Focal update: v5.4.145 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.145 upstream stable release from git://git.kernel.org/ fscrypt: add fscrypt_symlink_getattr() for computing st_size ext4: report correct st_size for encrypted symlinks f2fs: report correct st_size for encrypted symlinks ubifs: report correct st_size for encrypted symlinks kthread: Fix PF_KTHREAD vs to_kthread() race xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats reset: reset-zynqmp: Fixed the argument data type qed: Fix the VF msix vectors flow net: macb: Add a NULL check on desc_ptp qede: Fix memset corruption perf/x86/intel/pt: Fix mask of num_address_ranges perf/x86/amd/ibs: Work around erratum #1197 perf/x86/amd/power: Assign pmu.module cryptoloop: add a deprecation warning ARM: 8918/2: only build return_address() if needed ALSA: hda/realtek: Workaround for conflicting SSID on ASUS ROG Strix G17 ALSA: pcm: fix divide error in snd_pcm_lib_ioctl ARC: wireup clone3 syscall media: stkwebcam: fix memory leak in stk_camera_probe igmp: Add ip_mc_list lock in ip_check_mc_rcu USB: serial: mos7720: improve OOM-handling in read_mos_reg() ipv4/icmp: l3mdev: Perform icmp error route lookup on source device routing table (v2) powerpc/boot: Delete unneeded .globl _zimage_start net: ll_temac: Remove left-over debug message mm/page_alloc: speed up the iteration of max_order Revert "r8169: avoid link-up interrupt issue on RTL8106e if user enables ASPM" x86/events/amd/iommu: Fix invalid Perf result due to IOMMU PMC power-gating Revert "btrfs: compression: don't try to compress if we don't have enough pages" ALSA: usb-audio: Add registration quirk for JBL Quantum 800 usb: host: xhci-rcar: Don't reload firmware after the completion usb: mtu3: use @mult for HS isoc or intr usb: mtu3: fix the wrong HS mult value xhci: fix unsafe memory usage in xhci tracing x86/reboot: Limit Dell Optiplex 990 quirk to early BIOS versions PCI: Call Max Payload Size-related fixup quirks early Linux 5.4.145 UBUNTU: upstream stable to v5.4.145 ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + v5.4.145 upstream stable release + from git://git.kernel.org/ -v5.4.145 upstream stable release -from git://git.kernel.org/ + fscrypt: add fscrypt_symlink_getattr() for computing st_size + ext4: report correct st_size for encrypted symlinks + f2fs: report correct st_size for encrypted symlinks + ubifs: report correct st_size for encrypted symlinks + kthread: Fix PF_KTHREAD vs to_kthread() race + xtensa: fix kconfig unmet dependency warning for HAVE_FUTEX_CMPXCHG + gpu: ipu-v3: Fix i.MX IPU-v3 offset calculations for (semi)planar U/V formats + reset: reset-zynqmp: Fixed the argument data type + qed: Fix the VF msix vectors flow + net: macb: Add a NULL check on desc_ptp + qede: Fix memset corruption + perf/x86/intel/pt: Fix
[Kernel-packages] [Bug 1945516] [NEW] Touchpad not recognized in the device list. So I can't install driver & no response from touchpad
Public bug reported: My Laptop is Lenovo V15 IIL i5 10th gen laptop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 23:39:03 2021 InstallationDate: Installed on 2021-09-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945516 Title: Touchpad not recognized in the device list. So I can't install driver & no response from touchpad Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: My Laptop is Lenovo V15 IIL i5 10th gen laptop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.11.0-27-generic 5.11.0-27.29~20.04.1 ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 23:39:03 2021 InstallationDate: Installed on 2021-09-28 (0 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) SourcePackage: linux-signed-hwe-5.11 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.11/+bug/1945516/+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 1918582] Re: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-450 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-450 in Ubuntu. https://bugs.launchpad.net/bugs/1918582 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia kernel module failed to build Status in nvidia-graphics-drivers-450 package in Ubuntu: Confirmed Bug description: I changed to use the nvidia-driver-460(proprietary,tested) and this error keep popping up everytime i logged in ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-kernel-source-450 (not installed) ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.8.0-44-generic Date: Tue Mar 9 23:41:30 2021 DuplicateSignature: dkms:nvidia-kernel-source-450:450.51.05-0ubuntu1:/var/lib/dkms/nvidia/450.51.05/build/common/inc/nv-linux.h:508:17: error: too many arguments to function ‘__vmalloc’ InstallationDate: Installed on 2021-02-22 (16 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageVersion: 450.51.05-0ubuntu1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.4 SourcePackage: nvidia-graphics-drivers-450 Title: nvidia-kernel-source-450 450.51.05-0ubuntu1: nvidia 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/nvidia-graphics-drivers-450/+bug/1918582/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
** Description changed: [Impact] New hardware support for AMD's Yellow Carp need five commits backported - to mesa and new firmware. This is only needed on focal, skipping - hirsute/impish (no kernel support there). + to mesa and new firmware. This is only needed on focal, skipping hirsute + (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1944752] Re: AER PCIe Bus Error for Asus X541UVK
Hi, I currently do not have access to a running linux system to compile and test the patch with, since the only pc that I have is my laptop affected by this bug, and I also really need windows on it for some windows-specific software for my university. So, It's not possible for me right now to test the patch. I'll leave some more specific info about my system (hoping that somebody else has the same exact machine) for anyone that is willing to test this (I'm copying this from System Information). System ModelX541UVK Processor Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz Adapter Description Intel(R) HD Graphics 620 Adapter Description NVIDIA GeForce 920MX BIOS Version/Date American Megatrends Inc. X541UVK.308, 30-Jan-18 Thanks to everyone for the help, I'll keep in touch. Riccardo -- 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/1944752 Title: AER PCIe Bus Error for Asus X541UVK Status in linux package in Ubuntu: Incomplete Bug description: I already posted this on the Ubuntu Forums and I'm revisiting it now with more information and accuracy. Whenever I try to install any flavor of *buntu, I always run into this problem; a process taking up all of my CPU and after a while, it crashes the system and the whole screen goes black with text spamming. It shows some PCI errors non-stop, and following some guides online i tried to fix it but never actually succeeded. The distro I was trying to install this time was the default 20.04.2 Ubuntu. My PC is a laptop, it's an ASUS X541UVK with an i7 7500U and Geforce 920MX. At first I thought that there was a problem with the Nvidia GPU but it appears to be with the Realtek BT card. I went to follow this guide: https://forums.linuxmint.com/viewtopic.php?t=305970 (since using pci=nomsi once solved the issue some time ago) And the reproduced steps from the guide above are here (from the live usb): https://imgur.com/a/enq5UCt However this still doesn't solve my problems. I submitted my information at the time on this bug: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173 But now I made a duplicate of the bug since my pc has slightly different hardware. Also, I have a little bit more free time now. So, this time, I tried again with Ubuntu 20.04.3 and the results were pretty much the same; after booting up Ubuntu reported an "internal error" and I just managed to open the Gnome System Monitor (and sort the processes by CPU usage) just before the entire pc froze. Here are some pictures: https://imgur.com/a/Sd7TO4y Then, as suggested in the original bug report ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1521173/comments/139 ), I tried booting using the "pci=noaer" option, and the desktop at first booted fine, much quicker than before also, but for a few seconds the screen went black and these appeared on screen: https://imgur.com/a/Ppq2D0W Then after that it just went back to normal, and I didn't notice any anomaly. Also here (again, as suggested in the other bug report) I copy-pasted the results of "lspci -nn" and "dmesg": https://pastebin.com/HMvdhvnz https://pastebin.com/pnjPNcWr I really hope this helps towards finding the issue :) for anything else for me to try, feel free to suggest and I'll try it and report the results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1944752/+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 1945393] Re: package linux-headers-5.11.0-37-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dp
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-hwe-5.11 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945393 Title: package linux-headers-5.11.0-37-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: Confirmed Bug description: The installation process failed. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic (not installed) ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22 Uname: Linux 5.11.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 11:13:50 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:(not installed) Unpacking linux-headers-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-UamDef/6-linux-headers-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-09-15 (13 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic (not installed) failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1945393/+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 1934647] Re: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine
Noting here that the fix for 1936708 (https://bugs.launchpad.net/ubuntu/hirsute/+source/linux/+bug/1936708) also resolves this problem for me. (Granted, that seems to be in the works only for 5.11.x on Hirsute, and not 5.8.x on Focal, but I figure it's worth flagging for others affected.) Not sure when they'll put the finishing touches on that kernel release, but it's one to look forward to. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1934647 Title: [HP Pavilion Gaming Laptop 15-dk0xxx] Black screen at login using 5.8.0-59, but 5.8.0-43 and 5.12.14 work fine Status in linux-hwe-5.8 package in Ubuntu: Confirmed Bug description: If I choose nvidia driver, then the screen is black and I cannot log in. To log in, I need to delete all nvidia files. After that, the xorg is selected and I can log in. But I cannot edit brightness. I can hardly see anything on the screen. The battery is draining very badly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.8/+bug/1934647/+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 1944397] Re: HDMI does not display anything with Impish RPi desktop image
New plan: I'll back out the vc4 breakage from 5.11 so we don't need a FW bump on hirsute. ** No longer affects: linux-firmware-raspi2 (Ubuntu Hirsute) -- 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/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi package in Ubuntu: Fix Committed Status in linux-raspi source package in Hirsute: New Status in linux-firmware-raspi2 source package in Impish: New Status in linux-raspi source package in Impish: Fix Committed Bug description: Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+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 1945494] [NEW] [EHL] Quadrature Encoder Peripheral support for sprint 2
Public bug reported: Tracking bug, please don't triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: Confirmed ** Tags: intel oem-priority originate-from-1929897 ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Confirmed ** Tags added: intel oem-priority originate-from-1929897 ** Summary changed: - Quadrature Encoder Peripheral support for sprint 2 + [EHL] Quadrature Encoder Peripheral support for sprint 2 ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Anthony Wong (anthonywong) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945494 Title: [EHL] Quadrature Encoder Peripheral support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Confirmed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945494/+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 1945444] Re: Touchpad randomly freezes
I had another touchpad crash and here is the dmesg output : [10665.178468] i2c_designware i2c_designware.0: controller timed out [10681.337825] i2c_designware i2c_designware.0: controller timed out [10734.714133] i2c_designware i2c_designware.0: controller timed out [10975.448460] i2c_designware i2c_designware.0: controller timed out [11397.751194] i2c_designware i2c_designware.0: controller timed out [11474.262443] i2c_designware i2c_designware.0: controller timed out [12512.320584] irq 27: nobody cared (try booting with the "irqpoll" option) [12512.320589] CPU: 5 PID: 0 Comm: swapper/5 Tainted: G O 5.11.0-37-generic #41~20.04.2-Ubuntu [12512.320591] Hardware name: HUAWEI KLVD-WXX9/KLVD-WXX9-PCB-B2, BIOS 3.02 07/31/2021 [12512.320592] Call Trace: [12512.320592] [12512.320594] dump_stack+0x74/0x92 [12512.320599] __report_bad_irq+0x3a/0xaf [12512.320600] note_interrupt.cold+0xb/0x60 [12512.320601] handle_irq_event_percpu+0x73/0x80 [12512.320604] handle_irq_event+0x3b/0x60 [12512.320605] handle_fasteoi_irq+0x9c/0x150 [12512.320606] common_interrupt+0x70/0x150 [12512.320608] asm_common_interrupt+0x1e/0x40 [12512.320610] RIP: 0010:__do_softirq+0x73/0x29b [12512.320612] Code: 7b 01 67 00 01 00 00 89 75 ac c7 45 c8 0a 00 00 00 48 89 45 c0 48 89 45 b0 65 66 c7 05 54 ba 02 67 00 00 fb 66 0f 1f 44 00 00 ff ff ff ff 49 c7 c3 c0 60 80 99 41 0f bc df 83 c3 01 89 5d d4 [12512.320613] RSP: 0018:b6d500250f90 EFLAGS: 0206 [12512.320614] RAX: 9cc600b83d80 RBX: RCX: 06e0 [12512.320615] RDX: RSI: 04200042 RDI: [12512.320616] RBP: b6d500250fe8 R08: R09: 06ae80dfda07 [12512.320616] R10: 06ae80a20080 R11: 4635 R12: b6d500133d98 [12512.320617] R13: 0001 R14: R15: 0080 [12512.320619] asm_call_irq_on_stack+0xf/0x20 [12512.320620] [12512.320621] do_softirq_own_stack+0x3d/0x50 [12512.320622] irq_exit_rcu+0xa4/0xb0 [12512.320624] sysvec_apic_timer_interrupt+0x3d/0x90 [12512.320625] asm_sysvec_apic_timer_interrupt+0x12/0x20 [12512.320627] RIP: 0010:cpuidle_enter_state+0xdf/0x350 [12512.320629] Code: ff e8 d5 b3 77 ff 80 7d d7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 52 02 00 00 31 ff e8 68 5d 7e ff fb 66 0f 1f 44 00 00 <45> 85 ff 0f 88 e5 00 00 00 49 63 c7 4c 2b 75 c8 48 8d 14 40 48 8d [12512.320630] RSP: 0018:b6d500133e48 EFLAGS: 0246 [12512.320630] RAX: 9cc97096c2c0 RBX: 0001 RCX: 001f [12512.320631] RDX: RSI: 2da97f6a RDI: [12512.320631] RBP: b6d500133e80 R08: 0b604ab14610 R09: 99a4d8e0 [12512.320632] R10: 9cc97096aee4 R11: 9cc97096aec4 R12: d6d4ffd4 [12512.320633] R13: 99a4d8e0 R14: 0b604ab14610 R15: 0001 [12512.320633] ? cpuidle_enter_state+0xbb/0x350 [12512.320635] cpuidle_enter+0x2e/0x40 [12512.320636] call_cpuidle+0x23/0x40 [12512.320638] do_idle+0x1df/0x260 [12512.320639] cpu_startup_entry+0x20/0x30 [12512.320640] start_secondary+0x11f/0x160 [12512.320641] secondary_startup_64_no_verify+0xc2/0xcb [12512.320644] handlers: [12512.320644] [] idma64_irq [idma64] [12512.320648] [<2ed4f530>] i2c_dw_isr [12512.320650] Disabling IRQ #27 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945444 Title: Touchpad randomly freezes Status in linux-signed-hwe-5.11 package in Ubuntu: New Bug description: We have 5 laptops, all brand new Huawei Matebook 14 2021. They have no hardware problem (on Windows it is ok). On Ubuntu Linux, the Elantech touchpad regularly freezes for some seconds, with one of the CPU at 100%. The problem occurs both with kernel 5.4, and also with the new 5.11 kernel. I also tried the kernel 5.14 (with mainline) and the problem was not solved, so I rolled back to 5.11. I see in dmesg output: [ 3335.316965] i2c_designware i2c_designware.0: controller timed out [ 3335.568349] input: ELAN2605:00 04F3:3163 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2605:00/0018:04F3:3163.0001/input/input104 [ 3335.568407] input: ELAN2605:00 04F3:3163 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2605:00/0018:04F3:3163.0001/input/input106 [ 3335.568444] hid-multitouch 0018:04F3:3163.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN2605:00 04F3:3163] on i2c-ELAN2605:00 [ 3335.685062] input: 06CB19AB:00 06CB:1A1A as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-06CB19AB:00/0018:06CB:1A1A.0002/input/input107 [ 3335.685154] hid-multitouch 0018:06CB:1A1A.0002: input,hidraw1: I2C HID v1.00 Device [06CB19AB:00 06CB:1A1A] on i2c-06CB19AB:00 [ 3360.880952] i2c_designware i2c_designware.0: controller timed out [ 3548.917328] watchdog: BUG: soft
[Kernel-packages] [Bug 1929895] Re: [EHL] Enable ISHTP
** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+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 1929895] Re: [EHL] Enable ISHTP
** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1929895 Title: [EHL] Enable ISHTP Status in intel: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux source package in Focal: New Status in linux-intel-5.13 source package in Focal: Fix Committed Bug description: Description This driver enables the OS to talk to eclite firmware on a dedicated low power chip over ISH Transport Protocol (ISHTP) Hardware: Elkhart Lake Target Release: 21.04 Target Kernel: TBD External links: https://github.com/intel/linux-intel-quilt/tree/mainline-tracking-v5.11-yocto-210223T083754Z To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1929895/+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 1945475] Re: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/br
** Tags removed: need-duplicate-check -- 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/1945475 Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-88-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dianekerivan 1609 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 29 09:14:01 2021 DuplicateSignature: package:linux-modules-extra-5.4.0-88-generic:(not installed) Unpacking linux-modules-5.4.0-88-generic (5.4.0-88.99) ... dpkg: error processing archive /tmp/apt-dpkg-install-7eiv6l/15-linux-modules-5.4.0-88-generic_5.4.0-88.99_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-88-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-01-06 (265 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: TOSHIBA Satellite Pro A210 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=9e3c351a-381e-49ad-87e1-07a3a643c33c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to focal on 2021-09-03 (26 days ago) dmi.bios.date: 01/23/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.60 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.60:bd01/23/2008:svnTOSHIBA:pnSatelliteProA210:pvrPSAFHU-010002:rvnATI:rnSB600:rvrRev1:cvnAMD:ct1:cvrNone: dmi.product.name: Satellite Pro A210 dmi.product.version: PSAFHU-010002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945475/+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 1945475] 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/1945475 Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-88-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dianekerivan 1609 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 29 09:14:01 2021 DuplicateSignature: package:linux-modules-extra-5.4.0-88-generic:(not installed) Unpacking linux-modules-5.4.0-88-generic (5.4.0-88.99) ... dpkg: error processing archive /tmp/apt-dpkg-install-7eiv6l/15-linux-modules-5.4.0-88-generic_5.4.0-88.99_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-88-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-01-06 (265 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: TOSHIBA Satellite Pro A210 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=9e3c351a-381e-49ad-87e1-07a3a643c33c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to focal on 2021-09-03 (26 days ago) dmi.bios.date: 01/23/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.60 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.60:bd01/23/2008:svnTOSHIBA:pnSatelliteProA210:pvrPSAFHU-010002:rvnATI:rnSB600:rvrRev1:cvnAMD:ct1:cvrNone: dmi.product.name: Satellite Pro A210 dmi.product.version: PSAFHU-010002 dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945475/+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 1945475] [NEW] package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/
Public bug reported: broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-88-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dianekerivan 1609 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 29 09:14:01 2021 DuplicateSignature: package:linux-modules-extra-5.4.0-88-generic:(not installed) Unpacking linux-modules-5.4.0-88-generic (5.4.0-88.99) ... dpkg: error processing archive /tmp/apt-dpkg-install-7eiv6l/15-linux-modules-5.4.0-88-generic_5.4.0-88.99_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-88-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-01-06 (265 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: TOSHIBA Satellite Pro A210 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=9e3c351a-381e-49ad-87e1-07a3a643c33c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted UpgradeStatus: Upgraded to focal on 2021-09-03 (26 days ago) dmi.bios.date: 01/23/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 1.60 dmi.board.name: SB600 dmi.board.vendor: ATI dmi.board.version: Rev 1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr1.60:bd01/23/2008:svnTOSHIBA:pnSatelliteProA210:pvrPSAFHU-010002:rvnATI:rnSB600:rvrRev1:cvnAMD:ct1:cvrNone: dmi.product.name: Satellite Pro A210 dmi.product.version: PSAFHU-010002 dmi.sys.vendor: TOSHIBA ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-package 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/1945475 Title: package linux-modules-extra-5.4.0-88-generic (not installed) failed to install/upgrade: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg- new': Operation not permitted Status in linux package in Ubuntu: Confirmed Bug description: broken install ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-88-generic (not installed) ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dianekerivan 1609 F pulseaudio CasperMD5CheckResult: skip Date: Wed Sep 29 09:14:01 2021 DuplicateSignature: package:linux-modules-extra-5.4.0-88-generic:(not installed) Unpacking linux-modules-5.4.0-88-generic (5.4.0-88.99) ... dpkg: error processing archive /tmp/apt-dpkg-install-7eiv6l/15-linux-modules-5.4.0-88-generic_5.4.0-88.99_amd64.deb (--unpack): unable to create new file '/var/lib/dpkg/info/linux-modules-5.4.0-88-generic.list-new': Operation not permitted ErrorMessage: unable to open '/lib/modules/5.4.0-88-generic/kernel/drivers/net/wireless/broadcom/b43legacy/b43legacy.ko.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-01-06 (265 days ago) InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 (20200806.1) MachineType: TOSHIBA Satellite Pro A210 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=9e3c351a-381e-49ad-87e1-07a3a643c33c ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26.13 RfKill: 0: phy0: Wireless LAN
[Kernel-packages] [Bug 1942181] Re: Add support for AlderLake CPUs
Exercised hirsute thermald 2.4.3-1ubuntu3 for 3 hours - no observable regression under varying CPU loads that cycled the temperature between 65 and TjMax. Looks good to me. ** Tags removed: verification-needed-hirsute ** Tags added: verification-done-hirsute ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1942181 Title: Add support for AlderLake CPUs Status in OEM Priority Project: Fix Released Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Released Status in thermald source package in Hirsute: Fix Committed Status in thermald source package in Impish: Fix Released Bug description: [Impact] * Support thermald on AlderLake CPUs. [Test Plan] * Use a machine with a AlderLake CPUs * systemctl status thermald * Status of thermald should be `running` [Where problems could occur] * This change is to support Jasper Lake in thermald, which won't impact other hardware because the changes match on the CPU model ID. [Other Info] Supported added with: * https://github.com/intel/thermal_daemon/commit/ffb226c62d3bc052f47970be9802254e48799bf4 * https://github.com/intel/thermal_daemon/commit/d0c9e7fb5aea85b84841eba927feb8767765fda2 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942181/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1943794] Re: audio device [8086:51c8] subsystem [1028:0af3] not supported
pushed staging kernel version 5.14.0-9004.4+staging.21 that includes patches from the attachments to https://launchpad.net/~vicamo/+archive/ubuntu/linux-staging and staging linux-firmware version 1.187.17+staging.23 to https://launchpad.net/~vicamo/+archive/ubuntu/linux-firmware-staging . ** Attachment added: "five_products(updated_Tributo).zip" https://bugs.launchpad.net/bugs/1943794/+attachment/5529094/+files/five_products%28updated_Tributo%29.zip -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1943794 Title: audio device [8086:51c8] subsystem [1028:0af3] not supported Status in HWE Next: New Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.14 source package in Focal: Incomplete Status in linux-oem-5.14 source package in Impish: Invalid Bug description: No workable audio output device in Settings. :00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:51c8] Subsystem: Dell Device [1028:0af3] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit+ Address: fee00578 Data: Kernel driver in use: sof-audio-pci-intel-tgl Kernel modules: snd_hda_intel, snd_sof_pci_intel_tgl 2552 [ 6.488289] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if info 0x040100 2553 [ 6.488313] sof-audio-pci-intel-tgl :00:1f.3: SoundWire enabled on CannonLake+ platform, using SOF driver 2554 [ 6.488345] sof-audio-pci-intel-tgl :00:1f.3: enabling device ( -> 0002) 2555 [ 6.488572] sof-audio-pci-intel-tgl :00:1f.3: DSP detected with PCI class/subclass/prog-if 0x040100 2556 [ 6.488680] sof-audio-pci-intel-tgl :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) 2557 [ 6.495058] sof-audio-pci-intel-tgl :00:1f.3: use msi interrupt mode 2558 [ 6.512802] sof-audio-pci-intel-tgl :00:1f.3: hda codecs found, mask 4 2559 [ 6.513510] sof-audio-pci-intel-tgl :00:1f.3: Direct firmware load for intel/sof/sof-adl.ri failed with error -2 2560 [ 6.513518] sof-audio-pci-intel-tgl :00:1f.3: error: request firmware intel/sof/sof-adl.ri failed err: -2 2561 [ 6.513519] sof-audio-pci-intel-tgl :00:1f.3: you may need to download the firmware from https://github.com/thesofproject/sof-bin/ 2562 [ 6.513521] sof-audio-pci-intel-tgl :00:1f.3: error: failed to load DSP firmware -2 2563 [ 6.514237] sof-audio-pci-intel-tgl :00:1f.3: error: sof_probe_work failed err: -2 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1943794/+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 1945464] [NEW] MEI (Intel Management Engine Interface) for sprint 2
Public bug reported: Tracking bug, please don't triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: Confirmed ** Tags: intel oem-priority originate-from-1929894 ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Anthony Wong (anthonywong) ** Tags added: intel oem-priority originate-from-1929894 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945464 Title: MEI (Intel Management Engine Interface) for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Confirmed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945464/+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 1945462] [NEW] EHL graphics support for sprint 2
Public bug reported: Tracking bug, please don't triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Alex Hung (alexhung) Status: Confirmed ** Tags: intel oem-priority originate-from-1883616 ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Alex Hung (alexhung) ** Tags added: intel oem-priority originate-from-1883616 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945462 Title: EHL graphics support for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Confirmed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945462/+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 1945461] [NEW] Integrated TSN controller for sprint 2
Public bug reported: Tracking bug, please don't triage. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-intel-5.13 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Assignee: Anthony Wong (anthonywong) Status: Confirmed ** Tags: intel oem-priority originate-from-1943687 ** Also affects: linux-intel-5.13 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-intel-5.13 (Ubuntu) Status: New => Invalid ** Changed in: linux-intel-5.13 (Ubuntu Focal) Status: New => Confirmed ** Changed in: linux-intel-5.13 (Ubuntu Focal) Assignee: (unassigned) => Anthony Wong (anthonywong) ** Tags added: intel oem-priority originate-from-1943687 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1945461 Title: Integrated TSN controller for sprint 2 Status in HWE Next: New Status in linux-intel-5.13 package in Ubuntu: Invalid Status in linux-intel-5.13 source package in Focal: Confirmed Bug description: Tracking bug, please don't triage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1945461/+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 1945451] 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/1945451 Title: linux-image-5.4.0-8x kernels on Ubuntu 20.04.3 LTS cause incorrect disk enumeration Status in linux package in Ubuntu: Confirmed Bug description: My system had this disk configuration running 20.04.3 LTS server (fresh install, not upgrade) without issue: 1 SATA SSD ext4 on internal 6Gb SATA port was /dev/sda with 20.04.3 LTS server OS installed. 1 SATA disk ext4 on internal 6Gb SATA port was /dev/sdb 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode was /dev/sd[cdefghij] 2 SATA disks (mdraid1) on internal 3Gb SATA ports was /dev/sd[kl] apt upgrade from 5.4.0-7x kernel booting any current linux-image-5.4.0-8x kernel now looks like this: 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode are /dev/sd[abcdefgh] 1 SATA SSD ext4 on internal 6Gb SATA port is now /dev/sdi with 20.04.3 OS installed. 1 SATA disk ext4 on internal 6Gb SATA port now /dev/sdj with 20.04.3 OS installed. 2 SATA disks (mdraid1) on internal 3Gb SATA ports is /dev/sd[kl] The system boots, but any utils e.g. smartd, hdparm etc. referencing /dev/sda are now fubared. Booting any 5.4.0-7x kernel enumerates the disks correctly. Booting any 5.4.0-8x kernel enumerates the disks incorrectly as described above. Booting latest Mainline kernel 5.15.0-051500rc3-generic enumerates the disks correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.86.90 ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 20:36 seq crw-rw 1 root audio 116, 33 Sep 29 20:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Sep 29 20:40:44 2021 InstallationDate: Installed on 2021-03-27 (186 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=f84368a6-a484-40ef-aacf-d7cd3ce2ecc2 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-86-generic N/A linux-backports-modules-5.4.0-86-generic N/A linux-firmware1.187.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945451/+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 1944397] Re: HDMI does not display anything with Impish RPi desktop image
On Hirsute 5.11 the display comes up but the kernel is not happy: $ sudo dmesg | grep -P 'firmware|WARN' [0.124340] raspberrypi-firmware soc:firmware: Attached to firmware from 2021-02-25T12:10:40, variant start [0.128359] raspberrypi-firmware soc:firmware: Firmware hash is 564e5f9b852b23a330b1764bcf0b2d022a20afd0 [ 17.517350] raspberrypi-firmware soc:firmware: Request 0x00030066 returned status 0x8001 [ 17.530301] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22 [ 17.674616] raspberrypi-firmware soc:firmware: Request 0x00030066 returned status 0x8001 [ 17.685979] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22 [ 17.864574] raspberrypi-firmware soc:firmware: Request 0x00030066 returned status 0x8001 [ 17.873532] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22 [ 20.031174] raspberrypi-firmware soc:firmware: Request 0x00030066 returned status 0x8001 [ 20.040515] vc4-drm gpu: [drm] Couldn't stop firmware display driver: -22 [ 20.127052] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x390/0x49c [vc4] [ 20.493554] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] [ 20.803013] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x388/0x49c [vc4] [ 21.113145] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] [ 21.422741] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x380/0x49c [vc4] [ 21.731941] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] [ 22.041559] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_disable+0x424/0x49c [vc4] [ 22.351113] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] [ 22.662902] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc4_hdmi_encoder_post_crtc_powerdown+0x178/0x1c0 [vc4] [ 22.978912] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x198/0x220 [vc4] [ 23.300587] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:445 vc5_hdmi_phy_disable+0x190/0x220 [vc4] [ 23.619497] WARNING: CPU: 1 PID: 103 at drivers/gpu/drm/vc4/vc4_hdmi_regs.h:417 vc4_hdmi_read+0xd8/0x140 [vc4] ** Also affects: linux-firmware-raspi2 (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Assignee: (unassigned) => Juerg Haefliger (juergh) -- 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/1944397 Title: HDMI does not display anything with Impish RPi desktop image Status in linux-firmware-raspi2 package in Ubuntu: New Status in linux-raspi package in Ubuntu: Fix Committed Status in linux-firmware-raspi2 source package in Hirsute: New Status in linux-raspi source package in Hirsute: New Status in linux-firmware-raspi2 source package in Impish: New Status in linux-raspi source package in Impish: Fix Committed Bug description: Workaround -- With media which you will boot off of change the line dtoverlay=vc4-kms-v3d to dtoverlay=vc4-fkms-v3d in /system-boot/config.txt Original Description Have a HDMI display w/o audio hooked up to this RPI4B. With the latest kernel update the screen does not turn on due to this. ProblemType: BugDistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-1007-raspi 5.13.0-1007.8 ProcVersionSignature: Ubuntu 5.13.0-1007.8-raspi 5.13.13 Uname: Linux 5.13.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu69 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Sep 20 20:56:14 2021 ImageMediaBuild: 20210421 ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=vt100 XDG_RUNTIME_DIR= PATH=(custom, user)SourcePackage: linux-raspi UpgradeStatus: Upgraded to impish on 2021-08-17 (34 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1944397/+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 1945451] Re: linux-image-5.4.0-8x kernels on Ubuntu 20.04.3 LTS cause incorrect disk enumeration
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1945451 Title: linux-image-5.4.0-8x kernels on Ubuntu 20.04.3 LTS cause incorrect disk enumeration Status in linux package in Ubuntu: New Bug description: My system had this disk configuration running 20.04.3 LTS server (fresh install, not upgrade) without issue: 1 SATA SSD ext4 on internal 6Gb SATA port was /dev/sda with 20.04.3 LTS server OS installed. 1 SATA disk ext4 on internal 6Gb SATA port was /dev/sdb 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode was /dev/sd[cdefghij] 2 SATA disks (mdraid1) on internal 3Gb SATA ports was /dev/sd[kl] apt upgrade from 5.4.0-7x kernel booting any current linux-image-5.4.0-8x kernel now looks like this: 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode are /dev/sd[abcdefgh] 1 SATA SSD ext4 on internal 6Gb SATA port is now /dev/sdi with 20.04.3 OS installed. 1 SATA disk ext4 on internal 6Gb SATA port now /dev/sdj with 20.04.3 OS installed. 2 SATA disks (mdraid1) on internal 3Gb SATA ports is /dev/sd[kl] The system boots, but any utils e.g. smartd, hdparm etc. referencing /dev/sda are now fubared. Booting any 5.4.0-7x kernel enumerates the disks correctly. Booting any 5.4.0-8x kernel enumerates the disks incorrectly as described above. Booting latest Mainline kernel 5.15.0-051500rc3-generic enumerates the disks correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.86.90 ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 20:36 seq crw-rw 1 root audio 116, 33 Sep 29 20:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Sep 29 20:40:44 2021 InstallationDate: Installed on 2021-03-27 (186 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=f84368a6-a484-40ef-aacf-d7cd3ce2ecc2 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-86-generic N/A linux-backports-modules-5.4.0-86-generic N/A linux-firmware1.187.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1945451/+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 1945451] [NEW] linux-image-5.4.0-8x kernels on Ubuntu 20.04.3 LTS cause incorrect disk enumeration
You have been subscribed to a public bug: My system had this disk configuration running 20.04.3 LTS server (fresh install, not upgrade) without issue: 1 SATA SSD ext4 on internal 6Gb SATA port was /dev/sda with 20.04.3 LTS server OS installed. 1 SATA disk ext4 on internal 6Gb SATA port was /dev/sdb 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode was /dev/sd[cdefghij] 2 SATA disks (mdraid1) on internal 3Gb SATA ports was /dev/sd[kl] apt upgrade from 5.4.0-7x kernel booting any current linux-image-5.4.0-8x kernel now looks like this: 8 SATA disks ext4 on LSI Megaraid 9240-8i in IT mode are /dev/sd[abcdefgh] 1 SATA SSD ext4 on internal 6Gb SATA port is now /dev/sdi with 20.04.3 OS installed. 1 SATA disk ext4 on internal 6Gb SATA port now /dev/sdj with 20.04.3 OS installed. 2 SATA disks (mdraid1) on internal 3Gb SATA ports is /dev/sd[kl] The system boots, but any utils e.g. smartd, hdparm etc. referencing /dev/sda are now fubared. Booting any 5.4.0-7x kernel enumerates the disks correctly. Booting any 5.4.0-8x kernel enumerates the disks incorrectly as described above. Booting latest Mainline kernel 5.15.0-051500rc3-generic enumerates the disks correctly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-generic 5.4.0.86.90 ProcVersionSignature: Ubuntu 5.4.0-86.97-generic 5.4.133 Uname: Linux 5.4.0-86-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Sep 29 20:36 seq crw-rw 1 root audio 116, 33 Sep 29 20:36 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass Date: Wed Sep 29 20:40:44 2021 InstallationDate: Installed on 2021-03-27 (186 days ago) InstallationMedia: Ubuntu-Server 20.04.2 LTS "Focal Fossa" - Release amd64 (20210201.2) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: System manufacturer System Product Name PciMultimedia: ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-86-generic root=UUID=f84368a6-a484-40ef-aacf-d7cd3ce2ecc2 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-86-generic N/A linux-backports-modules-5.4.0-86-generic N/A linux-firmware1.187.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/13/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd08/13/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-V:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- linux-image-5.4.0-8x kernels on Ubuntu 20.04.3 LTS cause incorrect disk enumeration https://bugs.launchpad.net/bugs/1945451 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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
With manually placing firmware in /lib/firmware (since SRU not started for that) and using 5.14 kernel confirmed that mesa looks good. Since we don't have linux-firmware SRU package yet and they are combined on this bug report I will not add "verification-done-focal". # glxinfo | grep "OpenGL render" -i OpenGL renderer string: AMD YELLOW_CARP (DRM 3.42.0, 5.14.0, LLVM 12.0.0) # dpkg -l | grep 21.0.3-0ubuntu0.3 ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945227 Title: drm/amdgpu: Add support for Yellow Carp Status in linux-firmware package in Ubuntu: New Status in mesa package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Status in mesa source package in Focal: Fix Committed Bug description: [Impact] New hardware support for AMD's Yellow Carp need five commits backported to mesa and new firmware. This is only needed on focal, skipping hirsute/impish (no kernel support there). [Test plan] Install updates, boot a YC machine and check that the desktop has full hardware acceleration. [Where problems could occur] The firmware is new, so it will simply add new files to l-f without any impact on others. Mesa adds five commits in total, and while some affect other chips, they mostly fix hw bugs or add a helper and such, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1939177] Re: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken
Hello all, Hope everyone is well and safe. This is a plea to push along the resolution of this bug. I'm heavily invested in zfs and this has been a huge problem for me. Just like TimK I'm a sanoid/syncoid user and have seen the zfs recv problem. Changing syncoid's perl to not use "-s" worked for me. But thats not been an end to my problems. Originally I thought I had "lost" my main 10TB zpool for e.g hardware reasons, but its not proved simple as that. I can import and read from the zpool but see zfs timeouts regularly in syslog. If I try to write to this pool it hangs. zfs list hangs as well. Eventually zfs seems completely "stopped" and I have to reboot. Assuming my "tank" was trashed, I had been using my (syncoid) backups to reestablish my files in a new zfs pool on new hardware. Which worked fine (+1 syncoid). I've been trying to reestablish backups for my new pool/hardware this morning and find whereas I can zfs send a 4.8GB snapshot ok, I can not send a 7.2GB (or larger) snapshots - I get the rather anodyne message "Input/output error". I have also seen hangs when trying to zfs destroy snapshots on one of my other pools. Whether the hanging destroy is the root cause or just a casualty of other zfs stuff going on, I've no information. I realise that relating the generally instability of my system is pretty vague: its proving hard to pick apart the problems and demonstrate repeatable effects. So I'm eager to try the proposed fix but, as Jason has said, there is no amd64 version yet in focal-proposed. Can I encourage you to make the fix available please? Really appreciate everybody's effort. Thanks in advance. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939177 Title: Ubuntu 20.04.2 LTS kernel 5.11.0-25 zfs send | receive broken Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Focal: Fix Committed Bug description: == SRU Justification Focal == [Impact] https://github.com/openzfs/zfs/issues/12462 Ubuntu 20.04.2 LTS Kernel: 5.11.0-25-generic #27~20.04.1-Ubuntu zfs-0.8.3-1ubuntu12.12 zfs-kmod-2.0.2-1ubuntu5 Trying to run zfs send | receive and getting an error: # zfs send 'rpool/home'@'autosnap_2020-08-01_00:59:01_monthly' | zfs receive -s -F 'nas/rpool_backup/home' cannot receive: failed to read from stream cannot receive new filesystem stream: dataset does not exist This used to work before the recent Ubuntu kernel update from 5.8 to 5.11 Kernel 5.8 came with zfs-kmod-0.8.4-1ubuntu11.2 Ubuntu updates that broke it: Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux- image-generic-hwe-20.04:amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10), linux-generic-hwe-20.04 :amd64 (5.8.0.63.71~20.04.45, 5.11.0.25.27~20.04.10) Sending the zfs send part to a file works, but then sending the file to zfs receive also fails. The dump file size seems reasonable but the contents may not be correct. [Test Plan] 1. create test pool and backup pool sudo zpool create pool /dev/vdb1 sudo zpool create backup /dev/vdc1 2. populate pool with some files and create some snapshots sudo zfs snapshot pool@now1 create some more files etc, make another snapshot sudo zfs snapshot pool@now2 3. perform send/recv using -s option: sudo zfs send pool@now1 | sudo zfs receive -vFs backup sudo zfs send -i pool@now1 pool@now2 | sudo zfs receive -vFs backup Without the fix, the -s option on the receive fails. With the fix it works fine. Test with focal 5.4 and 5.11 kernel to exercise 0.8.x and 2.x kernel ZFS drivers. [Where problems could occur] The main fix nullifies the deprecated action_handle option so that it's not checked, this allows 0.8.x userspace it to be forwardly compatible with 2.x kernel ZFS and also since it is deprecated in 0.8.x it makes not difference to the 0.8.x kernel ZFS driver. Thus the risk with patch action_handle is very small. Included in the fix is a send/recv upstream bug fix 4910-Fix-EIO-after-resuming-receive-of-new-dataset-over-a.patch that makes send/recv more resilient by making zfs receive to always unmount and remount the destination, regardless of whether the stream is a new stream or a resumed stream. The change is upstream for ~10 months and has minimal impact on current recv functionality. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177/+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 1945351] Re: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011
** Changed in: linux-oracle (Ubuntu Hirsute) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1945351 Title: hirsute linux-oracle: Enable CONFIG_SERIAL_AMBA_PL011 Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle source package in Hirsute: Fix Committed Bug description: [Impact] No support for arm64 console currently [Fix] Add arm64 console support [Test] Confirm that it boots on desired arm64 hardware, as well as VMs, and produces console output. [Regression Potential] This was never working on arm64 so there should be no risk of regression. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1945351/+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 1935850] Re: Dell XPS 17 (9710) PCI/internal sound card not detected
Precision 5760 - kernel 5.11.0-37-generic. I cna confirm the audio is working correctly. 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/1935850 Title: Dell XPS 17 (9710) PCI/internal sound card not detected Status in linux package in Ubuntu: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux source package in Impish: Fix Released Bug description: This patch is for soundwire audio, and only ubuntu 5.11-generic and later kernels support soundwire audio driver, so this patch is not sent to groovy and focal kernels. For oem-5.10 and oem-5.13 kernels, since this bug is not from OEM project, it is not urgent to merge this patch to OEM kenrels, after the patch is in the hirsute and impish kernels, the oem kernels will have this patch when syncing with generic kernels. [Impact] On the Dell XPS 17 (9710) machine, the audio card is not detected when booting hirsute or impish kernels. So the audio doesn't work on this machine with ubuntu linux 21.04 or 21.10. [Fix] Backport a upstream patch, this will set the correct codec config for this machine: rt711 for headset, dual rt1308 for spks and rt715 for internal mic. [Test] Booting up with the patched kernel, the audio card is detected, test internal speaker and internal mic, all work well, plug a headset, the headphone and external mic work well too. [Where problems could occur] This change only applis to the Dell machines with the DMI_PRODUCT_SKU equals to "0A5D", if this could introduce the regression, it will make the audio (speaker, internal mic and headset) can't work anymore on the Dell machine with that PRODUCT_SKU, but this possibility is very low, and we tested the patch on the machine, so far no regression is found. No audio/mic from internal speakers/build in microphone running Ubuntu 20.04, 20.10 or 21.04 . Can connect via USB headset and audio will work. Tried suggestions from Dell XPS 17 (9700) but this is the new model and fixes do not work. Currently running 21.04 with proposed. Have tried hirsute-proposed (5.11.0-24-generic) with no luck. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 ProcVersionSignature: Ubuntu 5.11.0-24.25-generic 5.11.22 Uname: Linux 5.11.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mblack 1698 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jul 12 11:21:27 2021 InstallationDate: Installed on 2021-07-07 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Title: PCI/internal sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/2021 dmi.bios.release: 1.2 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.0 dmi.board.name: 012MMP dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.0:bd06/15/2021:br1.2:svnDellInc.:pnXPS179710:pvr:rvnDellInc.:rn012MMP:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9710 dmi.product.sku: 0A5D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1935850/+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 1944417] Re: Add support for 5.14
I'll add it in for hirsute though. I'll use the bug number. ** Also affects: zfs-linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Hirsute) Importance: Undecided => Low ** Changed in: zfs-linux (Ubuntu Hirsute) Assignee: (unassigned) => Colin Ian King (colin-king) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944417 Title: Add support for 5.14 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Focal: Invalid Status in zfs-linux source package in Hirsute: New Bug description: zfs-linux needs at least these two compat changes in order to build against 5.14 kernel like oem-5.14 in focal: https://github.com/openzfs/zfs/commit/1b06b03a7be88f4565c2c3114b8d3f2dc9f9408a https://github.com/openzfs/zfs/commit/1c24bf966c373009f2be77438e8696aabf50a7e7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+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 1945444] [NEW] Touchpad randomly freezes
Public bug reported: We have 5 laptops, all brand new Huawei Matebook 14 2021. They have no hardware problem (on Windows it is ok). On Ubuntu Linux, the Elantech touchpad regularly freezes for some seconds, with one of the CPU at 100%. The problem occurs both with kernel 5.4, and also with the new 5.11 kernel. I also tried the kernel 5.14 (with mainline) and the problem was not solved, so I rolled back to 5.11. I see in dmesg output: [ 3335.316965] i2c_designware i2c_designware.0: controller timed out [ 3335.568349] input: ELAN2605:00 04F3:3163 Mouse as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2605:00/0018:04F3:3163.0001/input/input104 [ 3335.568407] input: ELAN2605:00 04F3:3163 Touchpad as /devices/pci:00/:00:15.0/i2c_designware.0/i2c-1/i2c-ELAN2605:00/0018:04F3:3163.0001/input/input106 [ 3335.568444] hid-multitouch 0018:04F3:3163.0001: input,hidraw0: I2C HID v1.00 Mouse [ELAN2605:00 04F3:3163] on i2c-ELAN2605:00 [ 3335.685062] input: 06CB19AB:00 06CB:1A1A as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-2/i2c-06CB19AB:00/0018:06CB:1A1A.0002/input/input107 [ 3335.685154] hid-multitouch 0018:06CB:1A1A.0002: input,hidraw1: I2C HID v1.00 Device [06CB19AB:00 06CB:1A1A] on i2c-06CB19AB:00 [ 3360.880952] i2c_designware i2c_designware.0: controller timed out [ 3548.917328] watchdog: BUG: soft lockup - CPU#3 stuck for 23s! [swapper/3:0] [ 3548.917333] Modules linked in: hid_multitouch xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc vboxnetadp(O) vboxnetflt(O) vboxdrv(O) cmac algif_hash algif_skcipher af_alg aufs overlay bnep snd_hda_codec_hdmi hid_logitech_hidpp hid_logitech_dj btusb uvcvideo btrtl btbcm videobuf2_vmalloc btintel videobuf2_memops bluetooth videobuf2_v4l2 videobuf2_common videodev ecdh_generic mc usbhid ecc snd_sof_pci snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof snd_sof_xtensa_dsp snd_soc_hdac_hda snd_hda_ext_core snd_soc_acpi_intel_match snd_soc_acpi snd_hda_intel snd_intel_dspcfg soundwire_intel soundwire_generic_allocation soundwire_cadence joydev snd_hda_codec snd_hda_core nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hwdep soundwire_bus snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine [ 3548.917395] x86_pkg_temp_thermal intel_powerclamp snd_pcm coretemp snd_seq_midi kvm_intel snd_seq_midi_event snd_rawmidi i915 snd_seq kvm iwlmvm crct10dif_pclmul ghash_clmulni_intel snd_seq_device aesni_intel mac80211 drm_kms_helper snd_timer crypto_simd cec cryptd rc_core glue_helper i2c_algo_bit libarc4 snd huawei_wmi processor_thermal_device intel_cstate ledtrig_audio fb_sys_fops mei_me processor_thermal_rfim sparse_keymap wmi_bmof syscopyarea processor_thermal_mbox sysfillrect processor_thermal_rapl intel_rapl_common soundcore sysimgblt mei intel_soc_dts_iosf iwlwifi input_leds serio_raw efi_pstore cfg80211 mac_hid int3400_thermal int3403_thermal acpi_thermal_rel int340x_thermal_zone acpi_pad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul nvme i2c_i801 i2c_smbus nvme_core intel_lpss_pci intel_lpss idma64 xhci_pci virt_dma i2c_hid xhci_pci_renesas wmi hid video pinctrl_tigerlake [last unloaded: hid_multitouch] [ 3548.917449] CPU: 3 PID: 0 Comm: swapper/3 Tainted: G O 5.11.0-36-generic #40~20.04.1-Ubuntu [ 3548.917452] Hardware name: HUAWEI KLVD-WXX9/KLVD-WXX9-PCB-B2, BIOS 3.02 07/31/2021 [ 3548.917453] RIP: 0010:_raw_spin_unlock_irqrestore+0x15/0x20 [ 3548.917458] Code: ff 7f 5b 44 89 f0 41 5c 41 5d 41 5e 41 5f 5d c3 cc cc cc cc cc 0f 1f 44 00 00 55 48 89 e5 c6 07 00 0f 1f 40 00 48 89 f7 57 9d <0f> 1f 44 00 00 5d c3 0f 1f 40 00 0f 1f 44 00 00 55 49 89 f8 b8 00 [ 3548.917459] RSP: 0018:bc53801e8e30 EFLAGS: 0287 [ 3548.917462] RAX: 001d462c RBX: 9fab00a39ec0 RCX: 000f4240 [ 3548.917463] RDX: 00701f67 RSI: 0287 RDI: 0287 [ 3548.917464] RBP: bc53801e8e30 R08: 0003 R09: 03d8 [ 3548.917465] R10: 9fab00a39f90 R11: 9fae708ec3f0 R12: 9fae708ec2c0 [ 3548.917465] R13: R14: 0287 R15: 9fab00a3aabc [ 3548.917467] FS: () GS:9fae708c() knlGS: [ 3548.917468] CS: 0010 DS: ES: CR0: 80050033 [ 3548.917469] CR2: 280406941000 CR3: 00011d010003 CR4: 00770ee0 [ 3548.917470] PKRU: 5554 [ 3548.917470] Call Trace: [ 3548.917471] [ 3548.917475] try_to_wake_up+0x432/0x5d0 [ 3548.917479] ? __next_timer_interrupt+0x110/0x110 [ 3548.917482] wake_up_process+0x15/0x20 [ 3548.917484] process_timeout+0x12/0x20 [ 3548.917485] call_timer_fn+0x2e/0x100 [ 3548.917487] __run_timers.part.0+0x1e0/0x250 [ 3548.917489] run_timer_softirq+0x2a/0x50 [ 3548.917491]
[Kernel-packages] [Bug 1931841] Re: generic arm64 kernel can not boot initrdless and there is no -kvm kernel
** 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/1931841 Title: generic arm64 kernel can not boot initrdless and there is no -kvm kernel Status in linux package in Ubuntu: Confirmed Bug description: The CPC team wants to build minimal arm64 images. Those images should boot initrdless (similar to the amd64 images where the -kvm kernel is used). But booting an initrdless image (build with livecd-rootfs) does fail with: $ sudo qemu-system-aarch64 -m 2G -M virt -cpu max -bios /usr/share/qemu-efi-aarch64/QEMU_EFI.fd -drive if=none,format=qcow2,file=livecd.ubuntu-cpc.img,id=hd0 -device virtio- blk-device,drive=hd0 -device e1000,netdev=net0 -netdev user,id=net0,hostfwd=tcp:127.0.0.1:-:22 -nographic [snipped] [0.945928] VFS: Cannot open root device "PARTUUID=15058d73-bec1-4c7d-9cd7-f0f73f3ec694" or unknown-block(0,0): error -6 [0.946117] Please append a correct "root=" boot option; here are the available partitions: [0.947611] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [0.948139] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.4.0-74-generic #83-Ubuntu [0.948237] Hardware name: QEMU QEMU Virtual Machine, BIOS 0.0.0 02/06/2015 [0.948453] Call trace: [0.948736] dump_backtrace+0x0/0x190 [0.948864] show_stack+0x28/0x38 [0.948918] dump_stack+0xb4/0x10c [0.948974] panic+0x150/0x364 [0.949027] mount_block_root+0x248/0x304 [0.949090] mount_root+0x48/0x50 [0.949145] prepare_namespace+0x13c/0x1bc [0.949205] kernel_init_freeable+0x270/0x2c4 [0.949274] kernel_init+0x1c/0x114 [0.949336] ret_from_fork+0x10/0x18 [0.949913] Kernel Offset: disabled [0.950175] CPU features: 0x0952,20e0a230 [0.950251] Memory Limit: none [0.950595] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- The reason is, that the the virtio drivers are modules (CONFIG_VIRTIO_BLK=m) but for initrdless boot, they need to be compiled into the kernel. Expected behavior: Booting an arm64 image without an initrd does work in a virtualized environment similar to an amd64 image (that uses the -kvm kernel) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931841/+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 1945438] Re: Update ADL-P dmc firmware
** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu) Status: New => Invalid ** Description changed: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test - that DC6 power state works fine. + that DC6 power state works without issues. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945438 Title: Update ADL-P dmc firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works without issues. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+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 1945438] Re: Update ADL-P dmc firmware
included in 1.201 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945438 Title: Update ADL-P dmc firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Bug description: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works fine. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+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 1945438] [NEW] Update ADL-P dmc firmware
Public bug reported: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works fine. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Assignee: Timo Aaltonen (tjaalton) Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Timo Aaltonen (tjaalton) ** Changed in: linux-firmware (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1945438 Title: Update ADL-P dmc firmware Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: New Bug description: [Impact] It's reported that 2.12 fixes some issues with DC6 power saving state on ADL-P [Test case] With a suitable kernel (oem-5.14 which knows about this fw version) test that DC6 power state works fine. [Where things could go wrong] Using this version needs kernel support, so it does not affect other systems than Alder Lake P. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945438/+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 1944417] Re: Add support for 5.14
** Changed in: zfs-linux (Ubuntu Focal) Status: In Progress => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1944417 Title: Add support for 5.14 Status in zfs-linux package in Ubuntu: New Status in zfs-linux source package in Focal: Invalid Bug description: zfs-linux needs at least these two compat changes in order to build against 5.14 kernel like oem-5.14 in focal: https://github.com/openzfs/zfs/commit/1b06b03a7be88f4565c2c3114b8d3f2dc9f9408a https://github.com/openzfs/zfs/commit/1c24bf966c373009f2be77438e8696aabf50a7e7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1944417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.11.0.1018.19)
All autopkgtests for the newly accepted linux-meta-kvm (5.11.0.1018.19) for hirsute have finished running. The following regressions have been reported in tests triggered by the package: lttng-modules/2.12.5-1ubuntu2~21.04.1 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu8 (amd64) oss4/4.2-build2010-5ubuntu8 (amd64) systemd/247.3-3ubuntu3.6 (amd64) rtl8821ce/5.5.2.1-0ubuntu6 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu14 (amd64) v4l2loopback/0.12.5-1ubuntu1 (amd64) backport-iwlwifi-dkms/8613-0ubuntu2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/hirsute/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1911055] Re: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nvidia-graphics-drivers-470 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1911055 Title: [modeset][nvidia] suspend/resume broken in nvidia-460 : Display engine push buffer channel allocation failed Status in nvidia-graphics-drivers-460 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-470 package in Ubuntu: Confirmed Bug description: After a recent update to nvidia-460, suspend then resume results in a black screen, then a hang for around 120 seconds, and then the text: nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer dmesg shows: [ 188.352670] ACPI: Waking up from system sleep state S3 ... [ 309.142164] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 309.142319] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.142165] nvidia-modeset: ERROR: GPU:0: Display engine push buffer channel allocation failed: 0x65 (Call timed out [NV_ERR_TIMEOUT]) [ 313.142348] nvidia-modeset: ERROR: GPU:0: Failed to allocate display engine core DMA push buffer [ 313.151885] acpi LNXPOWER:08: Turning OFF [ 313.151898] acpi LNXPOWER:04: Turning OFF [ 313.152351] acpi LNXPOWER:03: Turning OFF [ 313.153064] acpi LNXPOWER:02: Turning OFF ... [ 325.010192] nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DELL 2209WA (HDMI-0) [ 325.010577] BUG: kernel NULL pointer dereference, address: 0050 [ 325.010579] #PF: supervisor read access in kernel mode [ 325.010580] #PF: error_code(0x) - not-present page [ 325.010580] PGD 0 P4D 0 [ 325.010582] Oops: [#1] SMP PTI [ 325.010583] CPU: 9 PID: 2247 Comm: Xorg Tainted: P O 5.4.0-60-generic #67-Ubuntu [ 325.010584] Hardware name: Razer Blade/DANA_MB, BIOS 01.01 08/31/2018 [ 325.010595] RIP: 0010:_nv000112kms+0xd/0x30 [nvidia_modeset] [ 325.010596] Code: 16 00 74 06 83 7e 0c 02 77 03 31 c0 c3 c7 46 0c 01 00 00 00 b8 01 00 00 00 c3 0f 1f 00 0f b7 46 04 0f b7 56 08 39 d0 0f 47 c2 <3b> 47 18 77 06 83 7e 10 02 77 08 31 c0 c3 0f 1f 44 00 00 c7 46 10 [ 325.010597] RSP: 0018:b89542e5b8a8 EFLAGS: 00010246 [ 325.010598] RAX: 0280 RBX: 0038 RCX: 03ff [ 325.010598] RDX: 0280 RSI: b89542e5bba0 RDI: 0038 [ 325.010599] RBP: b89542e5b9c8 R08: R09: c379e440 [ 325.010600] R10: R11: R12: b89542e5b948 [ 325.010600] R13: b89542e5b948 R14: b89542e5b930 R15: c3a50e60 [ 325.010601] FS: 7feb4c09ea80() GS:8e46ada4() knlGS: [ 325.010602] CS: 0010 DS: ES: CR0: 80050033 [ 325.010602] CR2: 0050 CR3: 0004772e2006 CR4: 003606e0 [ 325.010603] Call Trace: [ 325.010610] ? _nv002768kms+0x96/0xd0 [nvidia_modeset] [ 325.010616] ? _nv002328kms+0xb5/0x110 [nvidia_modeset] [ 325.010624] ? _nv000742kms+0x168/0x370 [nvidia_modeset] [ 325.010823] ? _nv036002rm+0x62/0x70 [nvidia] [ 325.010910] ? os_get_current_tick+0x2c/0x50 [nvidia] [ 325.010921] ? _nv002771kms+0x433/0x600 [nvidia_modeset] [ 325.010928] ? _nv002771kms+0x3fc/0x600 [nvidia_modeset] [ 325.010930] ? __schedule+0x2eb/0x740 [ 325.010935] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010939] ? nvkms_alloc+0x6a/0xa0 [nvidia_modeset] [ 325.010944] ? _nv000742kms+0x40/0x40 [nvidia_modeset] [ 325.010948] ? _nv000744kms+0x2a/0x40 [nvidia_modeset] [ 325.010952] ? nvKmsIoctl+0x96/0x1d0 [nvidia_modeset] [ 325.010957] ? nvkms_ioctl_common+0x42/0x80 [nvidia_modeset] [ 325.010961] ? nvkms_ioctl+0xc4/0x100 [nvidia_modeset] [ 325.011016] ? nvidia_frontend_unlocked_ioctl+0x3b/0x50 [nvidia] [ 325.011017] ? do_vfs_ioctl+0x407/0x670 [ 325.011019] ? do_user_addr_fault+0x216/0x450 [ 325.011020] ? ksys_ioctl+0x67/0x90 [ 325.011021] ? __x64_sys_ioctl+0x1a/0x20 [ 325.011023] ? do_syscall_64+0x57/0x190 [ 325.011024] ? entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 325.011025] Modules linked in: rfcomm ccm aufs overlay cmac algif_hash algif_skcipher af_alg bnep snd_sof_pci snd_sof_intel_hda_common nvidia_uvm(O) snd_soc_hdac_hda snd_sof_intel_hda
[Kernel-packages] [Bug 1944955] Re: Update the 470 NVIDIA driver
The test results are available at https://docs.google.com/spreadsheets/d/10rgG0qyrMdhwjrpHdPecCeDk4MGVZs7iPJdAZcHZZkk/edit#gid=1527963777 No regressions were found. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu. https://bugs.launchpad.net/bugs/1944955 Title: Update the 470 NVIDIA driver Status in nvidia-graphics-drivers-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-470 source package in Focal: Fix Committed Status in nvidia-graphics-drivers-470 source package in Hirsute: Fix Committed Bug description: Update the 470 (UDA) NVIDIA series in Bionic, Focal, Hirsute. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 470.74 (470) == * New upstream release: - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Updated nvidia-bug-report.sh to search the systemd journal for gdm-x-session logs. - Fixed a bug that could prevent nvidia-xconfig from disabling the X Composite extension on version 1.20 of the X.org X server. - Fixed a build failure, "too many arguments to function 'get_user_pages'", when building the NVIDIA kernel module for Linux kernel v4.4.168. - Fixed a build failure, "implicit declaration of function do_gettimeofday", when building the NVIDIA kernel module for Linux kernel 5.0 release candidates. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1944955/+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 1945417] Re: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.d
*** This bug is a duplicate of bug 1945414 *** https://bugs.launchpad.net/bugs/1945414 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1945414, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Tags removed: need-duplicate-check ** This bug has been marked a duplicate of bug 1945414 package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945417 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Upgrade error: when running software updater. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 08:04:57 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:5.11.0-37.41~20.04.2 Unpacking linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-0AD8TG/21-linux-modules-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.11.0-37-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-03-23 (189 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1945417/+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 1945417] [NEW] package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty
*** This bug is a duplicate of bug 1945414 *** https://bugs.launchpad.net/bugs/1945414 Public bug reported: Upgrade error: when running software updater. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 08:04:57 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:5.11.0-37.41~20.04.2 Unpacking linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-0AD8TG/21-linux-modules-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.11.0-37-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-03-23 (189 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945417 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Upgrade error: when running software updater. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 08:04:57 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:5.11.0-37.41~20.04.2 Unpacking linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-0AD8TG/21-linux-modules-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.11.0-37-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-03-23 (189 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1945417/+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 1932117] Re: Lots of hisi_qm zombie task slow down system after stress test
https://lists.ubuntu.com/archives/kernel-team/2021-September/123793.html
Thanks Cascardo pointing out that patch a13c97118749 ("crypto: hisilicon/sec2 -
Add workqueue for SEC driver.") is also needed and in order to cherry-pick it,
we need to cherry-pick eaebf4c3b103 ("crypto: hisilicon - Unify hardware error
init/uninit into QM") too.
I am testing patched kernel and see if any more issue shall be noted.
--
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/1932117
Title:
Lots of hisi_qm zombie task slow down system after stress test
Status in kunpeng920:
In Progress
Status in kunpeng920 ubuntu-18.04-hwe series:
In Progress
Status in kunpeng920 ubuntu-20.04 series:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Hirsute:
Invalid
Status in linux source package in Impish:
Invalid
Bug description:
[Impact]
hisi_qm does not clean up kernel process after calculation is done. Many
zombie processes slow down system. After checkbox cpu stress test, it takes
more then 2min to ssh in.
[Test Plan]
1) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times
--af-alg 0
2) ps aux | grep hisi_qm | wc -l
Expected result is less then 100
[Regression Risk]
hisi_qm only affects kunpeng920 platform. Minimal risk for other platform,
and full regression test is needed on kunpeng920.
===
[Bug Description]
With focal 5.4 kernel, crypto driver does not clean up its created process
when calculation is done. Many zombie processes slow down system. e.g. Takes
more then 10sec for ssh connection.
[Steps to Reproduce]
1) Install Ubuntu 20.04 with GA (5.4) kernel
2) sudo apt install -y stress-ng
3) stress-ng --aggressive --verify --timeout 300 --metrics-brief --tz --times
--af-alg 0
4) ps aux | grep hisi_qm | wc -l
[Actual Results]
>10
[Expected Results]
<100
[Reproducibility]
100%
[Additional information]
Can not reproduce with focal HWE (5.8) kernel.
[Resolution]
To manage notifications about this bug go to:
https://bugs.launchpad.net/kunpeng920/+bug/1932117/+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 1945414] [NEW] package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty
Public bug reported: Upgrade error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 08:04:57 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:5.11.0-37.41~20.04.2 Unpacking linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-0AD8TG/21-linux-modules-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.11.0-37-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-03-23 (189 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-hwe-5.11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.11 in Ubuntu. https://bugs.launchpad.net/bugs/1945414 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux- headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted Status in linux-hwe-5.11 package in Ubuntu: New Bug description: Upgrade error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.20 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed Sep 29 08:04:57 2021 DuplicateSignature: package:linux-headers-5.11.0-37-generic:5.11.0-37.41~20.04.2 Unpacking linux-modules-5.11.0-37-generic (5.11.0-37.41~20.04.2) ... dpkg: error processing archive /tmp/apt-dpkg-install-0AD8TG/21-linux-modules-5.11.0-37-generic_5.11.0-37.41~20.04.2_amd64.deb (--unpack): unable to open '/usr/share/doc/linux-modules-5.11.0-37-generic/copyright.dpkg-new': Operation not permitted ErrorMessage: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted InstallationDate: Installed on 2021-03-23 (189 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.6 SourcePackage: linux-hwe-5.11 Title: package linux-headers-5.11.0-37-generic 5.11.0-37.41~20.04.2 failed to install/upgrade: unable to open '/usr/src/linux-headers-5.11.0-37-generic/scripts/mod/empty.dwo.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1945414/+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
